A new strategy gets announced, everyone nods, and six months later the organization is still running exactly as it did before — same reporting lines, same decision-making bottlenecks, same meetings, just with a new set of words in the strategy deck. This happens because strategy and operating model are treated as separate workstreams: strategy gets set at an offsite, and the organizational structure is expected to catch up on its own. It rarely does. An operating model — the structure, decision rights, and processes that actually determine how work gets done — doesn’t evolve automatically just because the strategy changed. It has to be deliberately redesigned to match, and that redesign is usually where the real difficulty of “strategy execution” actually lives.
Key Takeaways
- A strategy that requires new capabilities or priorities but keeps the old operating model will default back to old behavior within months.
- Operating model redesign should start from decision rights and workflow, not from an org chart redraw.
- Structure follows strategy, but only if someone explicitly does the translation — it doesn’t happen by osmosis.
- Redesigning reporting lines without redesigning incentives and metrics produces a new structure chasing old behavior.
- Pilot the new operating model in one part of the business before a full redesign, since organizational change carries real execution risk.
Why New Strategy and Old Structure Don’t Coexist Quietly
An operating model encodes assumptions about what matters. Reporting lines reflect what leadership needed to control closely at the time they were drawn. Decision-making processes reflect what used to require careful, slow deliberation versus what could be delegated. When strategy shifts — a move into a new market segment, a push toward a different customer model, a new emphasis on speed over cost control — those old assumptions often stop matching what the business now needs, but nobody has explicitly revisited them. The result is an organization trying to execute a new strategy through decision rights, incentives, and workflows that were quietly optimized for the old one. People aren’t ignoring the strategy; the system around them is still pulling toward the previous priorities.
Starting From Decision Rights, Not the Org Chart
The instinct when redesigning an operating model is to start by redrawing boxes and lines — who reports to whom. This is usually the wrong starting point, because an org chart is a consequence of how decisions and work are supposed to flow, not the thing that determines it. A more effective sequence starts with mapping the decisions that actually matter to executing the new strategy: what gets decided, at what level, how fast, and with what information. Only once that’s clear does it make sense to ask what structure supports those decision flows best. Practical steps:
- List the five to ten decisions most critical to the new strategy’s success (e.g., pricing exceptions, new product prioritization, resource reallocation across regions).
- For each, determine the ideal decision-maker based on who has the best information and the most direct accountability for the outcome — not who currently holds that authority.
- Identify where the current structure creates unnecessary approval layers or, conversely, where a decision is too decentralized and creating inconsistency.
- Only after this mapping, redesign reporting lines and structure to support the decision flows identified, rather than starting from a structural template.
Redesigning Incentives and Metrics Alongside Structure
A new structure with old metrics and incentives is one of the most common ways operating model redesigns quietly fail. If the new strategy requires cross-functional collaboration but individual performance metrics still reward purely functional output, people will optimize for what they’re measured on, regardless of what the org chart says. Every operating model redesign should include an explicit review of what gets measured and rewarded at each level affected by the change, and update those metrics to actually reinforce the new decision rights and priorities. This is frequently skipped because it touches compensation and performance management, which are harder and slower to change than a reporting line — but skipping it is exactly why so many restructurings produce a new chart with the same old behavior underneath it.
Mapping the Transition, Not Just the End State
It’s common to design a clean target operating model and then struggle badly in the transition, because moving from the current state to the target state was never explicitly planned. People need to know not just where the organization is headed but what changes for them specifically, when, and what happens to decisions and work in flight during the transition period. A transition plan should address:
- Which decisions and workflows move to the new model immediately versus on a phased timeline.
- How work in progress under the old decision rights gets handled — abrupt cutover on active initiatives creates confusion and dropped accountability.
- Interim reporting or communication mechanisms for the period when the org chart has changed but new relationships and trust haven’t yet formed.
- A clear point of contact for people whose role or reporting line is genuinely ambiguous during the transition, since some ambiguity is unavoidable even with good planning.
Piloting Before Full Rollout
Operating model changes carry real execution risk — a poorly designed decision-rights change or reporting structure doesn’t just fail quietly, it can actively slow the business down while people figure out the new rules. Where the organization’s structure allows it, piloting the redesigned model in one business unit, region, or function before a full rollout is a lower-risk path than changing everything simultaneously. A pilot surfaces practical issues (a decision right that sounded right on paper but creates a bottleneck in practice, a metric that doesn’t actually reinforce the intended behavior) while the blast radius is contained, and gives the organization real evidence to refine the model before it goes wide.
Frequently Asked Questions
How do we know if our operating model actually needs to change, or if execution is just slow for other reasons?
A useful test is to trace two or three important recent decisions related to the new strategy and see where they got stuck or diluted. If the same structural bottleneck or unclear decision right shows up repeatedly, that’s a sign the operating model itself needs redesign, not just better execution discipline within the current one.
How long does an operating model redesign typically take?
Decision-rights mapping and target design can be done in six to ten weeks for a focused scope. Full transition, including a pilot and phased rollout, more typically spans two to three quarters, depending on organizational size and complexity.
Does every strategy change require an operating model change?
No. Incremental strategy adjustments that don’t change what decisions matter most or who needs to make them can often be executed within the existing model. The signal that redesign is needed is when the new strategy requires materially different decisions, speed, or cross-functional coordination than the current model supports.
Who should lead an operating model redesign?
It needs senior sponsorship, since it touches decision rights and reporting lines across functions, but day-to-day design and transition management benefits from a dedicated program lead who isn’t also trying to run a full-time operational role simultaneously — this work requires sustained focus that’s hard to sustain as a side project.
Related Reading
- Cash Flow Visibility During Periods of Rapid Growth
- Budget Governance for Multi-Entity Organizations
- Learn more about our Finance & Operational Transformation services