The Law
Most failed integrations do not collapse in dramatic fashion. There is no single meeting where everyone realises the deal has gone wrong. Instead, value leaks quietly.
Robert Greene’s fifteenth law is one of the most ruthless: crush your enemy totally. Taken literally into M&A, it is the wrong lesson. People are not enemies to be crushed. Counterparties, employees, founders, managers and advisors are human beings whose cooperation often determines whether the deal works.
But if the enemy is reframed, the law becomes useful. In M&A, the enemy is not a person. The enemy is unresolved dysfunction. Indecision. Ambiguity. Competing agendas. Unclear ownership. Two systems pretending to be one. Two leaders pretending to share the same role. A toxic behaviour everyone notices but nobody names.
A decision is delayed because it feels politically sensitive. A difficult conversation is postponed because morale is fragile. Two leaders continue sharing authority because choosing one feels unfair. Separate systems remain because migration seems complicated. Each compromise appears reasonable in isolation. Over time, temporary accommodations become permanent realities, and what began as an attempt to preserve harmony slowly turns into confusion, duplication and resentment.
In M&A, unresolved issues rarely disappear. They simply become more expensive.
Law 14 was about seeing beneath the presentation. Law 15 is about acting once you have seen the truth. Discovery without resolution creates frustration. Resolution is the discipline of confronting the root cause completely enough that the organisation can finally move on.
The M&A Translation
The M&A translation of Law 15 is this: resolve the root cause completely.
Half measures are seductive in transactions because they look diplomatic. Keep both leaders for now. Run both systems for now. Preserve both processes for now. Maintain both cultures for now. Avoid the difficult conversation for now. The words for now are often where future dysfunction begins.
The greatest threat to a transaction is often not the obvious problem, but the one leaders know exists and choose not to address fully. The overlapping systems everyone agrees should eventually be consolidated. The duplicated leadership roles that stay undefined for years. The conflicting compensation structures that reward opposite behaviours. The toxic manager who delivers numbers but destroys collaboration.
People tell themselves they can revisit it later. But later rarely comes. The unresolved issue grows roots while people adapt around it. Eventually the cost of fixing it becomes far larger than the discomfort of having addressed it early.
Temporary harmony can become permanent dysfunction.
Where This Shows Up in a Deal
Law 15 appears wherever a transaction needs a clean decision but receives a compromise that only postpones the real issue.
It appears in diligence, when a red flag is acknowledged but not fully investigated before signing. It appears in integration design, when duplicated roles remain undefined because choosing one leader feels politically costly. It appears in system migration, when two platforms are kept alive long after everyone knows one future system is required.
It appears in culture integration, when leaders tolerate destructive behaviour because the person delivering it is commercially important. It appears in governance, when nobody owns a decision clearly enough to make it stick. It appears in strategic deals, when the buyer has not resolved whether the acquired business is core, adjacent or experimental.
In each setting, unresolved tension becomes a tax on execution. The organisation pays it through duplicated work, slower decisions, internal politics, employee frustration and value leakage.
The Deal Power Map
For Law 15, the power map is a resolution map. The question is not only what the problem is. It is whether the problem has been named, owned, decided, executed and removed from the organisation’s recurring debate.
Five Questions to Map Resolution Risk
Before accepting a compromise as progress, test whether the root cause has actually been resolved.
- 1What is the real issue?
Name the root cause, not only the symptom. Is the issue leadership ambiguity, system duplication, unresolved risk, cultural conflict, incentive misalignment or strategic indecision?
- 2Who owns the resolution?
If everyone owns it, nobody owns it. A hard issue needs one accountable owner with the mandate to finish the decision.
- 3What decision is being avoided?
Look for the uncomfortable choice hidden behind the delay: who leads, which system stays, which culture rule applies, which risk changes the price or which business is no longer strategic.
- 4What would complete resolution look like?
Define the end state clearly. A resolved issue should have a decision, an owner, an execution path, a communication plan and a way to know the debate is finished.
- 5What is the cost of postponement?
Calculate the hidden tax of delay: duplicate work, lost morale, slower integration, customer confusion, leadership frustration, technical debt or future write-down risk.
Cases from the Deal Floor
These cases share one shape. A difficult decision was either confronted cleanly, or postponed until the postponement itself became the problem.
HP–Autonomy2011
Concerns about accounting and valuation that appeared, but were not fully confronted before closing.
HP’s acquisition of Autonomy became one of the most painful cautionary tales in modern technology M&A. The price was high, the strategic ambition was large and the expectations were enormous.
The deeper Law 15 issue is that serious questions around accounting, valuation and business quality were not resolved cleanly enough before the transaction closed. Once the deal was complete, the unresolved issue did not disappear. It became larger, louder and more expensive.
The years that followed brought accusations, investigations, lawsuits and write-downs. The controversy became inseparable from the story of the acquisition itself. The organisation never truly moved beyond the dispute because the unresolved issue became the deal’s identity.
Difficult truths addressed early may save billions later. Difficult truths postponed often return with legal fees, reputational damage and strategic distraction attached.
Problems rarely become smaller through avoidance. Difficult truths addressed early may save billions later.
Microsoft–Nokia2014
A strategic question left open: was the acquired business hardware, software, or both?
Microsoft’s acquisition of Nokia’s devices business was meant to strengthen its position in mobile. But the strategic question at the centre of the deal was never resolved clearly enough: what exactly was Microsoft becoming in mobile?
Was the acquired business a hardware platform, a way to protect Windows Phone, a vertical integration move, a distribution play or a temporary bridge? The organisation struggled to answer that question with conviction after closing.
The result was repeated strategic reversal, confusion and eventual write-down. Thousands of employees were affected as the business was reduced. The painful lesson is that organisations can survive clarity, even painful clarity. They struggle to survive prolonged uncertainty.
A strategy that cannot name what it is becoming eventually becomes a morale problem, an execution problem and a capital allocation problem at the same time.
Organisations can survive painful clarity. They struggle to survive prolonged uncertainty.
Deutsche Bank–Dresdner Bank2000
Who would lead, whose culture would dominate and whose strategy would prevail.
The Deutsche Bank and Dresdner Bank merger discussions show that unresolved issues can kill value before integration even begins. The commercial logic of a combination may exist, but if leadership questions remain unresolved, trust can collapse quickly.
In this case, the core questions were difficult and personal. Who would lead? Whose strategy would prevail? Which culture would set the tone? How would power actually work in the combined bank?
Because those questions were not resolved cleanly enough, the talks collapsed. Years later, the lesson still matters: merger discussions cannot survive indefinitely on polite ambiguity when everyone knows the real decision has not been made.
Leadership ambiguity often destroys value before integration even begins.
Leadership ambiguity often destroys value before integration even begins.
Alcatel–Lucent2006
Two competing cultures and identities, left to coexist rather than reconciled.
The Alcatel and Lucent merger promised global scale, broader capability and stronger competitive positioning. But beneath the logic sat a difficult integration problem: two large organisations with different national histories, leadership styles, cultures and identities.
Those differences were not resolved decisively enough. French and American leadership styles collided. Decision-making slowed. Competing identities survived inside one company rather than being translated into a coherent operating model.
The result was prolonged integration difficulty and a promise never fully realised before Nokia eventually acquired the company. The issue was not that cultural differences existed. The issue was that they remained unresolved long enough to shape the company’s operating reality.
If competing cultures remain unresolved, they eventually compete for control.
If competing cultures remain unresolved, they eventually compete for control.
Compaq–HP2002
A decision, once made, executed without lingering indefinitely in two identities.
The HP and Compaq merger faced enormous opposition. Shareholders disagreed publicly, the debate was intense and the strategic rationale was contested. Before approval, the issue was genuinely disputed.
But once the decision was made, leadership moved to execute. Integration decisions were clarified, structures were defined and the organisation committed to a direction. The execution was not perfect, but it avoided the worse fate of living indefinitely between two identities.
This is the uncomfortable lesson of Law 15. Once a decision has been made, hesitation can become more dangerous than commitment. A company cannot integrate while continuing to behave as if the strategic choice is still undecided.
Organisations may debate intensely before a decision. After the decision, they need enough clarity to execute.
Once a decision is made, hesitation becomes more dangerous than commitment.
The Legacy System Nobody Wanted to Touch
A combined company running two finance systems, with consolidation always agreed in principle and never in practice.
Everyone agrees the systems should eventually be consolidated. There is no strategic debate. The duplicate finance systems create reconciliation work, reporting complexity and inconsistent master data. The issue is obvious.
But the timing never feels right. The migration is painful. The business has other priorities. The integration team moves on. The annual plan pushes the project to next year. The word eventually becomes the hiding place for a decision nobody wants to own.
Five years later, employees maintain duplicate processes, reports require manual reconciliation, errors multiply and no one even remembers why the original decision was postponed.
Technical debt often begins as emotional debt: the discomfort of making a difficult decision is converted into years of operational cost.
Technical debt often begins as emotional debt.
The Two Leaders
Two talented, respected executives with overlapping responsibilities, and a leadership team afraid to choose.
The combined company has two respected leaders for one practical role. Both are talented. Both have political capital. Both teams are watching. Choosing one feels unfair, so leadership creates co-leadership.
At first, the compromise feels diplomatic. Nobody loses face. The announcement sounds balanced. But over time, teams become confused, meetings multiply and employees seek approval from whichever leader supports their preference. Accountability disappears because ownership is split.
Eventually one leader leaves and the decision that had been postponed for two years is finally made. The organisation stabilises, and people quietly ask the same question: why did we not address this from the beginning?
Delayed decisions do not eliminate pain. They distribute it across the organisation.
Delayed decisions do not eliminate pain. They distribute it across the organisation.
The Pattern Behind the Cases
Across these cases, the pattern is not ruthlessness. It is completion.
HP and Autonomy show what happens when red flags are not resolved cleanly enough before close. Microsoft and Nokia show strategic ambiguity turning into write-down and workforce disruption. Deutsche Bank and Dresdner show leadership ambiguity killing a deal before it starts. Alcatel and Lucent show competing cultures becoming a long-running operating problem.
The positive case shows the other side. HP and Compaq faced conflict before the decision, but once the decision was made, leadership committed to a direction. The two practitioner cases show how unresolved systems and unresolved roles become recurring costs that outlive the original integration plan.
The lesson is not to act brutally. It is to finish the difficult work. A problem is not resolved because it has been discussed, postponed, renamed or assigned to next year’s roadmap. It is resolved when the root cause is named, owned, decided, executed and no longer returning as the same debate in a different form.
A problem postponed long enough becomes part of the operating model.
Four Diagnostic Questions
Before accepting temporary harmony as progress, ask four questions.
The Four Questions That Protect Complete Resolution
These questions help expose whether a difficult issue is truly resolved or merely postponed.
- 11. Which decision am I postponing because it is politically uncomfortable?
Separate genuine uncertainty from discomfort. Many unresolved issues survive because the facts are known but the decision is painful.
- 22. Is this issue clearly named, owned, executed and behind us?
If the answer is no to any part, the issue is probably still alive. A status update is not the same as resolution.
- 33. Where have I chosen temporary harmony over a clean resolution?
Harmony created by avoiding the real issue usually turns into confusion, resentment or duplication later.
- 44. What unfinished decision from a past deal is still quietly costing the organisation?
Look for recurring workarounds, duplicate systems, unclear ownership and the debates everyone is tired of having.
The Four Tests of Resolution
A problem is only truly resolved when it passes four tests. If any answer is no, the conflict is still alive, whatever the status report says.
- 1Is the issue clearly named?
Organisations cannot solve problems they refuse to acknowledge out loud.
- 2Is ownership defined?
If everyone owns it, no one owns it. A resolution without a single accountable owner is a wish.
- 3Has the decision been executed?
A decision without implementation is merely an intention with better paperwork.
- 4Has the organisation moved on?
If the same debate keeps resurfacing, the issue was never actually resolved.
How to Apply This at Your Level
Role Lens: Senior, Mid-Level and Junior
If you are a CEO, founder, partner, managing director, board member or investor, your responsibility is not avoiding difficult choices. It is making them thoughtfully and early. People can adapt to clarity, even painful clarity. They cannot adapt to prolonged ambiguity, because there is nothing stable to adapt to.
At every level, Law 15 asks for the same discipline: do not confuse postponement with peace.
The Trap
The trap of Law 15 is mistaking decisiveness for brutality.
Because Greene’s original law is so severe, it is easy to draw the wrong lesson. Some people hear resolve it completely and think it means attacking people, forcing decisions without listening, or treating opposition as weakness. That is not professional M&A leadership. It is insecurity disguised as strength.
Complete resolution does not mean careless speed. It does not mean ignoring facts, silencing dissent or pushing through a decision because ambiguity makes leaders uncomfortable. Some issues need more analysis. Some require legal process. Some require employee consultation. Some require careful sequencing.
The point is not to rush. The point is to finish. Once the facts are clear enough, once the trade-offs are understood and once the organisation needs a direction, delaying to avoid discomfort becomes its own form of harm.
The mature version of Law 15 is disciplined completion. Be humane with people. Be uncompromising with unresolved dysfunction.
Do not crush people. Resolve the dysfunction that keeps people trapped.
The Paradox at the End of Law 15
The paradox of Law 15 is that leaders often delay difficult decisions because they care about people, yet prolonged indecision frequently harms more people than decisive action would have.
A leader avoids choosing between two executives because both are respected. The result is two years of confusion for hundreds of employees. A company keeps two systems because migration is painful. The result is five years of manual work, reconciliation and frustration. A buyer avoids confronting a red flag because the process is late and the deal is politically important. The result is litigation, write-downs and reputational damage.
Short-term discomfort can create long-term stability. Short-term avoidance often creates long-term suffering.
Every acquisition eventually reaches a moment of truth. The organisation must decide what to preserve and what to leave behind: its systems, its leaders, its priorities, its behaviours and its future identity. Those choices are rarely painless, yet the cost of postponing them is usually far greater because unresolved tensions do not stay neutral. They consume attention, divide teams and quietly drain the value the deal was meant to create.
The objective is not to defeat people. It is to resolve the issues standing between intention and execution. Because the problems you refuse to confront today often become the crises that define tomorrow.
The leaders who create lasting value are not necessarily the most ruthless. They are the ones courageous enough to finish the difficult work they begin.
Resolve It Completely
In M&A, resolve the root cause completely. Half measures create lasting dysfunction, and the problems you refuse to confront today become tomorrow’s crises.
Because the problems you refuse to confront today often become the crises that define tomorrow.
Before your next meeting on a live deal, ask yourself:
- 1.Which integration decision am I postponing because it is politically uncomfortable rather than genuinely unclear?
- 2.Is this issue clearly named, owned, executed, and behind us, or only one of those?
- 3.Where have I chosen temporary harmony over a clean resolution?
- 4.What unfinished decision from a past deal is still quietly costing the organisation?