Leadership restructures so often that institutional memory, informal networks, and accumulated expertise never settle long enough to form a challenge to the people at the top.
An example
Four reorganizations in three years: the lead architect in a regional bank's technology group had counted them, by product, then by platform, then by customer journey, then back to platform under a new name. Each came with a memo about the market and a new set of managers. The team that had spent eighteen months mapping the bank's core-system risk, and had told the chief information officer the replacement vendor was a mistake, was broken up in the second reorganization before it finished its report. By the fourth, only two of its seven members were still at the bank, and the notes sat on a shared drive nobody had permission to open anymore. When the vendor's migration failed its first test, the bank's directors asked who had assessed the risk, and no current manager could say.
Why it works
Constant restructuring makes keeping your head down the easy choice, because people spend their energy learning who they report to and what their metrics are. It makes a challenge worth less, since the assets a challenge needs (knowing who will back you, what the data says, which old decision caused today's problem) lose value at every reshuffle. And it makes organizing costlier, because allies are scattered and trust has to be rebuilt each time. Leaders who control structure alone can sustain it, given plausible outside reasons for each change and an organization too large to rebuild networks by walking down the hall.
The thinking behind it
Mark Granovetter In The Strength of Weak Ties (1973), Mark Granovetter shows how acquaintances spanning groups carry information and coordination across an organization. Each reorganization cuts those bridges and scatters the people who knew which colleague would back them and which data told the story. Keeping in touch with former colleagues across the new lines is a defense because it rebuilds the ties the reshuffles break.
Mancur Olson Mancur Olson's The Logic of Collective Action: Public Goods and the Theory of Groups (1965) argues that anything raising the cost of coordination makes collective action less likely. Constant restructuring keeps raising that cost: a coalition that formed last year now spans three divisions and two new managers. Structures the leader cannot reshuffle alone, such as a board with continuity, bring the cost back down.
Warning signs
Restructuring outruns any stated change in strategy. Teams are broken up and re-formed before they deliver what they were created for, especially teams that disagreed with leadership. Each memo cites market conditions. Managers turn over with every cycle, records and working files are lost in the moves, and fewer people each year can explain why an earlier decision was made.
How to defend yourself
Build on structures the leader cannot reshuffle alone, such as a board with continuity or a published org chart, and put your concerns into them.
- Keep your own records of decisions, analyses, and who knew what, in a form that survives a move: dated, written, and held where you will still have access.
- Stay in touch with former colleagues across the new lines. The informal network is what the reshuffles break.
- Finish and circulate work in pieces, so a team broken up midway still leaves something usable.
- Count the reorganizations and the turnover, and give the numbers to directors or investors who track them.
How a leader shuts it down
Directors and investors can track reorganization frequency and management turnover directly, alongside the strategy each change was meant to serve. Require published org charts and records that outlive each restructure. Ask why a team was dissolved before it delivered, and treat repeated reorganizations with no change in strategy as a governance issue.