Organization Development Archives - Centroid Strategy https://www.centroidstrategy.com/category/organization-development/ Organization Design & Workforce Transformation Fri, 06 Mar 2026 12:25:59 +0000 en-US hourly 1 https://www.centroidstrategy.com/wp-content/uploads/2018/10/favi.png Organization Development Archives - Centroid Strategy https://www.centroidstrategy.com/category/organization-development/ 32 32 Why Transformation Stalls — And How Operating Model Design Fixes It https://www.centroidstrategy.com/why-transformation-stalls-and-how-operating-model-design-fixes-it/ Fri, 27 Feb 2026 13:29:13 +0000 https://www.centroidstrategy.com/?p=1967 Transformation doesn't fail because strategy is wrong. It stalls because execution lacks deliberate design. Understanding the design gap that most leaders miss.

The post Why Transformation Stalls — And How Operating Model Design Fixes It appeared first on Centroid Strategy.

]]>
  • Organization Development

Why Transformation Stalls — And How Operating Model Design Fixes It

  • 6 min read
  • Centroid Strategy

Ask any CEO about their last major transformation, and the story is remarkably consistent.

Strategy was clear. Leadership was aligned. The vision was compelling. The roadmap was approved. And then — six months in — momentum started to slow. Decisions took longer. Accountability blurred. The transformation didn’t fail outright. It just… stalled.

The usual diagnosis? “Change fatigue.” “Cultural resistance.” “Lack of buy-in.”

The real diagnosis? The organization wasn’t redesigned to execute the transformation.

Transformation doesn’t fail because strategy is wrong. It stalls because execution lacks deliberate design.

The Design Gap

Most transformations begin with strategic clarity: new markets, new capabilities, new ways of competing. Leadership approves the strategy. Consultants are hired. Workstreams are launched.

But here’s what doesn’t get redesigned:

  • Who owns which decisions — and who has veto power
  • How information flows — and where it gets stuck
  • What gets measured and rewarded — and whether it aligns with the new strategy
  • Where accountability actually sits — not on the org chart, but in practice
  • How day-to-day work gets done — roles, processes, decision rights, data access

These are not “implementation details.” They are the operating model — the invisible architecture that determines whether a strategy can actually be executed.

When strategy changes but the operating model doesn’t, transformation stalls.

"You cannot execute a new strategy on an old operating model. The structure will always win."

Why Leaders Underestimate This

Operating model design feels less urgent than strategy. Strategy is visible, exciting, forward-looking. Operating model design is structural, detailed, and unglamorous.

So it gets deferred. Or delegated. Or assumed to be “something HR will figure out.”

But here’s the reality: an organization’s operating model is more durable than its strategy.

Change the strategy, and people will try to execute it using the old decision-making processes, the old reporting lines, the old incentives. They’re not being resistant. They’re being rational. The operating model tells them how work gets done. Until that changes, behavior doesn’t change.

This is why transformations that look successful in slide decks often feel stuck on the ground. The strategy changed. The structure didn’t.

The Three Structural Blockers

When transformation stalls, it’s usually because one (or all) of these three structural problems wasn’t addressed:

1. Decision Rights Are Unclear or Contested

In most organizations, it’s not obvious who actually owns key decisions.

  • Can regional leaders approve hiring without global sign-off?
  • Does the product team decide pricing, or does finance have final say?
  • Who can veto a restructuring proposal — and at what stage?

When decision rights are ambiguous, every decision becomes a negotiation. Speed drops. Accountability dissolves. People escalate to avoid risk.

The result: Transformation initiatives require 6 sign-offs instead of 2. Pilots take 9 months to approve. Momentum dies in committee.

2. Accountability Is Misaligned with Authority

People are held accountable for outcomes they don’t control.

  • A regional GM is accountable for revenue but can’t set pricing or control product roadmap
  • An HR BP is accountable for talent outcomes but has no authority over hiring decisions or compensation budgets
  • A transformation leader is accountable for adoption but has no control over incentives or performance metrics

This is the fastest way to create learned helplessness. People stop trying to drive outcomes they can’t actually influence.

The result: Transformation leaders spend their time lobbying for buy-in rather than executing. Progress slows to the speed of consensus.

3. Incentives Aren’t Aligned with the New Strategy

The transformation says: “We’re shifting from product-centricity to customer-centricity.”

But compensation is still tied to product P&L, not customer lifetime value. Promotions still reward individual heroics, not cross-functional collaboration. Performance ratings still emphasize quarterly delivery, not strategic capability-building.

The result: People do what they’re measured and rewarded for — which is the old strategy, not the new one. The transformation is announced, but behavior doesn’t shift.

Diagnostic Questions
If decisions take longer than they should, if accountability feels diffuse, or if people keep doing what they've always done despite new strategy — you have an operating model problem, not a change management problem.

What Operating Model Design Actually Means

