Track · Product Operations4 min read

Reorgs That Redraw the Chart but Never Touch How Work Gets Done

Execution advisor Akin Monehin names the Structural Change Illusion: reorgs that redraw boxes while decisions, handoffs and behaviours stay frozen — and what CEOs, CHROs and boards should test instead.

The reorganisation that changes everything except how work gets done
The reorganisation that changes everything except how work gets donePexels / pixabay

Context

  1. Akin Monehin, author of Execution Is a Lie, defines the 'Structural Change Illusion': structural change without operating change.

  2. He has worked across 10+ countries at British Airways, Virgin Atlantic, Nigeria LNG and Shell's Deepwater Executive Leadership Team.

  3. Common failure test checks roles filled and reporting lines changed rather than whether decisions and handoffs improved.

  4. Boards should examine restructuring benefits like any other investment, against the original business case.

Six months after most reorganisations, the same decisions still travel through the same few people — and Akin Monehin, author of Execution Is a Lie and Managing Partner of Praxis Execution Advisory, has a name for why: the Structural Change Illusion. It's what happens when roles, reporting lines and boxes change while the decision flows, interfaces and behaviours that actually determine execution stay put.

His diagnosis is blunt. "If the boxes move but the decisions, handoffs and behaviours do not, the organisation has been redrawn—not redesigned."

That distinction is expensive to miss. Restructuring consumes management attention, creates uncertainty, disrupts relationships, slows decisions and can push good people out the door. Leaders accept those costs expecting faster decisions, clearer accountability, lower overhead or better customer ownership. When those outcomes don't arrive, the enterprise has paid the disruption cost without capturing the operating benefit.

Why do org charts fool everyone?

Charts are seductive because they make change visible. A box moves, a reporting line redraws, a role disappears, and a new function exists on Monday morning. But execution doesn't happen inside boxes. It happens through decisions, interfaces, information, incentives, routines and behaviours — where the operating model actually lives.

"An organisation chart can change overnight," Monehin writes. "The operating system underneath it usually does not."

He's seen the pattern up close. Over a career spanning British Airways, Virgin Atlantic, Nigeria LNG and Shell — where he sat on the Shell Deepwater Executive Leadership Team running Business Transformation, and across work in more than 10 countries — he has watched formal structures change materially while the real decision architecture barely moved. A new business-unit leader existed on paper, but major commercial decisions still returned to the centre. Functions were combined, yet their performance measures still conflicted. End-to-end process owners were appointed without authority over the functions controlling the work.

The redesign was visible. The operating reality was not.

What should leaders measure instead?

The illusion persists, Monehin argues, because companies test whether the new structure has been implemented, not whether the enterprise performs differently. The usual checklist — roles filled, reporting lines changed, job descriptions issued, employees briefed — proves structural completion, not operating change.

The stronger questions cut deeper:

  • Are decisions being made faster and closer to the work?
  • Have cross-functional handoffs improved?
  • Are accountabilities clearer where value is created?
  • Have duplicated approvals disappeared?
  • Are customer issues resolved with fewer escalations?
  • Have leaders actually stopped doing work that now belongs elsewhere?

A new structure changes where accountability is drawn. A new operating model changes how work moves. That's why reorganisations disappoint even when the design logic is sound: the legacy organisation survives through informal power, historical relationships, old performance measures, inherited approval routines and behaviours that outlasted the announcement.

People figure out what really changed fast. If a new role supposedly owns an outcome but still needs three old approvals, employees learn authority didn't move. If leaders announce empowerment but keep reversing decisions, judgement hasn't moved. If functions are told to collaborate while being rewarded for conflicting outcomes, the old system still governs behaviour. The chart says "new"; the operating signals still say "old".

What does this mean for CEOs, CHROs and boards?

Monehin splits the mandate by role. For CEOs, the test of a reorganisation should extend beyond span, layers and cost — leadership should be explicit about which decisions will move, which interfaces will change, and which enterprise outcomes should improve because the redesign happened.

For CHROs, organisation design can't stop at roles and reporting lines. Performance measures, incentives, capability and leadership behaviour must reinforce the new architecture, or the old organisation will quietly reconstitute itself inside the new one.

For boards, restructuring benefits deserve the same scrutiny as any other investment. If the business case promised faster decisions, lower overhead, stronger accountability or better customer outcomes, those benefits should eventually show up in operating evidence — not merely a completed chart.

His closing test is one any product or operations leader can run on Monday: compare your organisation six months before and six months after its last reorganisation. Which important decisions, handoffs and behaviours actually changed — and which simply survived inside a new chart?

As companies flatten structures and redraw reporting lines to chase speed and AI-era agility, the operating layer beneath the chart is where the next round of competitive advantage — or quiet failure — will be decided.

via businessday.ng (Source)

More from Daniel Okafor

Daniel Okafor

Show full bio

Staff writer covering technology and product news in product management at Roadmap File.

60 articles