Destabilisation → Stabilisation
This is the third in a six-part series mapping a KGB defector's blueprint for collapsing a nation onto the way organisations are hollowed out by their own leadership. Read on, or start at the top with The Bezmenov Blueprint and come back.
The reorganisation was announced on a Monday. By Wednesday, half the senior team had updated their LinkedIn profiles. Not because they had been made redundant. Because they had seen this before.
It was the third restructure in eighteen months. Different language each time. "Realignment" the first round. "Streamlining" the second. This time it was "future-proofing," which is what leaders say when they have run out of synonyms for the fact that the last change did not work.
Every organisation I have worked with that restructures more than once in two years shares a common trait: the restructure is never the strategy. It is the substitute for one. And every time the org chart is redrawn, the same thing happens. Reporting lines shift. Relationships that took months to build are severed. Institutional knowledge walks out the door or retreats into silence. The people who remain learn the only lesson the organisation is actually teaching: do not invest in anything, because it will be dismantled before it matures.
That is destabilisation. And most leaders doing it think they are being decisive.
The Architecture of Unreliability
In Bezmenov's model, destabilisation was the second stage. Faster than demoralisation. Two to five years. Where demoralisation attacked belief, destabilisation attacked structure. The economy, defence, foreign relations, the institutional architecture that held things together. The goal was not to destroy these systems outright. That would provoke resistance. The goal was to make them unreliable. Inconsistent. Contradictory. When people cannot predict how the structures around them will behave, they stop trusting those structures. They stop cooperating with them. They protect themselves.
The methodology was not exclusive to the Soviets. John Perkins documented the same playbook running in the opposite direction in Confessions of an Economic Hit Man: the United States deploying economic coercion, institutional capture, and structural destabilisation across Latin America, the Middle East, and Southeast Asia. Different operator, identical mechanics. The playbook is agnostic. It does not care who runs it. It only cares that the target's structures become unreliable enough that the population (or the workforce) stops investing in them.
Inside organisations, destabilisation has a specific set of tells. None of them look like sabotage. All of them look like leadership.
The perpetual restructure. Strategy by org chart. Every time results disappoint, the response is structural: move people, create new layers, collapse old ones, rename departments. The underlying problem is never addressed because the restructure itself is treated as the solution. What it actually produces is a workforce that has stopped building anything because they know it will be torn down.
The shifting priority. A company has one strategic priority. Not three. Not five. One. The word was singular for five hundred years before modern management decided it needed a plural. Departments and business units may hold operational priorities that serve the company's strategic priority, and it is entirely reasonable for those to shift in response to circumstances. That is leadership. What destabilises is when the strategic priority itself shifts without explanation, without connection to what came before, and frequently enough that people stop executing against it because experience has taught them it will change before the work matures. When everything is a "priority," nothing is. And when nothing is a priority, people default to whatever protects them personally. That is not a motivation problem. It is a structural one.
The back-channel undermining of middle management. This is the most corrosive and the least visible. A senior leader who bypasses their direct reports to issue instructions to the level below. Who creates private channels of communication that exclude the people nominally responsible for execution. Who builds personal loyalty networks that operate outside the formal structure. The effect is not just confusion. It is the systematic destruction of the management layer that holds the organisation together.
This pattern has become more destructive, not less, as organisations have flattened. Two decades of "lean" structures and widening spans of control have thinned the middle management layer significantly. In many organisations, what remains is already stretched. Every middle manager who is bypassed or undermined now represents a larger proportion of the organisation's connective tissue than they would have a generation ago. There is less redundancy in the system. When the connective tissue between strategy and execution is already thin, cutting through what remains is not efficient leadership. It is structural vandalism.
Middle managers who are routinely bypassed stop making decisions. They become administrators. And the organisation loses the only layer capable of translating strategic intent into operational reality.
The measurement chaos. KPIs that multiply without hierarchy. Dashboards that measure activity rather than impact. Targets that conflict with each other across departments, so that one team's success is structurally guaranteed to be another team's failure. When the measurement system is incoherent, people game it. Not because they are dishonest, but because the system has made honest performance impossible. You cannot hold people accountable to standards that contradict themselves.
Every one of these patterns has a reasonable-sounding justification. That is the point. Destabilisation does not need to be malicious. It only needs to be structural. The damage accumulates regardless of intent.
Stabilisation Is Not Rigidity
There is a reflexive objection to the word "stabilisation" in any leadership context, and it needs to be addressed head-on. Stability sounds like stagnation. It sounds like resistance to change, like bureaucracy, like an organisation that has stopped moving.
That is not what stabilisation means here.
Stabilisation is the deliberate construction of systems, relationships, and accountability structures that hold under pressure while remaining adaptable. It is not the absence of change. It is the presence of a foundation that makes change productive rather than destructive.
The distinction matters because most organisations do not have a change problem. They have a foundation problem. They change constantly. They restructure, they pivot, they launch initiatives, they adopt new frameworks. What they do not do is build anything underneath that change to absorb it. So every change event becomes a destabilisation event. Not because change is bad, but because there is nothing stable enough to change from.
Stabilisation operates on three axes.
Structural clarity. People know who is accountable for what, and that accountability is real. Not theoretical. Not "on paper." The org chart reflects how decisions actually get made, not how someone wishes they were made. Authority and responsibility sit in the same seat. When they are separated (authority without responsibility, or responsibility without authority), the structure is inherently unstable and everyone inside it knows it.
Strategic consistency. The direction holds long enough for people to execute against it. This does not mean the strategy never changes. It means that when it does change, the change is deliberate, explained, and connected to what came before. People can draw a line from where the organisation was to where it is going. The line does not need to be straight. It needs to be visible.
Measurement integrity. What gets measured reflects what actually matters, and the measurements do not contradict each other. This is where most organisations destabilise themselves without realising it. The measurement system is the operating system of the organisation. When it is incoherent, everything that runs on it is incoherent. When it rewards activity over impact, it produces activity without impact. When it pits departments against each other through conflicting targets, it produces politics instead of performance.
In my work I use Value Impact Goals™ rather than traditional KPIs for exactly this reason. A KPI measures whether something happened. A Value Impact Goal™ measures whether what happened mattered, to the client, to the team, to the organisation's stated purpose. The difference is not semantic. An organisation measured by activity will optimise for activity. An organisation measured by impact will optimise for impact. The measurement system you choose is a stabilisation decision, whether you recognise it as one or not.
The Stability Test
There is a version of this test for every level of leadership, but the simplest one is this.
If you disappeared for 30 days, would the organisation make good decisions in your absence?
Not the same decisions you would make. Good ones. Decisions consistent with the strategy, the values, and the standards you have set. If the answer is yes, you have built something stable. The structure holds because the structure is sound, not because you are personally holding it together.
If the answer is no, you do not have an organisation. You have a dependency. And a dependency is one absence, one crisis, one unexpected event away from destabilisation.
This is the test Bezmenov's framework implies but never states directly. A stable system is one that does not require constant intervention from the top to function. An unstable system is one that falls apart the moment the intervention stops. Most leaders confuse their own indispensability with organisational strength. It is the opposite. If the organisation cannot function without you, you have not built an organisation. You have built a vulnerability.
Do Something About It
Stability is not the end state. It is the platform. And a platform that exists only in theory is not a platform at all.
If you read the four destabilisation patterns above and recognised your organisation in any of them, you already know where the structure is failing. The question is whether you are willing to name it and act on it.
I built a diagnostic called the Confusion Diffuser™ for exactly this moment. Three questions. No theory. No worksheets. Just signal.
One. If each person on your team had to state their top priority in one sentence, would those sentences match yours? When did you last test that?
Two. What are you assuming they already know, that you have never actually made explicit? Name it.
Three. If you stepped away for a week, what would go off course? Why?
Run those three questions with your leadership team this week. Not as an exercise. As an honest audit. Write the answers down. Compare them. The gaps between what you assumed and what you find are the exact points where your organisation is structurally destabilised.
Then fix the first one. Not all of them. The first one. The one that, left unaddressed, will make every other problem worse. Ninety days. One structural gap. Closed.
That is not a transformation programme. It is a leadership decision. And it is the difference between an organisation that is one crisis away from collapse and one that is ready for whatever comes next.
Because what comes next is crisis. It always is. The only variable is whether the foundation holds.
Next in the series: Crisis to Confidence. A destabilised organisation is one crisis away from collapse. A stabilised one is ready for it.
Paul Lange advises owners, executives, and boards on the decisions that define commercial outcomes and organisational character, and on what a working board actually contributes. He has spent close to four decades across finance, technology, hospitality, professional services, and operating roles, in Europe, Asia, the Middle East, and Australia, on both sides of the table, with private equity and venture capital one part of it, and has taken five of his own companies through to exit. He is the creator of the Total QX™ and TILE Theory™ frameworks, and the author of The 20% Leader, Mis(très)s Entrepreneur Manifesto, Evolve or Be Remembered, and The Inheritance Manifesto. He runs his advisory practice, Manolutions, from the Gold Coast, Queensland. He writes Conviction because leadership without accountability is just theatre.