Operating model design is not “drawing a new org chart.” Org charts show reporting lines. They don’t show how work actually gets done. A well-designed operating model answers these questions explicitly:

1. How is value created and delivered?

  • What are the core value streams? (How does work flow from customer need to delivered outcome?)
  • Where are the handoffs? (And which ones create friction?)
  • What capabilities are required at each stage? (And where do gaps exist?)

2. Who owns which decisions?

  • What are the 15-20 most important decisions this organization makes regularly?
  • Who has the authority to make each one? (Not “consult on” — actually decide)
  • Who has veto power? (And under what conditions?)
  • What’s the escalation path when decisions are contested?

3. How is accountability structured?

  • What outcomes is each role accountable for?
  • Do they have the authority to influence those outcomes?
  • How is performance measured? (And does it align with strategic priorities?)
  • What happens when accountability overlaps or conflicts?

4. How does information flow?

  • What data do decision-makers need — and do they have access to it?
  • Where does information get stuck? (In silos, in approval chains, in systems that don’t talk to each other?)
  • How quickly can leaders get the signals they need to make good decisions?

5. What behaviors are rewarded?

  • What does the organization promote, celebrate, and pay for?
  • Does it align with the strategy — or reinforce the old way of working?
  • If someone does exactly what the transformation asks, will they be rewarded or penalized by the current system?
These aren’t theoretical questions. They’re the mechanics of execution. And if they’re not answered deliberately, the organization will answer them by default — usually in ways that preserve the status quo.

How to Design an Operating Model That Supports Transformation

Operating model design isn’t a one-time project. It’s an ongoing discipline. But here’s where to start:

Step 1: Map the Current State (Without Judgment)

Before redesigning anything, understand how the organization actually works today.

  • Who really makes decisions? (Not who’s supposed to — who actually does)
  • Where do things slow down? (Approvals, handoffs, information gaps)
  • What informal workarounds exist? (These reveal where the formal structure doesn’t work)

Use tools like value stream mapping to visualize how work flows — and where it gets stuck.

Step 2: Define Decision Rights Explicitly

Map the 15-20 most important decisions the organization makes. For each one, define:

  • Who decides (the person with authority to commit)
  • Who must approve (veto power)
  • Who must be consulted (input required)
  • Who must be informed (notified after decision)

Use frameworks like RACI or RAPID to make this explicit. The goal isn’t bureaucracy — it’s clarity.

Step 3: Align Accountability with Authority

Every role should have:

  • Clear outcomes they’re accountable for
  • Authority to influence those outcomes
  • Access to the data and resources they need

If someone is accountable for something they can’t control, either give them the authority or change what they’re accountable for.

Step 4: Redesign Incentives to Match Strategy

If the strategy is changing, the incentives must change too.

  • What gets measured in performance reviews?
  • What behaviors get promoted?
  • What does compensation reward?

If these still align with the old strategy, people will optimize for the old strategy — no matter what the transformation says.

Step 5: Test the Design Before Rolling It Out

Before announcing a new operating model, test it:

  • Walk through a real decision using the new model. Does it work? Where does it break?
  • Map a key workflow. Are handoffs clear? Is accountability obvious?
  • Ask people who will live in the new model: “Can you execute in this structure?”

Most operating model failures happen because no one tested whether the design actually works in practice.

The Bottom Line

Transformation stalls when strategy changes but structure doesn’t.

Leaders invest heavily in defining the new strategy. They invest far less in redesigning the operating model — the decision rights, accountability frameworks, incentives, and information flows that determine whether the strategy can be executed.

The organizations that succeed at transformation don’t just announce a new direction. They redesign how the organization works — deliberately, explicitly, and before rolling out the change.

Operating model design is not a detail. It’s the foundation on which transformation either succeeds or stalls.

The question isn’t whether your strategy is right. It’s whether your organization is designed to execute it.

Need to redesign your operating model?

Centroid Strategy helps organizations design operating models that support transformation — clarifying decision rights, aligning accountability, and building the structure strategy needs to execute.

Start a Conversation

Related Insights

  • AI & HR Transformation

Where AI Augments HR — And Where It Doesn’t

Understanding the critical distinction between where AI creates value and where it creates risk. A framework for decision-makers navigating AI in people systems.
  • 7 min read
  • People Analytics

Why Most People Analytics Projects Fail (And How to Fix Them)

Analytics projects fail when they're tool-led rather than decision-led. Learn the five failure modes and the decision-first framework that actually works.
  • 6 min read
  • Organization Development

Why Transformation Stalls — And How Operating Model Design Fixes It

Transformation doesn't fail because strategy is wrong. It stalls because execution lacks deliberate design. Understanding the design gap that most leaders miss.
  • 6 min read

The post Why Transformation Stalls — And How Operating Model Design Fixes It appeared first on Centroid Strategy.

]]>