Insights

An Organization Chart Is Not Organizational Development

Creating an organization chart, assigning job titles, and writing job descriptions does not mean you have achieved Organizational Development. Discover how span of control, RACI, role clarity, KPI alignment, and As-Is to To-Be gap analysis help build an effective organization.

HendNovember 09, 20268 min read
Perinvo Organizational Development infographic showing organization charts, span of control, RACI matrix, role clarity, gap analysis and strategy alignment.

PERINVO INSIGHTS   /   ORGANIZATION DESIGN & TRANSFORMATION

An Organization Chart Is Not
Organizational Development.

You can draw reporting lines, assign titles, and write job descriptions — and still have an organization that struggles to make decisions, deliver results, and work across departments.

As-Is → To-Be Span of Control RACI Matrix Strategy & Performance

By Perinvo Consulting · Practical perspectives from organizational transformation projects

Executive Summary

Design how work happens — not just who reports to whom.

Effective organization design aligns strategy, work, capabilities, decision rights, accountability, processes and performance measures. The chart is one output of that design.

The Leadership Question

Before asking “Who should report to whom?”, ask “How must the business operate to achieve its strategy?”

One of the hardest parts of organization development work is understanding the real operating environment before recommending a new structure. What appears on an approved chart may be very different from what employees do every day.

In practice, organization design focuses on the operating model, structure, systems and measures. Organization development helps people, teams and culture adopt and sustain better ways of working. Both are necessary for lasting change.

01. The hidden problems an org chart cannot show

A visually perfect chart can hide serious execution problems. During an As-Is diagnostic, look for these warning signs:

Overlapping responsibilities

Two departments believe they own the same activity — or each assumes the other will complete it.

Unclear authority

Employees perform the work but cannot make routine decisions without multiple approvals.

Role drift

People regularly perform work outside their defined roles while critical work remains unassigned.

Disconnected KPIs

Departments meet local targets while the organization misses its overall business goals.

Paper-only procedures

Approved SOPs describe a process that teams do not actually follow.

Management bottlenecks

Critical decisions wait for one overloaded manager, even when teams have the skills to act.

Key principle: A reporting line explains formal supervision. It does not automatically explain process ownership, decision authority or accountability for outcomes.

02. Start with As-Is. Design To-Be. Validate the gap.

Do not begin by moving boxes in PowerPoint. Begin with evidence: leadership interviews, employee discussions, process walkthroughs, workload data, organization records and performance results.

STEP 01

As-Is

Map the work as it is actually done: roles, workflow, approvals, workload, pain points, headcount and performance.

STEP 02

To-Be

Define the future operating model needed to deliver the strategy, service levels and planned growth.

STEP 03

Gap Analysis

Identify gaps in capacity, skills, accountability, systems, controls, process design and management effectiveness.

STEP 04

Implementation

Redesign, test, communicate, train, assign owners and track whether the new model delivers better results.

What evidence should you collect?

  • Strategy: business priorities, customer commitments and required capabilities.
  • Work: key activities, process maps, handoffs, workload volumes and rework.
  • People: actual responsibilities, competencies, capacity, critical roles and vacancies.
  • Authority: approval limits, escalation routes and ownership of important decisions.
  • Performance: cycle times, cost, quality, customer outcomes and employee experience.

03. Seven questions to ask before drawing an organization chart

Design dimensionQuestion to investigateWhy it matters
1. Strategy alignmentWhich business outcomes must this design enable?Prevents building around personalities rather than priorities.
2. Core processesWhere is value created, and where do handoffs fail?Reduces duplication, delays and functional silos.
3. AccountabilityWho owns each critical process, result and decision?Makes outcomes and escalation paths clear.
4. Span & layersCan managers support their direct reports effectively?Balances coaching, supervision and management cost.
5. Workload & capacityWhat volume, capability and coverage does the work require?Grounds headcount decisions in demand rather than habit.
6. Decision rightsWhich decisions are local, shared or centralized?Prevents unnecessary escalation and weak controls.
7. Measures & behaviorsWill KPIs and incentives support collaboration and results?Connects the design with day-to-day execution.

Only then should you decide which functions to group, where managerial roles are justified, how reporting lines should work and what each role must deliver.

04. Span of Control: the number is not the answer

Span of Control is the number of direct reports assigned to a manager. It matters because it affects supervision, coaching capacity, information flow, delegation, management cost and decision speed.

ILLUSTRATION A

1 : 4

Narrower span

May be appropriate for highly complex work, intensive coaching or less-experienced teams, but may add supervisory layers and cost.

ILLUSTRATION B

1 : 12

Wider span

May work for standardized processes and experienced, autonomous teams, but can overwhelm managers when work is variable or risky.

Illustrative ratios only, not recommended benchmarks. There is no universal ideal span of control.

Five factors that determine a workable span

  1. Work complexity: Is the work repetitive or does each decision require expert judgment?
  2. Employee autonomy: Can team members operate independently, or do they need frequent direction?
  3. Process standardization: Are workflows predictable, documented and supported by systems?
  4. Manager workload: Is the manager also responsible for significant individual work or multiple locations?
  5. Risk and coordination: How much quality, safety, regulatory or cross-functional supervision is needed?

Practical test: If a manager has too many direct reports to coach, review and unblock, the span may be too wide. If approvals move through several managers who add little distinct value, the organization may have too many layers. Investigate both before removing or adding positions.

