An integration office gets stuck at the same point every time: the number of decisions grows faster than the capacity to make them. In week one, the list of open items is manageable. By around week four, that list is often no longer manageable without structure. The question is not whether an integration office will exist, but how it stays workable once the real volume of decisions, dependencies, and signals starts coming in.
The plan is usually not the problem. The problem is that every decision demands attention at the moment it is made, and those moments pile up. Without a fixed way of sorting decisions, everything lands with the same people, in the same meetings, with the same lack of clarity about what is urgent and what can wait. An integration office running on improvisation works for the first two weeks. After that, it becomes the place where decisions slow down instead of where they get made.
The order in which decisions are made determines how much room remains later. A decision that blocks other decisions belongs earlier in line than a decision that stands on its own. That seems obvious, but in practice, sequence is often determined by who shouts loudest, not by what is most decisive. One way to break that pattern is to sort decisions by cost of uncertainty: what does it cost to delay a decision, expressed in the options that close off as a result. That is not an exact science, but it forces a ranking that goes beyond who sounds most urgent.
The same applies to the distinction between what does and does not belong in the first hundred days. Not every decision needs to happen now. Some decisions are important but not time-sensitive, and those can be deliberately parked — with an owner who makes sure they are not forgotten. Without that owner, parked decisions disappear quietly, and come back later as a crisis. Which topics can wait and who remains responsible for them is described in what can wait until after Day 100.
Most delay in an integration office comes not from bad decisions, but from decisions waiting on each other without anyone having noticed. A system choice locked in before the organizational structure is determined, or a staffing decision waiting on a system choice that in turn waits on a contract date. Those chains are rarely visible until they get stuck. Mapping which dependencies block the rest, before the planning is locked in, is one of the few ways to spot that delay early instead of only once the deadline has already been missed — see which dependencies block the rest.
An integration office that stays workable has an explicit answer to the question of who watches over which decision — not who executes it, but who signals when it gets stuck or comes in too late. That distinction is often skipped, with the result that no one notices the gap until it already hurts. Which decisions belong in the first hundred days and who oversees them is worked out in which decisions belong in the first hundred days and who oversees that. The same logic applies to the office itself: who watches that the office stays workable as volume increases is addressed in how do you keep the integration office workable and who oversees that.
Every week without clear sequencing and without oversight is a week in which decisions pile up without capacity growing along with them. That costs not only time. It also costs the moment at which people still trusted that there was a plan. If the integration office gives the impression that it is no longer keeping up, the organization's attention shifts from integrating to surviving, and that is hard to reverse.
Even when keeping the integration office workable, the question remains whether the component being discussed should be combined at all. Not every process, system, or team gains value by being integrated. Sometimes it is better to let something exist separately, or integrate it later, rather than fast-tracking it simply because the office is already running. That question should keep coming back, not as an exception but as a standard part of every decision.
The generators for the synergy baseline, Day 1 plan and Day 100 plan, and the integration office as a tool for benefit tracking, dependencies, and the decision log, are under development. There is no completed engagement to point to — the tool structures the decisions, it does not prove experience. Anyone who wants to use this once it becomes available can sign up for the waiting list.
Anyone who, during the first hundred days, also looks at the staffing of the integration office itself often runs into the same question: how much of the work now resting on people — tracking statuses, recording decisions, flagging dependencies — is actually task-bound work that can be taken over. FTE TO AI's work scan calculates, per task, what portion of it can be taken over by AI, giving a picture of where capacity is freed up before the integration office has to operate at full strength.
Vraag maar wat er op Day 1 moet staan, of wat integreren juist kapotmaakt.
Answers come from this site’s knowledge base. Not tailored advice, and not a scan of your company.