Critical workflows are rebuilt to run only through one new system or central group, pitched as efficiency, until that group can withhold what any unit needs until it complies.
An example
After a merger at an auto parts supplier, a new shared-services group took over purchasing, engineering-change approvals, and the plant data warehouse, all presented as standardization ahead of an audit. The manager of one Midwestern plant found the old supplier portal switched off on a Friday. Within a month every off-system request needed an escalation memo, and a request for a quality data pull came back with a checklist: confirm adoption of the new scheduling model before the data would be released. The plant had objected to that model in two operating reviews. The plant manager kept a log of every delayed release and its effect on line output, and when a late part cost the plant a day of production on a major customer's program, sent the log to the operations vice president along with the old portal's uptime record.
Why it works
Real but modest benefits, efficiency and audit readiness, come with the new system, so complying looks better. Complying also looks easier, since requests flow through in one step while everything off-platform needs justification. The old way looks worse once legacy channels are switched off, and resisting looks costlier because a unit that refuses can no longer buy, hire, or get its data. It fails without real control of critical resources, gradual embedding, timing during a merger or audit when restructuring seems normal, and a credible efficiency story.
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 actors work to reduce their own dependencies and create others'. A central group holding purchasing, change approvals, and the data warehouse has built that position. Keeping a working alternative alive reduces your own dependence before the position hardens.
Oliver E. Williamson Williamson's The Economic Institutions of Capitalism (1985) explains that once parties make investments specific to a relationship, each is exposed to the other taking advantage. Units that move their purchasing and data into the central system make such investments, and the central group can then attach conditions to access. The advice to object early follows directly: before the specific investment is made, the unit still has a choice.
Warning signs
Routine work now needs sign-off from a central group that did not exist until recently. Legacy channels are switched off one at a time, each with a sound reason. Every request outside the new system needs an escalation memo. Access to a critical resource such as data, purchasing, or hiring comes back with a compliance condition attached, and escalation cannot reverse the custody arrangement.
How to defend yourself
Object early, while the old way still works. Once lock-in is complete, objecting costs far more. Senior sponsors tend to withdraw support when operational paralysis embarrasses them, so make sure they see it. A dependency imposed too fast, or a central system that underperforms, gives you the case for alternatives. Collect that evidence and leave the motive out of it.
- Keep a working alternative alive as long as you legitimately can, and do not dismantle it ahead of schedule.
- Document every failure, delay, and compliance condition from the central system, with its operational cost.
- Look for substitute sources for the withheld resource, and for peers facing the same conditions.
How a leader shuts it down
Ask of every centralization what happens to a unit that disagrees with the central group. Keep custody of critical resources separate from the authority to set policy, so access never depends on agreement. Count resentment as a cost: compliance bought this way erodes the standing of the people who imposed it.