Many structural changes land at once and at speed, inside the leader's own authority, so the organization adapts to a new baseline before opposition can organize against any one piece.
Borderline: whether this move is justified depends on the situation, and only the person in it can judge.
An example
With a board mandate to fix a cost base running 18 percent above peers, the new chief executive of a gas distribution company moved fast. In one six-week window she announced fourteen changes: a new field-dispatch model, three merged district offices, a procurement reset, the end of two legacy billing systems, and a reorganized engineering function. Each came with an owner, a date, and the execution plan that HR, IT, and communications had built the previous quarter. Middle managers who had expected a year of working groups found themselves implementing. A coalition of district managers tried to fight the office mergers, but by the time their memo circulated, the dispatch model and the procurement reset had also landed, and they had to choose their battles. The company met its first-year cost target. Engagement scores fell nine points and took two years to recover.
Why it works
Speed reads as decisiveness to uncommitted middle managers, so going along looks better. Compliance looks easier because the consultation forums where objection would happen are gone. Organized resistance looks worse, since each new move resets the baseline before a coalition can form, and costlier, because resisters would have to fight on every front at once. The prerequisites are formal authority to issue each change without intermediate approvals, execution machinery that can land the moves, an organization whose resistance runs on slower cycles, and tolerance for lasting damage to trust.
The thinking behind it
Mancur Olson Olson's The Logic of Collective Action: Public Goods and the Theory of Groups (1965) explains that concentrated interests tend to prevail over diffuse ones, because organizing costs fall on individuals. Fourteen changes at once split the opposition into many affected groups, each facing its own fight and none large enough to carry the others. The counter is to concentrate: pick one or two battles and pool the opposition behind them.
Herbert A. Simon Simon's Designing Organizations for an Information-Rich World (1971) argues that information consumes the attention of its recipients. Every announcement claims the attention of the managers who must respond, and a wave of them uses up the attention needed to organize a counter-argument. Tracking what has actually landed matters for the same reason, since attention goes to announcements while execution may lag behind them.
When it fits
Appropriate for a leader with a clear mandate, formal authority over every change in the package, and a company whose problems are urgent and well understood. You need execution machinery ready before the first announcement. It does not fit organizations with hard procedural floors, such as works councils or co-determination, or changes that need broad input to be designed well.
How to use it well
Track what has actually landed against what was announced. The common failure is authority to announce without capacity to execute, and announced changes that never arrive hand opponents their case.
- Confirm formal authority for every change, since one that needs an approval you lack will stall and become the rallying point.
- Build the execution plan for each move before announcing any of them, with owners in HR, IT, and communications.
- Sequence the waves so each lands before the next is announced, inside a thirty-to-sixty-day window.
- Honor every legal and contractual consultation obligation, since speed works on informal friction and never on required process.
What it costs and where it backfires
Trust and discretionary effort fall, and survivors carry the damage for years. Middle managers stop volunteering information once they conclude that consultation is decoration. Speed reads as competence only in some cultures, and elsewhere it reads as recklessness. Required process is the hard limit. Bypassing a mandated consultation, a works council, or a board approval turns a fast program into a violation, and a court or regulator can halt every piece at once.
When it is used on you
Pick the one or two changes that matter most when they arrive in overlapping waves, and contest those, since fighting everything loses everything. Push for pace limits: review windows, the ability to halt a change, and dependencies between moves. Track which announced changes have landed, because many will not have.