10.06.2026

7 min. read

Most reorganisations move boxes and change nothing. Today, 63 percent of operating model redesigns achieve their objectives – up from 21 percent a decade ago. The difference lies in the operating logic beneath the chart: who is authorised to make which decisions, who holds the platform mandate, and how interfaces are governed. Leave those three questions open and you simply build the old friction into the new structure.

Key Takeaways

  • The org chart is the symptom, not the solution. Reorgs redraw lines but leave decision rights, mandates, and interfaces untouched. That is precisely where the friction originates – the friction that triggers the next reorg.
  • Three levers carry the model. Clear decision rights, a genuine platform mandate, and binding interface governance determine speed and value contribution. Without them, every structure is just a different form of standstill.
  • 20 to 30 percent in capital returns are on the line. That is how much potential capital return organisations forfeit, according to McKinsey, when their operating model is poorly aligned – and it hits directly on the bottom line.

Related:AI Governance: why CEOs cannot delegate  /  20 percent of companies capture 74 percent of AI returns

Why the reorg is usually the wrong tool

A reorganisation is the most visible answer to an invisible problem. It can be announced, displayed on slides, and measured in quarters. That is why leadership teams reach for it reflexively whenever performance stalls. Changing the org chart feels like action.

The effect evaporates because the friction rarely lives between the boxes – it lives in the handoffs. Who can make an architecture decision without navigating three escalation layers? Who carries the budget for a shared platform that belongs to no one outright? Those are the points where an organisation loses momentum, not in the number of hierarchy levels.

What is an operating model? The operating model describes how an organisation creates value: who makes which decisions, how work flows between units, which platforms are shared, and how success is measured. It is the operating logic beneath the org chart, and it determines whether a structure actually holds – or simply looks different.

McKinsey has put hard numbers to this. Across more than 2,000 executives, the data shows that poorly aligned operating models cost organisations 20 to 30 percent of their potential capital return. The encouraging finding from the same study: the success rate of redesigns has climbed from 21 to 63 percent. The lever was not more structure – it was better alignment among decision-makers and a disciplined rebuild of core processes.

Three Levers That Determine Value Contribution

The first lever is decision rights. In most organizations, nobody has defined who is authorized to make a decision unilaterally and who merely needs to be consulted. The result is a culture of cover-your-back: every resolution escalates upward, every conflict becomes a matter for the boss. An operating model that actually holds must codify decision rights explicitly – down to the question of which technical call a platform team can make without checking in with anyone. Where that clarity is absent, even Enterprise Agility fails at the first real escalation.

The second lever is the platform mandate. Shared platforms – from the data foundation to the internal developer stack – rarely fail for technical reasons. They fail because nobody has the mandate to set binding standards. A platform team without a mandate becomes a supplicant, negotiating every integration one by one. With a mandate, it becomes a standard-setter whose default decisions stand unless a business unit can demonstrate a documented exception. That shift is precisely what separates a scaling platform from an expensive side project, as the jump from AI pilot to production consistently demonstrates.

The third lever is interface governance. Every reorg generates new handoff points between units. Left unregulated, the old friction simply relocates to a new address. Binding interfaces define what one unit owes another: which data, at what quality, by when. That may sound bureaucratic – it is the opposite. Clear handoffs reduce handovers, duplicated work, and coordination loops, which is precisely the friction McKinsey identifies as a central lever in any redesign.

Whoever redraws the org chart and forgets the decision rights will be dealing with the same friction in 18 months – just in a different place.

The number that sets the direction

21 to 63 percent. That is how sharply the success rate of operating model redesigns has risen over a decade. The driver: clean decision rights, serious process investment, and a mandate that makes standards binding.

The DACH Factor: Co-Determination, Matrix Structures, and SAP

In the German-speaking context, the model collides with three distinct realities. The first is co-determination. Redistributing decision rights and making interfaces binding touches on operational changes that require works council involvement. This does not merely slow things down – it also disciplines the process: a mandate that has cleared employee representation tends to hold up far better under real-world pressure.

The second reality is the entrenched matrix. Many DACH corporations carry a dual reporting line – regional and functional – that undermines any clean allocation of decision authority. An operating model that holds here does not need to dismantle the matrix, but it must specify, for each type of decision, which axis takes precedence. Without that, the decision right remains a paper promise.