Do not ignore management layers

The number of hierarchical levels matters as much as the direct-report ratio. Extra layers can delay communication and decisions; too few may leave managers without enough support. Analyze span and layers together, based on the work and required control — not a fixed company-wide target.

05. RACI: who does the work, and who owns the outcome?

An org chart tells you who manages whom. A RACI Matrix helps clarify responsibility at the activity or process level — especially where departments interact.

R

Responsible

Performs the work.

A

Accountable

Owns the final result or decision.

C

Consulted

Provides input before action.

I

Informed

Receives updates.

Practical RACI example: approving a new position

Imagine a company where new hiring requests get delayed because HR, Finance and Operations are unsure who should approve what. A short RACI can clarify the process:

ActivityLine ManagerHRBPFinanceBusiness Head
Define the workload needRCIA
Validate role scope & job descriptionRAIC
Check financial impact & budgetCCR / AI
Authorize the new positionRCCA

Illustrative example. Actual responsibility assignments must match delegated authority, company policy and applicable controls. R / A means the same role performs the work and owns the outcome.

Good RACI practice: assign one clearly accountable role per activity, at least one responsible role, and only the necessary consulted parties. Then test the matrix with real cases. RACI should complement — not replace — approval authority policies and process documentation.

06. Design around processes, capacity and performance

A well-designed structure must support the work moving through it. Before approving headcount, assess workload volume, productive capacity, skill requirements, shift coverage, technology and expected service levels.

For repeatable activities, an initial capacity estimate can be built from forecast task-hours ÷ realistic productive hours per full-time employee. Adjust for variability, absence, coverage, skills and required supervision. This is a planning input — not a substitute for job analysis.

Cascading KPIs: from strategy to individual work

BUSINESS OBJECTIVE

Improve on-time delivery

PROCESS KPI

Order-to-dispatch lead time

TEAM KPI

Production schedule adherence

ROLE EXPECTATION

Timely escalation of material shortages

Illustrative manufacturing example: measures should reflect actual controllable contribution. Individual KPIs should not penalize employees for factors outside their authority.

A useful test: If every department reports green KPIs but customers experience delays, the organization may be measuring departmental activity rather than end-to-end performance.

07. A realistic example: restructure the work, not just the boxes

Consider a hypothetical manufacturing company where delivery delays lead to repeated disputes between Sales, Production and Supply Chain.

DimensionAs-Is problemTo-Be response
ProcessTeams work in separate handoffs.Map the order-to-delivery process and remove avoidable delays.
AccountabilityNo one owns the end-to-end result.Appoint a process owner and define a RACI for critical handoffs.
DecisionsExceptions wait for senior approval.Set explicit escalation thresholds and delegated authority.
PerformanceEach team optimizes a different target.Use shared on-time delivery and lead-time measures with clear role contributions.
StructureReporting lines do not support coordination.Change roles or reporting only where the process and accountability evidence justify it.

Notice the sequence: first understand the work, then improve decision rights and coordination, then change the structure if necessary. A new title alone would not solve the delivery problem.

08. How do you measure whether an OD project succeeded?

Count outcomes, not just documents completed. Use a baseline and review progress after implementation.

01 /

Decision cycle time

Time from a complete request to an authorized decision.

02 /

Process performance

Lead time, rework, defects, service levels or customer outcomes.

03 /

Accountability clarity

Critical activities with an agreed owner and decision path.

04 /

Manager effectiveness

Span distribution, coaching capacity and avoidable escalations.

05 /

Workforce productivity

Relevant output per labor hour, with quality and safety safeguards.

06 /

Adoption & experience

Procedure adoption, role understanding and employee feedback.

Interpret measures together. Lower management cost is not success if service quality declines; faster decisions are not success if controls become ineffective.

09. A practical OD project roadmap

PHASE 01Diagnose

Strategy review, interviews, process mapping, baseline metrics.

PHASE 02Design

Operating model, options, spans, layers, roles and decision rights.

PHASE 03Validate

RACI workshops, capacity analysis, risk checks and leadership sign-off.

PHASE 04Implement

Communications, training, updated job descriptions, systems and SOPs.

PHASE 05Improve

Review KPIs, resolve issues and adjust the model as needs change.

Five questions every CEO or HR leader should ask

  1. Can we explain how our structure supports our business strategy?
  2. Do we know who is accountable when a cross-functional process fails?
  3. Are our spans and management layers fit for the actual work?
  4. Do employees have both the responsibility and authority to deliver?
  5. Are we measuring better business outcomes — or only completing organizational charts?

The goal is not a beautiful chart.
The goal is an organization that works.

An effective organization makes responsibilities understandable, decisions timely, collaboration practical and performance measurable. It aligns strategy, structure, people, processes and accountability — and continues improving after the new chart is approved.

Design the work. Clarify ownership. Enable people. Measure the impact.

Discover Perinvo Consulting ↗

Further reading

The frameworks, examples and implementation recommendations in this article are presented for professional education. Company-specific decisions require validation against operating requirements, policies and applicable regulations.

© Perinvo Consulting 2026 · perinvo.com · Strategy. People. Performance. Transformation.

Reader discussion (0)

Comments and edits are reviewed before publication. Showing up to 20 comments per page.

Sign in or verify a reader account to comment and save articles.