A leadership team says: "we are going to integrate this acquisition." Everyone nods. And yet the CFO means something different from the HR director, and the operations director means something different again from the CIO. One reads integration as a shared ERP, another as a shared customer view, a third as an organizational chart in which no one holds the same position twice. As long as those words have not been broken down into what the organization must be able to do, the ambition is an intention and not a mandate.
To make an ambition measurable, it must first be laid down in layers: a vision (why this acquisition, what future picture justifies the effort), a vision state (what the integrated organization substantively looks like), a target (which milestone counts as success) and a target state (what situation must factually exist by that date). Only once those four layers are in place can it be tested whether the organization is ready for it.
An integration ambition voiced today often tacitly assumes that part of the work will be done by AI: merging customer data, reclassifying contracts, drafting first-version process documentation, flagging duplicate suppliers. That is a different ambition from integration without that assumption, even though leadership uses exactly the same sentence.
For every task within an integration process, one of three situations applies. AI can take over the task, such as matching article codes between two ERP systems. AI can do part of it with human oversight that approves or rejects with reason, such as a proposal for harmonized job profiles that a manager reviews. Or it remains human work, such as the conversation with a key customer worried about continuity. Which tasks fall into which category differs per company: it depends on the quality of the underlying data, on how many exceptions a process has, and on whether people have already been trained to assess AI outcomes rather than produce the work themselves. Companies that already do the latter see integration work shift faster; companies where oversight still needs to be set up see the ambition stall on exactly that point.
Readiness for an integration ambition is not one question but eight. Among others: is the data of both organizations comparable enough to be merged, are decision rights over the new combined entity assigned to roles rather than to individuals, does a process exist to have AI proposals for process harmonization approved, and has capacity been freed up to actually carry out that approval. Other dimensions concern culture, leadership, technical infrastructure, and the ability to measure progress rather than assume it. On each dimension the organization may be far advanced or barely started, and that picture is rarely equal across the eight dimensions.
After that come five confidence gates: moments at which it is explicitly established whether the confidence to proceed is present, before the next phase of the integration begins. A gate that is skipped because the schedule is under pressure is usually the point where the integration stalls six months later.
Readiness remains abstract until it is translated back into who does what. A target state such as "one consolidated customer view" requires a role that owns data quality, a decision right over which source takes precedence in case of conflicts, and an agreement on who reviews AI-generated matches before they enter the system. Without that translation, the ambition remains a wish on a slide. With that translation, everyone involved knows what is expected of them, and where the line lies between what they decide themselves and what they escalate.
Where this touches on who continues to hold which position within the new organization, separate legal requirements apply to decisions about personnel; this page is about the readiness of the work, not about those decisions.
An integration that has succeeded is not recognizable from a press release but from capacity: the number of hours freed up because processes are no longer performed twice, and the question of whether that freed-up fte capacity is actually deployed on the work for which the acquisition was once justified. That can only be established if the target state was defined sharply enough beforehand to be tested afterward. The same applies to related ambitions: whether flattening the organization actually resulted in fewer handover moments, whether becoming less dependent on key figures has become measurable in who can now carry out a process even without that one person, and whether early signals that a change is taking hold were already visible before the annual report appeared.
The question underlying all of these ambitions — which work in this company can genuinely be taken over by AI, and which work remains oversight or human work — is answered per task with the work scan from FTE TO AI. For the ambition itself, a different step comes first: checking whether it is still a document or already a way of working, because without that step a strategy often remains stuck in a document rather than in behavior, just as with the question of whether the organization has already started working in a more customer-focused way or only claims to want to.
Anyone who wants to know where their own organization currently stands can take the free readiness check: eight short questions, one per dimension, resulting in a picture of where you are furthest along and where the most work still lies. The full ambition assessment, with the four layers, the five confidence gates and the translation back into roles and decision rights, is under construction.
Vertel wat u wilt bereiken, dan kijken we samen wat daarvoor moet staan.
Answers come from this site’s knowledge base. Not tailored advice, and not a scan of your company.