The third is the SAP-centric core. When a single ERP system dictates process logic, interface governance is not a free design choice – it is anchored to the realities of that system. That is a constraint, but also a stabilizer: where processes are already wired into the system, handoffs can be defined more precisely than in a loose tool landscape. Clean interface governance also requires tech talent with an interface profile, not just deep functional expertise.

The Counter-Argument: Sometimes the Structure Really Does Need to Change

One can argue that there are situations where only a genuine structural overhaul helps. After a merger, during a carve-out, or when a business model collapses, tweaking decision rights simply isn’t enough. That’s true. But the objection confuses occasion with method. Even a necessary structural overhaul only holds if the three levers are pulled in tandem. Whoever redraws the org chart without clarifying decision rights, platform mandates, and interfaces will face the same friction in a different place 18 months later. The mechanism is equally visible with AI: organisations that fundamentally rebuild their workflows extract significantly more value from the technology than those who stop at isolated pilot projects, according to BCG.

The First Step for the Next 90 Days

Don’t touch the org chart – instead, list the ten most important recurring decisions. For each one, answer this question: who decides alone, who is consulted, who is merely informed? That single step already reveals where decisions are unnecessarily escalating upward. In parallel, identify the three most costly interfaces between units and document exactly what each owes the others. Only once those two lists exist does the question of structure become worthwhile. More often than not, it then becomes clear that the reorg wasn’t necessary at all – because the real problem sat in the handoffs, not the boxes. Anyone who works through this rigorously also prevents the next reorg, since the capacity for change is more limited than the roadmap assumes.

Frequently Asked Questions

Why do so many reorganisations fail?

Because they change the org chart while leaving the underlying operating logic untouched. The real friction sits in decision rights, missing platform mandates, and unresolved interfaces. If these three levers are not moved, a reorg simply relocates the old friction to a new address – and forces the next restructuring in 18 months.

What distinguishes an operating model from an org chart?

The org chart shows reporting lines – who answers to whom. The operating model describes the business logic: who is authorised to make which decisions, how work flows between units, which platforms are shared, and how value contribution is measured. Two organisations with identical org charts can operate in completely different ways.

What is the concrete first step, without immediately rebuilding everything?

An audit of the ten most important recurring decisions, paired with a clear assignment of who decides alone, who is consulted, and who is merely informed. Add the three most costly interfaces between units and define what each unit owes the others. These two lists often clarify more than any new org chart ever could.

Previously on Digital Chiefs

Digital ChiefsApple Builds AI as Its Moat: The Golden Gate StrategyDigital ChiefsThe global market is disintegrating – Europe’s strength becomes a trap.Digital ChiefsAI Has Broken the Hiring Mold: What Matters Now

More from the MBF Media Network

cloudmagazinKubernetes as the AI Default OS: Clusters as a Compliance Question mybusinessfutureAI Agents on the Team: Why Only One in Nine Pilots Goes Live securitytodayDORA and NIS2: Why Bank Audits Are Now Colliding

Image source: AI-generated (June 2026), C2PA certificate embedded in image

Share this article:

Also available in

More Articles

18.06.2026

Silent Deindustrialization: the Missing Successor Ecosystem

Bernhard Liebl

7 min. read Germany loses economic substance every year without anyone accounting for it. Around 114.000 ...

Read Article
17.06.2026

Geopolitics Meets the Data Center Roadmap: What CIOs Must Secure Now

Eva Mickler

6 min read Two seemingly unrelated developments are now converging on the same blueprint: the escalation ...

Read Article
17.06.2026

Records Management as a CIO Topic: Why Governance Ownership is Needed

Eva Mickler

7 min read In most companies, no one has ever answered the question of who actually owns the responsibility ...

Read Article
15.06.2026

When a Sovereign Stack Really Pays Off

Tobias Massow

7 min. read Sovereignty features in most presentations as a values argument: control over data, independence ...

Read Article
14.06.2026

The Blind Spot in the Transformation Pitch

Eva Mickler

7 min. read A transformation pitch rarely promises too little. It promises the wrong things in the right ...

Read Article
13.06.2026

When an AI Model Disappears Overnight: Why CIOs Need a Plan B

Tobias Massow

6 Min. read time On June 12, Anthropic took two of its latest models offline worldwide after a U.S. ...

Read Article
A magazine by Evernine Media GmbH