Org Design in M&A: Why Most Redesigns Fail

A senior leader pulled me aside three months into a merger. He looked the way people look when they’ve been smiling in meetings for twelve weeks while watching their team dissolve. “We’ve been talking about the org structure for twelve weeks,” he said. “Everyone has opinions. Nothing is decided. People are starting to leave.”

I’ve seen this movie before. It ends badly. Prolonged ambiguity is more damaging than an imperfect decision, because imperfect decisions can be corrected and ambiguity just compounds. The best people, the ones with options, don’t wait around while executives debate reporting lines for the third month running. They find clarity somewhere else. Usually at a competitor who made their org decisions in week three.

McKinsey’s research says less than 25% of organizational redesigns meet their objectives. Almost half run out of steam before completion. Those numbers track with what I’ve seen in the field. Most org design efforts fail not because the target structure is wrong, but because the process of getting there destroys value faster than the new structure can create it. You can have the perfect org chart. If it took six months to design, the people who were supposed to fill it are gone.

Design decisions, not boxes

The instinct is to start with structure: who reports to whom, how many layers, what goes in which function. Org charts are concrete. They feel like progress. You can put them on a slide and present them to the steering committee and everyone nods because it looks like something was accomplished.

But structure is the easy part. Anyone can draw boxes. The hard part is designing how decisions get made.

Before drawing any boxes, we map the 20-30 most important decisions the organization makes. Who sets pricing? Who approves capital expenditure over $X? Who decides which features make the roadmap? Who resolves conflicts between sales and operations when sales has promised something operations can’t deliver? (This happens every quarter. Plan for it.) For each decision: who has input, who decides, who needs to be informed, how quickly must it happen.

This exercise almost always surfaces problems that a structure change won’t fix. Decisions are slow because of culture, not reporting lines. Accountability is unclear because leadership hasn’t made hard choices about priorities, not because the org chart is wrong. Information doesn’t flow because systems are broken, not because boxes are in the wrong places.

Sometimes the answer is: structure isn’t actually the problem. The presenting complaint is “our org doesn’t work,” but the root cause is executive dysfunction, or process gaps, or technical debt that makes everything slow regardless of who reports to whom. A new structure just rearranges the dysfunction. Like reorganizing the deck chairs, except the deck chairs cost $2M in consulting fees.

When structure genuinely is the constraint, the decision map tells you what the structure needs to enable. You design for the work, not for political accommodation. This is also where HR integration planning intersects: the org design drives workforce planning, retention decisions, and synergy capture. Get the structure wrong and everything downstream breaks.

The decision map

Most org design frameworks are prescriptive. Galbraith’s star model. Bain’s RAPID framework. Deloitte’s seven practices. They start with what should be: here’s the target operating model, now work backward to the people. The problem is that prescription assumes diagnosis. And in post-acquisition organizations, the diagnosis is almost always wrong, because the people describing the symptoms are the same people whose power is at stake.

Henry Mintzberg’s insight cuts deeper: structure doesn’t follow strategy. Structure follows power. Your org chart is a photograph of who won the last political fight, not a blueprint for how work should flow. A redesign that starts with boxes will produce new boxes that encode the same power dynamics. It will look different. It will work the same.

The decision map starts with what is. Take the 20-30 critical decisions surfaced in the exercise above and run them through five columns:

Who decides today. Not the person on the org chart. The person who actually makes the call. These are often different people, and the gap between them is the first structural insight.

Who should decide. Based on proximity to information, speed requirements, and accountability for outcomes. This is where the design conversation begins.

Speed required. Some decisions need to happen in hours (competitive pricing, customer escalations). Others can take weeks (annual planning, capital allocation). The structure must match. A centralized approval chain for decisions that need to happen in 48 hours is a structural failure, regardless of how clean the org chart looks.

Structural blocker. Why the decision doesn’t flow at the speed the business requires. The blocker is usually political: dual authority, unclear escalation paths, legacy reporting lines that serve someone’s empire rather than the work. Naming it explicitly is uncomfortable. That discomfort is diagnostic.

Structural fix. What would have to change, in reporting lines, governance, or authority allocation, to remove the blocker. This column is the hardest to fill honestly. If the fix were obvious, someone would have implemented it already. Most structural fixes involve trade-offs that aren’t visible from inside the organization: giving one leader authority means taking it from another. That’s a conversation most executive teams avoid until the decision map makes avoidance more expensive than resolution.

We typically organize decisions across five domains: commercial, operational, people, financial, and technology. The domains are flexible. The columns aren’t.

The map reveals patterns no org chart can show. When seven of your thirty critical decisions are stuck at the same level, that’s a span-of-control problem disguised as “a culture of slow decisions.” When decisions in one domain flow quickly and another stalls, you don’t need a full redesign. You need a targeted fix in a specific place. The map tells you where.

Example: pricing authority after a $1.2B acquisition.

Before the map: pricing decisions took three weeks. Three people believed they owned the call: the acquirer’s pricing director, the target’s commercial VP, and the new combined P&L leader. Each escalated to their own chain. The steering committee discussed pricing authority twice without resolving it, because resolution meant telling one of three senior leaders they didn’t have the authority they assumed they had.

