The first integration chart often shows what will report to the centre. It is less likely to show the judgement that makes the acquired work possible. Equipment can be inventoried, contracts reviewed and job titles mapped. The moment at which an experienced colleague recognises that an apparently routine assignment is different may be harder to capture. Yet that distinction can be part of what the buyer intended to acquire. If integration makes it harder to exercise, a cleaner chart can coexist with a weaker operating proposition.
I learned this through a decision I supported. Following a workshop acquisition, I favoured a central quotation route intended to create consistent commercial treatment. I had not sufficiently examined where specialist assessment needed to enter the proposal. The central process reduced the acquired team's opportunity to distinguish the work before it progressed. It was tempting to describe the resulting difficulty as an implementation issue. That would have protected my original recommendation from the evidence. The arrangement itself needed reconsideration, including the assumptions I had allowed it to carry.
The correction did not require a romantic view of local expertise. An acquired business can have practices that deserve challenge, unclear authority or commercial terms the wider enterprise cannot support. Central visibility may be essential. The commercial team's objection was therefore reasonable: returning every decision to the workshop could preserve inconsistency and make accountability harder. I wanted to answer that objection rather than replace one simplistic model with another. The important distinction was between technical judgement about an assignment and the commercial authority to make a commitment on particular terms.
Our fictional review examined forty-two quotations. Twenty-six concerned routine work and sixteen required specialist treatment; twelve of those sixteen had returned for reassessment. Those figures did not establish the quality of every quotation or the financial outcome of the acquisition. They showed that the uniform route was not handling the reviewed work as its designers had assumed. A useful response needed to identify where specialist review belonged and how it connected to bounded commercial decisions. It could not be reduced to deciding that the centre was wrong and the workshop was right.
## Find the judgement before changing its route
This is why I would begin an integration discussion with the work rather than with reporting lines alone. Follow several assignments through the decisions that materially change them. Ask who recognises a different condition, what evidence they use and where their judgement must be heard before a commitment progresses. The purpose is not to turn the strategist into the technical approver. Qualified owners retain that responsibility. The purpose is to understand the organisational conditions under which their contribution can affect the decision, instead of merely documenting that expertise exists somewhere in the company.
## Keep control and technical authority distinct
The integration team can reasonably question how much investigation the timetable allows. An acquisition team cannot study every exception before introducing common controls. Delaying integration can create uncertainty, duplicate effort and frustrate colleagues waiting for a clear arrangement. I agree that complete understanding is not available at the start. However, that argues for explicit provisional choices and review points. It does not justify presenting a standard process as though it has already established the equivalence of every assignment passing through it. The early model should make its unresolved distinctions visible enough to revise.
The financial account also needs care. In our case, the workshop purchase had cost ₹18 crore. The later correction cost ₹61 lakh, including ₹14 lakh customer credits. The correction expense did not prove that the purchase price had been lost, and the credits were not another sum to add to the total. Nor did the reviewed quotations establish a measured loss of future customers. A leadership account should retain the actual consequence without recruiting a dramatic financial claim that the evidence cannot support. Correcting a material organisational error is significant even without an invented valuation conclusion.
The revised arrangement restored local technical review before specialist proposals progressed, together with bounded commercial delegation and central visibility. It was more complicated to explain than a universal route. That complexity reflected a difference in the work, although it still needed to be managed well. The enterprise accepted a less uniform process because uniformity had not been the only objective of the purchase. We wanted a service capability whose judgement could be used responsibly. A common system should help that capability operate within clear authority, rather than silently replace it with a more convenient classification.
An integration review should therefore examine what the new arrangement makes easier and what it makes less likely to be heard. A central route may improve visibility while increasing the distance between a specialist observation and the person deciding whether a proposal can proceed. The review needs evidence of that consequence, not a general assumption that centralisation is harmful. Equally, an acquired team's preference for its old approach should be examined rather than accepted as proof of superior judgement. The useful discussion concerns particular decisions and the arrangements that allow them to be made competently.
## Retain the cost of correcting your own arrangement
For a board, the question is whether the integration proposition preserves the reasons for acquiring the business while addressing its actual weaknesses. Directors should hear how management has distinguished control, technical assessment and commercial commitment. They should also hear what has changed since the acquisition account was approved. That oversight need not become instruction about individual quotations or repair work. It should establish whether the organisation being built is consistent with the value the institution believes it bought, and whether management can recognise and correct evidence that the arrangement is working differently from the original account.
My own contribution to such a discussion must include the decision I got wrong. I had helped make consistency persuasive before understanding enough about the specialist work it would govern. Farida's challenge mattered because it brought the effect into view through actual proposals. A better public account does not turn her objection into a device that allows me to claim sole credit for the correction. It records the challenge, my responsibility, the commercial counterargument and the narrower arrangement selected. That is more useful than a success story in which integration appears to have improved every part of the acquired enterprise.
The principle I carry forward is to discover the judgement before redesigning its route. An acquisition can require substantial change, and some inherited arrangements may properly end. The institution still needs to understand which capabilities it is trying to preserve and where they become consequential in the work. A tidy process is one possible means, not sufficient evidence of integration success. The strategy account becomes stronger when it explains how qualified judgement, commercial authority and organisational visibility will work together, and remains open to revision when the assignments reveal a distinction the first plan missed.