Organization Design and Operating Model
Structure Is Not the System
Why the Org Chart Is Not the Company, and What It Takes to Build an Organisation That Adapts
Most transformations are not lost in the planning. They are lost in the execution, and the execution is shaped by a system most leadership teams have never deliberately designed. Strategy does not fail at the planning layer. It fails at the execution layer, and the operating model is where the failure happens.
When performance stalls, the common instinct is to reorganise. New reporting lines. A few combined teams. A leadership role created to own the priority that keeps slipping. The chart changes; the company does not. Six months on, the same decisions take just as long, the same work falls through the same gaps, and the same priorities compete for the same attention. The structure moved. The system underneath it did not.
Organisation Design and Operating Model Are Not the Same Thing
Organisation design is how people, roles, capabilities, and accountabilities are arranged. The chart, the reporting lines, the question of who sits where. The operating model is something else entirely. It is how work moves across that structure: how decisions are made and who holds the right to make them, how governance functions, how resources move, how technology supports the work, and how performance is read and managed.
The two are routinely confused, and the confusion is expensive. A new org chart can clarify reporting lines and leave execution exactly where it was, because the delays, the duplication, and the ambiguity that slow an organisation down almost always live in the operating model, not in the boxes. Leaders can move teams, rename roles, and create new leadership positions, then discover that nothing about the speed or quality of execution has shifted.
A simple test exposes the gap. Create a new role to own a priority that spans several functions. If the role carries the title without the authority over the trade-offs, the budget, and the shared metrics the priority depends on, the title will not move the work. The structure says the priority has an owner. The operating model says otherwise.
Which is why the familiar design debate is the wrong one. The question is not centralise or decentralise. The more precise question is what work needs consistency, what work needs speed, what work needs local judgement, and what work needs enterprise coordination. Answer those four, and the structure follows from the answers. Start with the structure, and the design is a guess.
Simplify Before You Accelerate, but Not Toward a Simpler Organisation
The most consistent reason execution drags is an operating model that has grown complex enough to make work slow, expensive, and inconsistent. Complexity of this kind accumulates gradually. A platform is added to solve one problem. A committee is created after one initiative fails. A process is layered on to manage one risk. A metric is introduced to track one concern. Each addition is defensible on its own terms. The cumulative system becomes something no one can move through cleanly. Teams work around processes rather than through them, and meetings multiply because the formal model no longer resolves the work. That is how motion replaces progress.
There is one nuance most simplification arguments miss, and missing it is what causes them to overreach: complexity itself is not the enemy.
Reeves, Levin, Fink, and Levina argue the point persuasively in Harvard Business Review. A system built from many different, interconnected elements is harder to understand, and that same variety is what makes it resilient when conditions change. An organisation that runs on a narrow set of products, processes, and perspectives has very few ways to respond when the environment turns. The discipline is not to strip complexity out. The discipline is to make sure every addition earns its place, to keep the structure modular, and to govern it through a small number of clear operating principles.1
Simplification, then, is not about becoming smaller or more static. The work is removing the unmanaged complexity that consumes capacity, so the organisation has the headroom to absorb the complexity that matters and the room to move when conditions require it. The system is simplified precisely so it can adapt.
That reframes how a leadership team should treat disruption. A market shock, a regulatory shift, a sudden change in priorities is not only a cost to be absorbed and managed back to stability. It is also the moment when reallocation becomes possible and new capability can be built into the organisation. Companies that treat every disruption as a threat to be neutralised forfeit the upside. The ones that use the disruption to redeploy resources, retire low-value work, and build what they have been missing tend to come out of it stronger.
The research on this is unambiguous. Companies that reallocate resources dynamically deliver materially higher returns than those that hold their allocations steady, and the gap widens rather than narrows through downturns.2 3 Change is the opening, not the obstacle. The work is being ready to act on it.
Governance and Scanning Are How an Organisation Stays Adapted
Governance has a reputation problem, and the reputation is usually earned. In most organisations, it has become a catch-all for control: a steering committee added after a failure, a reporting line created to improve accountability, a forum added to manage a risk. Governance built that way slows the system in order to prove that work is being watched. Done well, governance is the opposite. Strong governance enables speed and trust precisely because it lets decisions move without losing control of them.
The failures are recognisable on sight. Meetings that review rather than decide. Dependencies no one owns. Progress no one recognises, so momentum stalls and no one notices. Effective governance answers four questions and stops there: what needs to be decided, who has the authority to decide it, what information is required, and how fast the decision must move. A forum that does not decide, unblock, reallocate, or stop low-value work is overhead wearing the costume of control.
Governance is only half of staying adapted. Adapting in the right direction depends on seeing the environment clearly and early. An organisation that scans regularly across markets, customers, competitors, technology, regulation, and its own performance—and feeds what it sees into the decisions that matter—can adjust deliberately rather than react late. Governance is the loop that connects sensing to deciding to reallocating. Without the scan, speed only delivers the organisation to the wrong place faster.
Adaptable Organisations Hold Stability and Dynamism at the Same Time
A shift is underway in how organisations hold stability and dynamism in the same design. McKinsey frames it as a move away from the organisation built primarily for stability—the static, siloed hierarchy in which decisions flow down from the top—toward a model that carries both qualities at once.4 The common misread is to treat stability and dynamism as opposites, where becoming more agile is taken to mean becoming less structured.
They are not opposites. The stable elements of an operating model—clear decision rights, consistent ways of working, a small set of operating principles, reliable visibility into performance—are precisely what make speed safe. An organisation without a stable backbone does not become agile when its structure is removed. It becomes chaotic. An organisation that is nothing but backbone cannot move at all. Adaptability lives in the combination: a stable spine that lets the rest of the body flex.
Which is why adaptability has to be treated as a capability built into the organisation rather than a slogan placed on top of it. Curiosity and adaptability are core competencies, not soft skills. Leaders who perform certainty about a future none of us fully understands teach their organisations to freeze, and a frozen organisation reads every change as a threat. Choices made under uncertainty are directional, not permanent. They become mistakes only when the organisation refuses to adapt to what it learns. When it does adapt, the same choices become starting points for the next move.
01
When priorities move, structure and funding have to move with them
A static budget is a strategy on autopilot. Most organisations set resource levels once and then adjust them only at the margin, year over year, regardless of how much the priorities have shifted underneath. The cost of that habit is well documented.
Roughly a third of companies reallocate about one percent of their capital from one year to the next, and the cross-company average is only about eight percent—yet eighty-three percent of executives name dynamic reallocation the single biggest lever they have for growth.2 The organisations that actually move money, people, and management attention toward where value is being created deliver close to ten percent in shareholder returns against six percent for the slow movers, and are worth roughly twice as much within two decades.2
The design implication is direct. An operating model has to include a mechanism for reallocation, not just an annual planning cycle. It needs a way to read shifting priorities and to move structure, funding, and attention toward them between cycles. When priorities can change inside a quarter, but funding can only change once a year, the system has been built to lag—and the lag is where advantage is lost.
Where the money sits and which teams own which work are operating-model decisions, not finance formalities. They either follow the current priority or they work against it. Treating them as fixed while expecting the organisation to be agile everywhere else is one of the more common contradictions in transformation design.
02
Skills are a design input, not an afterthought
Organisation design is the work of connecting priorities to the capabilities required to deliver them and then confirming that those capabilities actually exist where the priorities sit. Many designs come apart at exactly that point. The strategy names a priority, the structure assigns it to a team, and no one has tested whether the team holds the skills the priority requires. The chart looks complete. The capability is missing.
The difficulty is that skills are a moving target. The World Economic Forum reports that employers expect thirty-nine percent of workers’ core skills to change by 2030, and that the skills gap is now the single largest barrier to business transformation, named by roughly sixty-three percent of employers. 5 The capabilities a priority demands today are not the capabilities it will demand in three years. Among the skills rising fastest are not only fluency in AI and data but resilience, flexibility, and curiosity—the human capabilities that let people continue learning as the work itself changes. 5
Skill planning therefore belongs inside the operating model, not beside it. The design needs a way to identify the capabilities each top priority demands, to locate where those capabilities exist and where they are missing, and to build, buy, or redeploy them before the gap shows up in results. A design that assumes today’s skills will carry tomorrow’s priorities is already behind, whatever the chart says.
The operating model test
- Can we name the few priorities most critical to value creation, and does everyone agree on them?
- Do leaders know which work should stop, which should wait, and which should move now?
- Are decision rights clear at the moments where speed, cost, quality, and risk conflict?
- Can funding and people move toward a changed priority between planning cycles, not only once a year?
- Have we confirmed that the teams owning each priority hold the skills it actually requires?
- Do we scan the external environment regularly, and does what we see reach the people who decide?
- Does our governance help us make decisions, or does it mostly produce reporting?
- Can leaders identify where execution is stuck, who owns the barrier, and what decision is needed next?
- Is change sequenced to the capacity the organization has to absorb it, or only to our ambition?
What organizations that adapt do differently
The gap between organisations that execute well under pressure and those that do not is consistent and observable. The strongest share five operating habits.
01
They design the system, not just the structure
They change how work, decisions, and resources flow, rather than redraw the chart and hope behaviour will follow.
02
They simplify to create capacity to adapt
They strip out the unmanaged complexity that consumes capacity, without mistaking minimalism for the goal.
03
They move funding and structure as priorities move
They reallocate between cycles rather than freeze budgets for a year and call that discipline.
04
They treat skills as a design input
They identify the capabilities each priority requires and build them before the gap, rather than discovering it in the results.
05
They run governance as a decision and sensing engine
They scan the environment and convert what they see into faster, better-owned decisions, rather than into reports.
The system decides whether you can adapt
No organisation redraws its way to adaptability. The org chart is the easiest thing to change and, on its own, the least likely to change anything. What determines whether an organisation can move when the world moves is the system underneath the chart: how decisions are made, how resources follow priorities, how skills keep pace with the work, and how governance turns what the organisation sees into what it does.
None of this is an argument for more transformation theatre. It is an argument for designing the system on purpose. Build it well, and complexity becomes something the organisation uses rather than something that slows it down, and disruption becomes an opening rather than a threat. The companies that pull ahead will not be the ones with the boldest strategy or the longest list of initiatives. They will be the ones designed to adapt on purpose.
How mBolden works with leadership teams
mBolden works with organisations where the strategy is clear but execution has become slower and more complex than it should be. The work is the design of operating models and governance that let an organisation change without destabilising performance.
In practice, that means separating the structure from the system, simplifying where complexity has stopped earning its place, redesigning decision rights and governance so decisions move with appropriate control, building the mechanism to shift funding and skills toward priorities as they change, and sequencing transformation to the capacity the organisation actually has to absorb it. Engagements are typically project-based, with optional ongoing advisory support.
Frequently Asked Questions
What Is the Difference Between Organisation Design and Operating Model?
Organisation design is how people, roles, capabilities, and accountabilities are arranged—the structure and the reporting lines. The operating model is how work actually moves across that structure: how decisions are made and who owns them, how governance functions, how resources move, and how performance is managed. Redrawing the structure changes the chart. Changing the operating model changes how the organisation performs.
Why Do Reorganisations So Often Fail to Improve Performance?
Does Simplifying the Operating Model Make an Organisation Less Able to Adapt?
How should funding and structure change as priorities shift?
They should move with the priorities rather than lag a year behind them. Research on dynamic resource reallocation shows that organisations that actively shift capital, people, and attention toward where value is being created outperform those that hold allocations steady. An operating model needs a mechanism to reallocate between planning cycles, not only within an annual budget.
What Role Do Future Skills Play in Organisation Design?
A central one. A priority is only as deliverable as the skills behind it, and those skills are a moving target. With a large share of core skills expected to change this decade, organisation design needs a way to identify the capabilities each priority requires, locate where they exist and where they are missing, and build, buy, or redeploy them before the gap shows up in results.
How does governance support adaptability rather than slow it down?
Effective governance is a decision engine, not a reporting ritual. It clarifies what needs to be decided, who decides, what information is required, and how fast the decision must move. Paired with regular scanning of the external environment, governance becomes the loop that turns what an organisation sees into deliberate, well-owned decisions—which is how it adapts in the right direction rather than simply reacting faster in the wrong one.
About the Author
Suzanne Knight, MBA, MA is the founder and CEO of mBolden, a global management consulting firm. She has advised more than 80 organisations across 14 countries on transformation, organisation design, and execution, with engagements spanning Fortune 500 companies and governments. A former Fortune 500 transformation executive, she now keynotes internationally on digital transformation, leadership, and leading through change—including a keynote on the discipline of using disruption to build capability rather than absorb it. She is a long-standing instructor at the Schulich School of Business Executive Education. Her work rests on a single thesis: transformation succeeds or fails at the execution layer, not the planning layer.
Sources and References
- Reeves, M., Levin, S., Fink, T., & Levina, A. (2020). Taming Complexity. Harvard Business Review, January–February 2020.
- Atsmon, Y. (2016). How nimble resource allocation can double your company's value. McKinsey & Company.
- McKinsey & Company. Never let a good crisis go to waste. McKinsey Quarterly.
- Aghina, W., De Smet, A., et al. (2018). The five trademarks of agile organizations. McKinsey & Company.
- World Economic Forum. (2025). The Future of Jobs Report 2025, Skills Outlook.