peopleanalyst

use cases · M&A integration

The deal closed, and the team you bought is quietly coming apart

The deal closed and the team you bought is coming apart. It's not culture clash — it's two definitions of 'good.'

For who

Acquirer CEOs, COOs, and CHROs watching synergies stall and acquired talent leave

What it finds

That the binding constraint is Alignment — conflicting reward systems and decision rights, not vague 'culture.'

What you get

A reconciliation target before retention bonuses and a forced reorg burn the capability you bought.

Binding constraint

alignment'Culture clash' is a label, not a diagnosis. The binding constraint is Alignment: two organizations carry different operating definitions of 'good' — what gets rewarded, who decides, what success means — and forcing the acquirer's system on without reconciling them destroys the very capability you paid for. Retention bonuses keep bodies who've already mentally checked out; the lever is reconciling decision rights and what's rewarded, fast and explicitly.

The situation

Post-close, the acquired team is underperforming and its best people are leaving; the synergies in the model aren't materializing. Leadership calls it 'culture clash' and reaches for the usual moves: retention bonuses, a reorg, and forcing the acquirer's processes/tools onto the acquired team to 'get everyone on one system.'

How the walkthrough goes

  1. 01customer-situation

    The deal closed — and the team you bought is quietly coming apart.

    The acquired unit is underperforming, its best people are leaving, and the modeled synergies aren't showing. The read is 'culture clash.'

  2. 02problem-cost

    Retention bonuses, a reorg, and 'get everyone on one system' are on the table.

    All of it treats the symptom. If the fault line is something else, you spend the integration budget and still lose the capability you bought.

  3. 03insight

    'Culture clash' is a label. The fault line is two definitions of 'good.'

    The binding constraint is Alignment: the two orgs reward different things and decide differently. Forcing the acquirer's system on without reconciling that destroys the very capability you paid for.

  4. 04desired-outcome

    Realize the synergies you modeled — keep the capability, not just the bodies.

    Reconcile decision rights and what's rewarded, explicitly and fast, so the talent the deal was for actually stays and performs.

  5. 05product-path

    Performix names the binding constraint across both sides.

    Protected feedback + CAMS, run on acquirer and acquired, shows where the integration is actually breaking — here, Alignment.

  6. 06proof

    Retention bonuses don't predict staying. Alignment does.

    In the data, bonus receipt doesn't separate stayers from leavers; the alignment/decision-rights items do.

  7. 07risk-reversal

    Honest by construction.

    Protected feedback + minimum-group-size gate on both sides; people can name what's broken in the integration without it being traced back to them.

  8. 08next-step

    Diagnose the integration before the bonuses go out.

    One read on why the team's coming apart — before you spend on retention and a reorg that keep bodies, not capability.

Grounded in the research

Walkthrough data is composite and clearly labeled — shaped from the research to show the real shape of the finding, not a named client.

Realize the synergies you modeled by reconciling reward systems and decision rights instead of papering over it with bonuses and a forced reorg — the decision-error avoided is integration spend that retains bodies, not capability, and burns the talent the deal was for.