Organization Design in M&A: How People Intelligence Helps the New Structure Deliver the Deal

Last reviewed: October 30, 2026.

Short answer: Organization design is where an M&A deal thesis turns into roles, reporting lines and decision rights. Deloitte argues that many deals fall short "because the future organisation was never designed to deliver it." People intelligence strengthens that design with structured, team-level data on how the combined leadership team actually makes decisions, hands work off and escalates. Used well, it shows which decision rights, interfaces and interim structures are likely to hold under integration pressure and where teams will need support. Capture a baseline before or at close, map the findings to value creation plan (VCP) line items, and re-measure at the design review points. It is never a tool for choosing, cutting or scoring individuals.

What does Deloitte say organization design has to do in a deal?

In "From Deal to Delivery: How Organisation Design Drives Value in M&A" (Deloitte UK, 30 October 2026), Helen Carney, Megan Sharpe and Nina Fishta set out a practical framework for organization design (OD) in transactions. It's one of the clearest short pieces on the topic I've read this year, and it's worth reading in full.

Their core points, in brief:

• OD in M&A is role-led. The design should establish capabilities, accountabilities and structure "before considering the individuals who may fill those roles."
• It differs from business-as-usual change. Timelines are fixed and commercially driven, and design decisions are often made before the future leadership team is in place. So the people shaping the organization may not be the ones accountable for leading it.
• It often runs in two states: an interim structure that keeps Day 1 delivery and accountability clear, and an end-state structure aligned to the target operating model.
• Three challenges need the most attention: balancing pace with quality, over-reliance on legacy structures, and keeping focus on culture and people.
• Stakeholder engagement, iteration and reliable people data strengthen the process. Leaders support designs they helped shape, and "major decisions made using incomplete data should be revisited."
• Success is measured beyond structure: benefits realized, critical skills retained, minimal disruption, a maintained employee experience, and productive relationships with employee representative bodies.

I agree with all of it. My addition is about one phrase in particular: "reliable people data."

What kind of people data does org design actually need?

Deloitte is right that people data is "a critical enabler" and "one of the most challenging aspects of a transaction." They focus on the hard, necessary part: multiple HR systems, different grading structures and inconsistent role definitions that make a single view of the workforce difficult.

That's the structural layer. It tells you who sits where, at what grade and cost. It doesn't tell you how the combined leadership team will make decisions together once the new lines are drawn.

So I'd separate the people data an OD program needs into three layers:

Most deals are reasonably good at the first layer, eventually. Deloitte rightly adds the third. The middle layer is the one that usually stays a matter of instinct, and it's where many design decisions quietly succeed or fail.

Where does people intelligence strengthen the design?

Not in choosing people. In shaping the design that people will work inside. Here are five places where I think team-level behavioral evidence changes the quality of the design.

1. Decision rights

Org charts show reporting lines. Value is delivered through decisions. A design that gives a combined commercial team joint ownership of pricing assumes the two sides decide at a similar speed and escalate in similar ways. If the baseline shows one team decides by consensus and the other by a single owner, that's a design input. You might write the decision rights more explicitly, name a tie-breaker, or set a faster escalation path for the first months. For why this gap opens in the first place, see why alignment breaks during M&A integrations.

2. Interfaces and hand-offs

Spans and layers are structural choices, but most integration friction lives at the interfaces: between functions the synergy model assumed would work as one. People intelligence can show where coordination patterns between teams look strained. Those are the hand-offs that need a clearer process, a shared forum or a dedicated integration owner. The same logic applies to the hand-off between the deal team and the integration team, covered in The Handover Problem.

3. The interim structure

Deloitte's two-state model is practical. The interim structure carries Day 1 continuity while leadership and systems are still settling. It's also the structure most likely to rely on informal workarounds. A team-level read at or just after close helps show where interim accountability is clear in practice, and where people are working around it.

4. Legacy structures

Deloitte warns that leaders "naturally gravitate towards familiar organisational models." Behavioral data makes that pull visible after the new structure is live. If the new chart says one thing and the decision patterns still follow the old company lines, the design hasn't landed yet. That's a signal to invest in operating rhythms and leadership alignment, not to redraw the chart again.

5. How the top team operates once appointed

Org design often runs alongside top-team appointments, and this is where the line has to be firm. People intelligence should not decide who gets a seat. That's the job of a fair, role-led selection process, and we covered it separately in Choosing the Leadership Team After a Merger. What team-level data can do, once the team is in place, is help it design how it works together: which forums decide what, where alignment is still thin, and where coaching or facilitation would help.

What should people intelligence never be used for in org design?

This deserves its own section, because organization design in a deal is where jobs, reporting lines and appointments are on the table. People intelligence in this context only works if everyone can trust how it's used. The ground rules at HumanaQ are:

• Team level only. Reads cover groups of five or more people, and nobody is named in the output.
• Never for selection, retention, pay or performance decisions. It informs the design and the support around it, not decisions about individuals.
• No flight-risk predictions. It doesn't forecast who will leave.
• Patterns, not proof. Findings describe patterns associated with outcomes, not causes. They are one input alongside financial, operational and stakeholder evidence, and human judgment decides.

These rules also make the data more useful. Leaders are more open when they know the output can't be used against them, and that openness is what gives a team-level read its value.

How do you build people intelligence into the OD program?

Deloitte's advice on iteration gives the sequence. They recommend "formal review points" so teams can reassess decisions as new information emerges. People intelligence fits that rhythm:

1. Baseline before or at close. Capture how the combined leadership team works before integration habits set. Without a baseline, later reviews have nothing to compare against. The window between signing and close is covered in The Pre-Close Window.
2. Map findings to the design and the VCP. Each finding should point to a specific design choice (a decision right, an interface, an interim accountability) and to the VCP line item it affects, with a named owner and a check date.
3. Feed the design workshops. Deloitte stresses involving leaders early through design workshops and validation sessions. Team-level findings give those sessions a shared, depersonalized starting point that's about how the team works, not who is right.
4. Re-measure at the review points. Re-read the team at the same points where design decisions are revisited, for example Day 100, Day 200 and Day 365, so you can see whether the design is landing.
5. Report leading and lagging indicators together. Behavioral movement shows up before benefits realization does. Put both in front of the steering committee.

How should OD success be measured?

Deloitte lists the structural design metrics many programs set up front: grade mix, leadership ratios, workforce cost targets and reporting line structure. It notes that "structural metrics alone rarely tell the full story," and recommends adding engagement and sentiment tracking.

I'd add one more lens between the two. Structural metrics tell you whether the organization was built as designed. Sentiment tells you how people feel about it. Team-level behavioral re-measurement tells you whether the leadership team is actually operating the design: deciding where the decision rights say it should, handing off where the interfaces say it should, and escalating where it should.

Deloitte closes with three questions every OD program should ask. One of them is: "Where are the most material people, capability and execution risks in the proposed structure?" That question is hard to answer from an org chart alone. People intelligence is designed to help answer it with evidence rather than instinct.

For where the people question sits across the whole transaction, see The 8 Stages of an M&A Deal.