One standard tool is imposed on every unit by a central function, citing cost and consistency, and the strongest units lose capabilities that gave their leaders influence.
Borderline: whether this move is justified depends on the situation, and only the person in it can judge.
An example
Five merchandise planning systems, the new chief information officer of a department store group concluded, were costing too much in licenses and producing numbers nobody could compare. She chose one system for all divisions, the one home goods already ran, because it was the cheapest to scale and the easiest to train on. She knew the specialty apparel unit's homegrown tool was better at fast reorders, said so at the steering committee, and estimated the cost at about a point of margin in that unit. The mandate came with free licenses and a central migration team. She refused all thirteen exemption requests on the same grounds, so no division could say it had been singled out, and two division heads spoke for the plan. Eighteen months later the group had one set of planning numbers and a license bill forty percent lower, and apparel's margin lead had narrowed.
Why it works
Free licenses, central support, and migration help make going along easy, while the permanent cost of a weaker tool stays out of sight. It makes keeping the better capability look worse: a strength is recast as a noncompliant outlier, and the unit is described as refusing to align. And it makes keeping it costlier, in audit findings, exception requests, an unfunded budget line, and the look of being uncooperative at every steering meeting. The rationale has to survive a board question and the center has to control budget and architecture reviews, and it helps when other units are glad to see a peer leveled.
The thinking behind it
Jeffrey Pfeffer Pfeffer's The External Control of Organizations: A Resource Dependence Perspective (1978) holds that whoever controls a critical, scarce resource gains power over those who depend on it, and that people act to reduce their own dependence and create others'. A bespoke planning tool is such a resource for the unit that owns it. A single standard removes the dependence and the influence that came with it, which is why the mandate shifts power as well as cost.
Leon Festinger Festinger's A Theory of Social Comparison Processes (1954) argues that people judge their abilities by comparing themselves with similar others. Units with weaker tools have long measured themselves against the strongest peer. A standard set near their level narrows the gap they were measured against, which helps explain why they back the mandate in public, and why its author can count on their support.
When it fits
Central functions with authority over shared tools or processes, where variation across units costs real money in licenses, support, or data that cannot be compared. It needs a rationale that will survive a board question and enough budget to make migration painless for the weaker units.
How to use it well
State the trade-off openly. Say which capabilities the standard will cost and what the company gets in return.
- Choose the standard on cost and scale, and publish the criteria.
- Fund the migration centrally: licenses, support, training.
- Apply the exemption rule to every unit alike, and refuse or grant consistently.
- Measure the result, including the losses you predicted, and report it.
Where a unit can show a measurable tie between its tool and profit, consider a planned exception. It costs less than a fight you lose at the board.
What it costs and where it backfires
Something real is lost by the strongest unit, and its leader will remember who took it. If the capability was worth more than the savings, the board will see it in the numbers eventually. The line is honesty about the loss. Once you hide or misstate what the standard costs the strong unit, blame the predictable shortfall on that unit's execution, or pick the standard to cut down a rival leader you then hold to targets the tool cannot meet, the mandate has become a setup.
When it is used on you
Make the capability legible before the mandate lands: document what your tool does that the standard cannot and what that is worth, find a senior sponsor with a stake in that profit, and argue in the open on results. If you must migrate, record the baseline and the expected loss in writing so the shortfall is attributed correctly.