Key takeaways
- Start with the business outcome, not the HR activity.
- Diagnose work, structure and decision rights before prescribing a programme.
- Connect measures to the intended change and revisit them after implementation.
When performance problems appear, restructuring can feel like decisive action. New boxes are drawn, reporting lines change and titles are revised. But a new chart does not automatically improve execution. If decisions remain unclear, incentives conflict and work still crosses the same bottlenecks, the organisation may have changed its appearance without changing its operating capability.
Map the work and decision flow
Identify the outcomes the organisation must deliver and the critical decisions that shape them. Who needs to make each decision? What information is required? How often does it occur? What is the cost of delay or error? Mapping these flows reveals where authority is too centralised, responsibilities overlap or accountability disappears between functions.
Look beyond formal structure. Work is also shaped by governance forums, informal networks, systems, policies and management routines. A role may be accountable on paper while lacking access to the information or authority required to act. These gaps often produce escalation, duplication and dependence on a few individuals.
For leaders, the implication is to make the underlying assumption visible and test it against the organisation’s actual context. The same practice can produce different results across roles, sectors and operating conditions. Define the decision, identify what evidence would change it, and record the limits of the analysis so that a useful framework does not become a rigid rule.
Choose structure to support the strategy
Functional, product, geographic, customer and matrix structures each create trade-offs. Functional structures can deepen expertise and standardise practice but create cross-functional coordination demands. Product or customer structures can sharpen accountability but duplicate specialist capability. Matrix structures can combine dimensions but require explicit decision rights and conflict resolution.
There is no universally best organisation chart. The right design depends on strategic priorities, scale, risk, interdependence and the speed of decisions. Make the trade-offs explicit and test the design against real operating scenarios rather than selecting a fashionable model.
For leaders, the implication is to make the underlying assumption visible and test it against the organisation’s actual context. The same practice can produce different results across roles, sectors and operating conditions. Define the decision, identify what evidence would change it, and record the limits of the analysis so that a useful framework does not become a rigid rule.
Clarify accountability and authority
Accountability should identify the outcome owner; authority should specify which decisions that person can make; consultation should identify whose expertise is required; and escalation should define when a decision moves elsewhere. Ambiguity creates either paralysis or uncontrolled local variation.
Use a small set of decision principles and test them against recurring decisions. Avoid producing a large responsibility matrix that no one uses. The objective is to make important decisions faster and more reliable while preserving appropriate control.
For leaders, the implication is to make the underlying assumption visible and test it against the organisation’s actual context. The same practice can produce different results across roles, sectors and operating conditions. Define the decision, identify what evidence would change it, and record the limits of the analysis so that a useful framework does not become a rigid rule.
Design roles and interfaces
Roles should be designed around outcomes, core responsibilities and interfaces with other roles. Overlapping responsibilities may be deliberate where collaboration is essential, but the overlap needs rules. Gaps between roles are especially risky because each person may assume someone else owns the work.
Review spans of control, management layers, specialist capacity and the burden of coordination. A structure that appears efficient in headcount terms may create excessive meeting load or overload managers. Assess the work required to coordinate the design, not only the number of boxes it contains.
For leaders, the implication is to make the underlying assumption visible and test it against the organisation’s actual context. The same practice can produce different results across roles, sectors and operating conditions. Define the decision, identify what evidence would change it, and record the limits of the analysis so that a useful framework does not become a rigid rule.
Implement and evaluate
Treat organisation design as a change in how work gets done. Explain why the design is changing, what decisions will move, what will stay stable and how employees will get support. Update processes, role expectations, systems and performance measures so the formal design matches daily reality.
Evaluate outcomes after implementation: decision speed, hand-off quality, accountability, service levels, employee experience and cost. Watch for unintended consequences such as new silos or increased escalation. Adjust the design based on evidence rather than defending the original chart.
For leaders, the implication is to make the underlying assumption visible and test it against the organisation’s actual context. The same practice can produce different results across roles, sectors and operating conditions. Define the decision, identify what evidence would change it, and record the limits of the analysis so that a useful framework does not become a rigid rule.
Applying the analysis in practice
A leadership working session should connect the strategic objective to the work, capabilities and operating conditions that make it possible. Bring the business owner, operations, finance and people leaders into the same discussion. Ask each function to state its assumptions, then identify where they conflict. The value of the session is not consensus for its own sake; it is a clearer set of choices and owners.
Test the design against an ordinary day and a difficult day. What happens when demand rises, a critical person is unavailable, a customer issue crosses teams or a risk requires escalation? These scenarios reveal whether the organisation can operate as designed or depends on informal workarounds. Document the gaps and decide which are tolerable, which require controls and which need redesign.
Keep a decision log. Record the problem, evidence, options considered, trade-offs, decision owner and review date. This makes the reasoning visible and helps the organisation learn when assumptions change. It also discourages repeated debates in which the same options are reopened because no one remembers why the earlier choice was made.
A useful diagnostic is to ask whether the same problem persists across different people and teams. If it does, investigate shared processes, incentives, technology and governance before assuming the issue is individual capability. If the problem is concentrated, examine local leadership, role clarity and workload. This distinction helps target the intervention and prevents a broad programme from being applied where a narrower fix is more appropriate.
When several interventions are required, sequence them. Clarify decision rights before training people to make decisions; repair the data before introducing a dashboard; align performance measures before asking teams to collaborate more closely. The order matters because one intervention may depend on another. Identify these dependencies in the plan and make them visible to the executive sponsor.
A common failure is to treat the design as a one-time reorganisation. Strategy, customer demand and technology evolve, so the operating model needs a review mechanism. Establish triggers that prompt reconsideration—for example, repeated service failures, changes in demand, material new risk or a sustained shift in required capability. A trigger does not automatically mean restructure; it means leaders should revisit the assumptions and evidence before the current design becomes a constraint.
Keep employees informed about the reasoning and practical consequences. People need to know how responsibilities, decision paths and success measures will change, what support will be available and where questions should go. Communication cannot remove every concern, but it can reduce avoidable ambiguity. Involve managers early enough that they can explain the change accurately and raise operational problems before they become embedded.
A useful test is whether the organisation can explain the link between strategic priorities and the capabilities it chooses to build. If the link is vague, leaders should revisit the diagnosis before adding more initiatives. A focused plan with clear trade-offs and measurable assumptions is generally more useful than a broad catalogue of desirable activities.
Map decision flow before drawing the structure
Organisation charts show formal reporting relationships, but they rarely reveal where decisions stall, work is duplicated or accountability is negotiated informally. This distinction matters because organisations can become very active without becoming more effective. New programmes, policies, dashboards and training sessions may all be well intentioned, yet their combined effect depends on whether they address the actual constraint in the work. Leaders should therefore resist beginning with the intervention they already know how to purchase or deliver. Begin instead with a clearly framed decision: what must improve, for whom, over what period, and what evidence would indicate that the current approach is not working?
A useful diagnostic compares three layers. The first is the intended outcome: the customer, operational or workforce result the organisation is trying to achieve. The second is the operating mechanism: the work, decisions, capabilities, resources and relationships that are expected to produce that result. The third is the observed experience: what employees and managers actually encounter, including delays, exceptions, workarounds and competing demands. The gap between these layers is often more informative than a single performance score.
For example, imagine a service team missing response-time commitments. It would be premature to conclude that the team simply needs more people. The organisation should test whether demand is forecast accurately, cases are routed to the right capability, staff have authority to resolve common issues, knowledge is accessible, and performance measures reward resolution rather than speed alone. The example is illustrative, not a claim about a specific employer. Its purpose is to show how a symptom can have several possible causes—and why diagnosis should precede investment.
A diagnostic for structural friction
Translate the diagnosis into a small number of explicit design choices. State the problem in operational language, identify the people affected, and describe the mechanism through which the proposed change is expected to work. Record the assumptions behind that mechanism. If the intervention depends on managers having time to coach, for instance, the plan must address workload and priorities; a manager-training course cannot create time that the operating model does not provide.
- Establish a baseline. Agree on definitions and capture the current level of performance, experience, cost, quality or risk. Note where the data is incomplete or unreliable.
- Identify the constraint. Use process observation, employee input, operational data and manager judgement together. Treat each source as partial evidence rather than assuming one source explains the whole system.
- Choose a proportionate intervention. Consider process redesign, clearer decision rights, role changes, capability development, technology, incentives or staffing. Explain why the chosen option is more plausible than alternatives.
- Run a bounded test where feasible. Define the population, duration, expected signal and safeguards. A pilot can reveal implementation issues, but it does not automatically prove that an intervention caused the outcome.
- Assign ownership and review. Name the decision owner, the people responsible for delivery, the review date and the conditions under which the organisation will adapt, scale or stop the intervention.
This discipline is not bureaucracy for its own sake. It reduces the risk of solving the wrong problem, makes trade-offs visible and helps leaders learn when conditions change. It also makes the work of HR, operations, finance and technology more coherent: each function can contribute its expertise to a shared problem statement instead of optimising its own activity in isolation.
What to measure—and what not to assume
Use a balanced set of measures. A leading indicator may show whether a necessary practice is happening; a lagging indicator shows whether the desired result is appearing. Pair operational measures with relevant employee or customer experience evidence. Check whether apparent improvement in one measure creates a cost elsewhere—for example, faster case closure accompanied by more repeat contacts, or lower turnover accompanied by declining internal mobility.
Interpret results in context. Differences between teams may reflect workload, customer mix, role complexity, local labour markets or management changes rather than the intervention being evaluated. Where possible, compare like with like, document changes that occurred during the measurement period, and avoid claiming causation from a simple before-and-after comparison. Qualitative evidence can help explain a pattern, but anecdotes should not be presented as proof of prevalence.
Organisation design is context-dependent: centralisation, decentralisation and matrix arrangements each create trade-offs that should be tested against the work. Use the original source to understand its scope, methodology and limitations before applying a finding to a different organisation, geography or workforce. External research can inform a decision; it cannot replace local diagnosis. The strongest professional judgement combines credible published evidence with transparent assumptions and the organisation’s own operational facts.
The executive question is therefore not merely, “Did we deliver the programme?” It is, “Did the change improve the condition we intended to improve, for the people and business outcomes that matter, and what evidence supports that conclusion?” That question moves the discussion from activity reporting to organisational learning.
A practical action plan
- Define the business question and the outcome that should change.
- Gather relevant quantitative and qualitative evidence; document limitations.
- Agree on a small number of actions, accountable owners and review dates.
- Measure intended outcomes and unintended consequences, then adjust.
Questions for leaders
- What business outcome is this issue affecting in our organisation?
- What evidence would distinguish a root cause from a symptom in the current situation?
- Which decision or practice should change first, and who owns it?
- How will we know whether the change helped, and what unintended effects should we watch for?
The point
Organisation design is not primarily a drawing exercise. It is the deliberate arrangement of work, decisions, capability and accountability to deliver strategy. Start with the operating problem, choose a structure that supports it, make interfaces explicit and review whether the new system improves execution. The practical test is whether the organisation can explain the choice it made, show how the evidence informed it and learn from what happened next.
References and further reading
The following sources inform the analysis. They provide evidence and guidance; their findings should be interpreted within their stated scope and context.
