Merger Integration: One Frame for Two Ways of Running a Business

Only one leader in four calls their transformation a real success.

It didn't have to be that way. The other three were not fools. Some of those changes might have landed if both sides had steered by one control system instead of two habits.

Picture day one hundred after the deal. Two finance teams. Two dashboards. One weekly meeting where the first hour goes on whose revenue figure is the real one.

Here is the irony. The deal team valued the other company to the last decimal. Nobody agreed how the joined company would read its own numbers on a Monday.

The villain is not either team. It is the fight over whose method wins, while the business waits.

There is a calmer road. The Jirgenson Model is a control system for goals, numbers and plans. It is scientifically proven to work (the record on Zenodo). It is new, so it could not help the companies behind these numbers. Now it can help yours.

Merger integration needs one frame, not one winner

Half of big mergers destroy value. Fewer than one in five create any.

That number did not have to be so grim. Behind each merger are people who wanted it to work. Some of those deals might have kept their value if both halves had read the same three lines every week. With a shared control system, the odds could look different.

Look at the usual move first. As an illustration: the buyer runs OKR, the bought company runs EOS. The buyer's method wins by rank. The other half's meeting rhythm, scorecards and habits go in the bin, and their best people go quiet.

Now the model's move. Keep both methods. Give each one its place in a single frame.

Every familiar method already fits a slot in that frame:

Read the table as a peace treaty. Neither half has to give up its method. Both halves agree on the frame those methods serve.

How to avoid the value loss: before any reorganisation, agree on one goal list, one state and one way to read the gap. Then let each method do the job it is best at.

The one-frame sheet, filled in

A household is the smallest merger there is: two people, two habits, one account. Emma and Paul show the tool from start to finish.

Their income is €4,000 a month. Six months ago they spent the same. Over the last quarter their spending rose by 10%, to €4,400. Their savings stand at €2,000. At first they quarrelled. Then they sat down with one sheet.

1. Write one goal in one unit. Emma and Paul: a reserve of at least 3 months of expenses.
2. Take the state from records, not memory. They used three months of bank statements. The trajectory: spending rising, income flat.
3. Calculate coverage: reserve divided by expenses per period. 2,000 / 4,400, about 0.45 months. Against a goal of 3, that is red.
4. Calculate time to depletion: reserve divided by net outflow. 2,000 / 400 = 5 months.
5. Build three scenarios before you touch a lever. Change nothing: the savings run out in 5 months, sooner if spending keeps rising. Cut subscriptions and eating out by €180: the outflow drops to 220, and the savings last about 9 months. Do that and add a side job worth €300 a month: a surplus of 80 every month, and the savings grow.
6. Start with one lever, so you can see its effect. They chose the third scenario. They began with the cuts and added the side job a month later.

Two of those numbers are easy to confuse. Coverage is 0.45 months. Time until the money runs out is 5 months. They measure different things, and you need to watch both.

For a merger, run the same sheet on each half's cash, then on the joined company. Same formulas, same units, one result on the table. The argument moves from "whose number" to "which lever first".

Why change fails across fields: three houses, one formula

A house can be wood, brick or glass. Every house still has a foundation, walls and a roof. The same two formulas work in all of them.

Three tasks, one formula, different units. That is why two merged companies can share a frame even when one sells software and the other pours concrete.

How to avoid the trap: never let each half invent its own definition of "months of cash". Write the formula once, on the same sheet.

Digital transformation failure: the Phoenix lesson

Canada's government pay system cost sixteen times its budget.

It didn't have to reach that multiple. The people inside that project deserved a better instrument. A budget read every month as goal, state and error might have raised the alarm far sooner. With a control system, the curve could have looked different.

Use the same frame on any large rollout. The goal is the approved budget and the delivery date. The state is what has been spent and delivered, taken from records. The error is the gap.

Then apply the depletion formula to the budget. Divide the money left by the monthly spend. That gives the months until the budget runs out. Put it next to the months of work still ahead. When the first number is smaller, you have found the overrun while it is still a forecast.

How to avoid it: no new phase starts until the budget's time to depletion is on the same page as the work left.

What six more months of two languages cost

Inaction has a price, and the numbers above show it.

Take Emma and Paul without the sheet. They lose €400 a month. Six months of that is €2,400, more than their whole €2,000 of savings. The money is gone in month five, and the hole keeps growing.

Take Andrew's shop at a 9% margin. The reserve goal needs 15.2 months, so it arrives at month 16. Every month spent arguing about the reading is a month the reserve does not grow.

In a merger, the same arithmetic runs with more zeros. Six months of two dashboards means six months of decisions made on the wrong number, or not made at all.

And the human cost: the kitchen-table quarrel, or the Monday meeting, that keeps coming back because nobody shares a frame.

"Our two companies are too different"

They are different in content. They are the same in structure. A family budget, a coffee shop and a schoolboy's bicycle fund all fit three lines: goal, state, error.

Elena, a freelance designer, runs her business alone. Her goal list holds three rows: income, the share of her largest client, her hours. The frame that fits her fits a joined company of any size. Only the units and the number of rows change.

The model does not replace OKR, EOS, BSC, PDCA, TOC or MBO. It sits above them and answers the question they leave open: what matters more when everything is on fire.

Where the one-frame sheet stops

The sheet treats the symptom: both halves now read one goal, one state and one gap.

The cause runs deeper. You have described where you stand. You have not yet tested whether the goal can be reached from today, with the resources you have. And when three numbers turn red in one week, nobody knows what to save first.

Two steps close that gap.

• The backward move. The route from the goal back to this week, with resources checked at every step. Chapter 15.
• Zone thresholds and the red protocol. Where yellow turns red, and the order of rescue when several numbers are red at once. Chapter 4.

The frame is the base of one loop: goal, state, error, levers, plan, forecast. Without the next two steps, it shows you the gap. It does not yet tell you which route closes it. For the eight stages every change passes through, read business transformation.

Two choices for the next integration meeting

You have two choices. Spend another Monday arguing whose figure is right, while the cash keeps moving. Or put both halves on one sheet: goal, state, error, two formulas, three scenarios.

The sheet gives you one reading. The backward move and the red protocol turn that reading into a route and an order of action.

Picture next Monday. Both finance leads look at the same line, and the first hour goes on the lever, not the number.

Test the logic for free: Chapter 1, with the refusal test. Or get the complete control system on Kindle now, on Amazon. The full method comes as a Kindle book, from the first goal to the forecast.

Published research

It is scientifically proven that the Jirgenson Model works. The published experiment, its record and its data:

• Zenodo (DOI): 10.5281/zenodo.23964934
• Hugging Face: E5 Jirgenson Model blind test
• Kaggle: E5 blind test dataset
• GitHub: experiment folder
• Wikidata: dataset Q142022866, author Q141981336
• ORCID: 0009-0001-3034-3552