The map made the problem structural rather than personal. “Who decides today” had three names. “Speed required” said 48 hours (competitor bids expire). The blocker was matrix overlap with no tiebreaker. The fix: pricing sits in commercial under the P&L owner. The pricing director keeps an advisory role. The VP gains explicit authority and explicit accountability. Three weeks became two days. Not through a reorganization. Through a single structural decision the map forced into the open.

Download the decision map canvas to run this exercise with your leadership team. It’s organized by the five decision domains with pre-formatted columns. The “structural fix” column will be the hardest to fill. That’s by design.

Stop benchmarking

Clients often ask what best-in-class companies do. What’s the right span of control? How many layers should we have? Should we centralize or decentralize this function? They want a number. Preferably one from a company they admire.

There’s no right answer. Optimal structure depends entirely on strategy, competitive dynamics, talent, and culture. A centralized model that works beautifully for one company would destroy another. Amazon’s org structure would kill a 500-person specialty manufacturer. The specialty manufacturer’s structure would paralyze Amazon. Benchmarking tells you what someone else did. It doesn’t tell you what you should do.

Fortune’s Most Admired Companies have nothing in common structurally except flexible operating models. The implication is uncomfortable for anyone who wants a template: you need to design for your specific context.

I use a simple heuristic: optimize for your bottleneck. If speed is the constraint, flatten the structure and push decisions down. If consistency is the problem, centralize and standardize. If innovation is lagging, create cross-functional teams with dedicated resources. If accountability is unclear, simplify reporting lines and eliminate matrix overlaps. The question isn’t “what’s the best structure?” It’s “what’s constraining us and what structure alleviates that constraint?”

Move fast on leadership

Every week without an org decision costs you someone you wanted to keep.

Week one, they’re patient. Week four, they’re updating LinkedIn. Week eight, they’re gone.

This isn’t just anecdote. A UCL study found that uncertainty is more stressful than guaranteed bad news. People waiting for a 50% chance of an electric shock showed higher stress than people who knew they’d definitely get shocked. Your employees aren’t getting electric shocks, but they are checking their phones under the table during the all-hands meeting where someone says “we’re still working through the structure” for the fourth consecutive month.

Certainty, even painful certainty, is easier to process than limbo. Your best people aren’t afraid of a tough new structure. They’re afraid of twelve weeks of “we’re still working through it.” They can handle “your role is changing.” They cannot handle “we’ll let you know.”

Our rule: L1 decisions within 4 weeks of close. CEO directs named and in place. (For the full integration timeline, see what actually happens after the deal closes.) L2 follows shortly after. Not twelve weeks of debate. Never twelve. This is why the first 100 days matter so much: the window for org decisions is smaller than people think, and it’s closing faster than the PowerPoint is being finalized.

Separate structure from people

One of the most common failure modes: designing the structure around the people you have rather than the work you need done.

It’s understandable. You know Sarah is great and you want to keep her, so you create a role that fits her skills. You know Tom is difficult but connected, so you design around him rather than through him. Before long, the org chart is a political accommodation rather than a functional design. Every box exists because of a person, not because of a need. The structure is a portrait of the current team, not a blueprint for the future one.

Better approach: design the structure first, then assess people against roles. This is harder politically but produces better outcomes. It also surfaces talent gaps honestly rather than papering over them with creative titles. (“Director of Strategic Initiatives” is not a role. It’s a holding pattern.)

The conversation with Sarah becomes: “Here’s the role we need. Here’s what it requires. Do you want it? Can you grow into it?” That’s a respectful conversation. It treats her as an adult. The alternative, creating a role that doesn’t quite fit because you’re afraid to have the hard conversation, serves no one. Not the organization. Not Sarah. Especially not Sarah, who deserves to know where she stands.

Don’t reorganize your way out of a performance problem

If someone isn’t working out, the restructure won’t fix it. Deal with performance directly.

I’ve seen organizations use reorgs as a way to move problem performers around rather than address them. The hope is that a new structure, new boss, new team will somehow solve the issue. Like moving someone to a different seat on the bus will make them a better driver. It won’t. The problem follows the person.

The restructure should be about structure. Performance management should be about performance. Conflating them makes both worse, because now you’ve used a $5M organizational change to avoid a single difficult conversation.

The meta-question

Before launching any organizational redesign, answer this: “Is structure actually our problem?”

Often, the symptoms that trigger redesigns (slow decision-making, poor collaboration, unclear accountability) have root causes that structure won’t fix. Leadership behavior. Talent gaps. Misaligned incentives. Cultural dysfunction. Addressing those issues is harder than drawing new boxes, which is exactly why organizations reach for structural solutions. A reorg feels decisive. Having a hard conversation with the CHRO about why decisions take six weeks feels uncomfortable. One of these actually fixes the problem.

Sometimes structure really is the constraint. But verify before assuming. The cost of a misdiagnosis is six months of disruption, your best people’s patience, and a consulting bill that would make your procurement team weep.

Related Reading

• 100-Day M&A Integration Plan: The Roadmap
• HR Integration and Workforce Planning: The First 90 Days
• Why 70% of Transformations Fail (It’s Not Strategy)
• Retention Bonus Strategy in M&A: When to Pay and When to Talk
• Carve-Out Readiness Checklist: 30 Things That Get Missed

---

If you’re contemplating an organizational redesign, or recovering from one that didn’t work, let’s talk about how to approach it differently.