An organisational structure defines who is accountable for which outcome, where each type of decision is taken, and how work moves between units. It sets the ceiling on how fast a strategy can be executed. A structure built for the previous set of goals does not announce itself as a problem: it shows up as delay, as escalation, and as coordination work that produces no output.
Where structures fail, and what fixes them
- Structure determines whether a strategy can be executed and how fast the organisation can adapt.
- Main symptoms of dysfunctional structures: silo thinking, diffusion of responsibility, ineffective communication, slow decisions.
- Two failure modes: defending the existing structure, and copying a model that solved someone else's coordination problem.
- Effective structures are context-dependent: market logic, culture, and leadership style all constrain the design.
- The redesign starts with an as-is picture: network analysis, process reviews, decision-flow assessments.
- Distributed decision rights only take effect when the leaders who held them stop using them.
- Implementation runs in stages: pilot in one unit, involve the people affected, adjust before scaling.
- A structure defines which decisions a company can take quickly, and which it cannot take at all.
The symptoms that get misread as something else
Four symptoms appear before anyone calls it a structural problem. The same question gets answered differently depending on who is asked. Decisions escalate one level higher than they need to. Departments optimise against targets that were never reconciled with each other. And the people who cared most about getting work finished leave first.
None of these register as structural at the time. They are read as a communication problem, a discipline problem, or a personnel problem, and get treated accordingly. The structural diagnosis usually arrives after two rounds of fixes that could not have worked.
Why fit matters more than the model you pick
Fit is what makes a structure effective, and fit is specific to the situation. An agile structure in a highly standardised, regulated environment adds coordination cost without adding adaptability. A steep hierarchy in an innovation-driven market puts the slowest available path in front of every product decision. The design question is which coordination problem the company has, and every model answers a different one.
Organisational design is only part of the structure. What actually governs behaviour is the combination of reporting lines, the process organisation, the decision rights attached to each role, and accountability that follows results rather than activity. A transformation is where the difference becomes measurable, because that is when the structure has to carry decisions it was never designed for.
Three misconceptions that keep a structure in place
- Defending the familiar: many organisations hold on to a structure long after the symptoms have named the problem, duplicated work, conflicting objectives, coordination rounds that end without a decision.
- Underestimating change: a structural change redistributes power, and the people affected understand that before the announcement is finished. Projects that treat it as a design exercise stall at the point where someone has to give up scope.
- Believing in one-size-fits-all: matrix, holacracy and agile models each solve a specific coordination problem. Copying one without knowing which problem it solves imports the cost and none of the benefit.
An honest as-is picture comes before the target picture
The redesign starts with a description of how the organisation actually works, not how the org chart says it works. The two diverge most at the interfaces between units, and that is where the delay sits.
The strategic direction has to be settled before the design starts, because structure follows the intent and not the function. Three questions decide it: which position in the market the company is going for, which decisions have to be fast, and how much autonomy each unit needs to take them.
What comes out of that is a target structure specific to the company, tied to the strategy, workable within the existing culture, and implementable in stages rather than in one cutover. The people affected belong in the design, because they decide in practice whether the new decision rights get used or worked around.
What the new structure demands of leaders
A structure that distributes decisions only works if the leaders who used to take them stop taking them. That is a behavioural change and it needs training and supervision, not an announcement. The practical test comes the first time a team decides something the leader would have decided differently.
Leaders also have to set guardrails narrow enough that distributed decisions stay consistent and wide enough that they remain decisions. Without that shift the new structure describes behaviour that never occurs.
Six steps from diagnosis to a structure that holds
1. Map how decisions and information actually flow
What to do:
- Map information and decision flows, not just the boxes
- Run a network analysis: where do informal power centres form, and where do interfaces break down?
- Review process interfaces: where is work duplicated, and where is ownership missing?
- Analyse conflict patterns: which structural tensions are holding the organisation up?
Tools: RACI matrix, swimlane mapping, shadowing, heatmaps.
2. Test the structure against the strategy
Structures follow the strategy, not the reverse.
Key questions:
- Where are we heading, and what differentiates us?
- Which capabilities and which speeds do we need?
- How much autonomy does each unit require?
Practical rule: structure follows the operating model, not the org chart.
3. Combine archetypes deliberately
Pure models rarely help. Their principles combine:
- Functional, divisional, or process-oriented?
- Steering centralised, decentralised, or hybrid?
- Coordination via projects, committees, or communities?
Evaluate at least two variants against the same set of real decisions before choosing one.
4. Define decision rights and governance
An org chart without governance changes nothing.
- Who has the final decision?
- Which committees meet when, and for what purpose?
- Who is accountable for results, not just activities?
- Who owns the handovers between units?
Shared responsibility for an outcome usually means nobody is responsible for it.
5. Pilot in one unit, then scale
Structures have to prove themselves in day-to-day practice:
- Test prototypically in one business unit
- Define clear KPIs such as time-to-decision and escalation rate
- Make failures visible and improve iteratively
6. Anchor the structure in leadership behaviour
Structural change only holds when culture and leadership move with it:
- Prepare leaders for their new role, in particular the decision logic and shared accountability
- Involve employees in the design, not only in the announcement
- Make the reason for the change explicit: what is changing, and why
What to check a year after the reorg
A structural change is not finished when the new chart is published. Three questions a year later show whether it took. Are decisions being taken at the level the design assigned them to, or have they drifted back up? Has the time from question to decision changed in the units that were restructured? Can each department name the outcome it is accountable for without looking at the chart?
If those answers come back no, the redesign stopped at the chart and never reached the decisions.
Organisational structure: the questions we get asked most
What is an organisational structure?
An organisational structure is the formal arrangement of units, roles, reporting lines and decision rights through which a company gets its work done. It is broader than the org chart, because it includes the process organisation and the governance that determines where a decision is taken. The chart shows only the reporting part of it.
What is the difference between an organisational structure and an operating model?
The organisational structure covers units, roles and reporting lines. The operating model is wider: it also covers the value chain and who owns each stage of it, the processes, the technology, the planning cadence and the metrics used to steer. A structure change that leaves the operating model untouched rarely changes how the company runs.
What are the main types of organisational structure?
Four archetypes cover most cases: functional, organised by discipline; divisional, organised by product, region or customer segment; matrix, with dual reporting lines; and process-oriented, organised along the end-to-end value chain. Most real structures combine two of them. The choice depends on which coordination problem is the expensive one in that business.
What are the signs that a structure no longer fits the strategy?
Decisions escalate a level higher than the design intended. Handovers between units need a meeting to work. Two departments hold objectives that cannot both be met. Ownership of a customer-facing outcome is split across three units, so nobody can be held to it. Each of these is a design symptom, not a discipline problem.
How should a structural change be implemented?
In stages. A pilot in one business unit shows whether the new decision rights are actually used before the rest of the organisation depends on them. Settle the accountability and the escalation path before the reporting lines move, otherwise the pilot tests a chart rather than a way of working. Involve the people whose scope changes in the design itself.
