Spending or compliance policy is tightened in small steps, each defensible on its merits, and the cumulative burden falls on a department whose way of working depends on the latitude being withdrawn.
Borderline: whether this move is justified depends on the situation, and only the person in it can judge.
An example
Over four quarters, the chief financial officer of an engineering services firm tightened purchasing rules three times. Each change came with its own memo and data: field purchases above $10,000 had produced two duplicate-payment incidents, so the approval threshold fell from $25,000, and late travel bookings were costing 40 percent more than advance ones, so trips booked inside fourteen days needed a director's sign-off. The field services division, which had resisted her plan to fold it into a central delivery unit, bore most of the new approvals, and its head said so at the leadership offsite. She did not dispute his numbers. She said the rules applied to every division, that his exception volume showed how much of the division's spending ran outside normal controls, and that the central delivery unit would carry those purchases inside a single budget. The chief executive asked for the reorganization proposal by the next quarter.
Why it works
Each step is small enough to defend on its merits, so there is never a single decision to oppose. The burden lands on the department whose model depends on the latitude being withdrawn, raising the cost of its everyday work and wearing down the speed and judgment that made its approach work. Agreeing to the larger plan becomes the easy path, because it would remove most of the friction. It needs authority over a class of company-wide policy, a real case for each change, and increments small enough to pass as prudence.
The thinking behind it
Oliver E. Williamson Williamson's The Economic Institutions of Capitalism (1985) explains asset specificity: investments specialized to one relationship lose much of their value outside it, which leaves their owners exposed. A department whose working model depends on purchasing latitude has made that kind of investment in the current rules. Tightening the rules lowers the value of everything it built around them, without any direct decision about the department, which is why small changes press so hard on it.
Thomas C. Schelling Schelling's salami tactics, from Arms and Influence (1966), describe defeating a line by crossing it in slices too small to justify a response. Here the slices are policy changes: each tightening is too minor to fight on its own, and the department's position erodes across a year. Tracking the cumulative burden is the department's answer, because it turns the slices back into a single decision someone has to defend.
When it fits
Finance, compliance, and operations leaders who own company-wide policy, and who see real control problems in how a resistant unit spends or operates, are the natural users. You need a sound reason for each change, data to support it, and the patience to let several small steps work across a year.
How to use it well
Make every change stand on its own. If a tightening cannot be justified without reference to the department you are pressing, do not make it.
- Tie each step to a specific control problem, with numbers, and publish the memo.
- Apply each rule to every unit it covers, allies included.
- Track exception volume by department, and be ready to show it.
- When the department objects, answer on the merits of each rule, and say openly what larger change would remove the burden.
Keep the increments modest and spaced out. A burst of new rules reads as a campaign.
What it costs and where it backfires
The department will document the uneven burden, and peers or the chief executive may read the pattern as targeting, which costs you standing even when every rule is sound. Tight controls also slow legitimate work, and the delays show up in client results. The clean form ends at the reason for each step: rules chosen to cripple a department because it opposed you, or enforced on it while waived for allies, are retaliation, and the memo trail will show which it was.
When it is used on you
Squeezed by successive rules, record each change, its date, and the exception volume it produced in your unit and in others. Take the comparison to the policy owner, and if needed to the chief executive, and ask directly why the burden falls on you. Find peers who will acknowledge in the room that the changes barely touch them.