Most people who have worked for a disleader cannot name what happened to them. They describe the aftermath instead. They say the job stopped being interesting. They say they became careful. They say they started keeping a folder of emails, and that they felt slightly ridiculous doing it. What they are describing is not a personality clash. It is a recognisable pattern with a recognisable progression, and the reason it goes unnamed for so long is that every individual instance of it looks reasonable.
The National Leadership Association calls that pattern disleadership. This article sets out what it is, why intelligent and well-intentioned people fall into it, how it spreads through an organisation, and what actually interrupts it. It is the conceptual core of the DISLEADERSHIP programme, and it begins in an unexpected place: not with the leader, but with the feeling they leave behind.
It starts with a feeling of betrayal
Ask someone who has left a team under a blaming leader what the worst moment was, and they rarely name the largest injustice. They name a small one. A meeting where they were contradicted in front of a client. A project they had led for a year, described in a summary email as something the leader had driven. A mistake, genuinely theirs, that was raised eleven months later in a performance review as though it had been on file the whole time.
The reaction to these moments is disproportionate to their size, and that disproportion is the diagnostic. What has been broken is not fairness in a single instance. It is the assumption that effort given in good faith will be received in good faith. That assumption is what allows a person to volunteer for the difficult task, to flag their own error early, to say "I do not know" in front of colleagues. Once it goes, all three behaviours go with it, and they go quietly.
The betrayal is not that the leader was unfair. It is that the person had assumed they would not have to defend themselves, and discovered that they did.
This matters for diagnosis because betrayal is felt long before it can be evidenced. By the time someone can point to a pattern, they have usually spent months adjusting to it. Organisations that wait for a documented case are, structurally, always about a year late.
Blaming the culture is the first symptom, not the diagnosis
The most common thing a disleader says about a struggling team is that the culture is the problem. This is worth taking seriously, because it is almost always partly true, and because its truth is what makes it so effective as a defence.
Culture is the ideal object of blame. It is real enough to be discussed, diffuse enough that nobody can be asked to fix it by Friday, and it implicates everyone equally, which in practice means it implicates no one. A leader who attributes a missed quarter to the culture has produced an explanation that survives scrutiny, requires no change in their own behaviour, and positions them as the clear-eyed diagnostician of a problem they inherited.
The test is simple and it is worth applying honestly. When a leader names a cultural problem, do they describe their own contribution to it? Not in the ritual sense of "we all need to do better", but specifically: this is the behaviour I model that reinforces the thing I am complaining about. A leader who can do that is describing culture. A leader who cannot is using it.
Why the brain reaches for blame first
It would be convenient if blaming leaders were simply bad people. Most are not, and treating the pattern as a character defect is one reason it persists — it makes the behaviour unspeakable rather than correctable. The more useful account is neurological, and the DISLEADERSHIP curriculum spends two full chapters on it for good reason.
A public failure registers as a threat to standing, and threat responses are fast, physiological, and older than deliberation. The response mobilises before the slower, evaluative parts of the brain have finished assembling a considered account of what happened. In that window — and it is a short one — the mind produces an explanation that reduces the threat. An explanation locating the cause outside oneself reduces it most efficiently.
This is why blame so often arrives in the first sentence after bad news, and why it is so frequently wrong in ways the person would recognise an hour later. It is not a considered judgement. It is a reflex wearing the clothing of a judgement, and it is convincing precisely because the person producing it believes it.
What a blaming leader looks like from the inside
From the outside, the pattern reads as unfairness. From the inside it reads as rigour. This gap is the reason self-correction is so rare, and it is worth spelling out what the pattern feels like to the person enacting it.
- A sense of being surrounded by people who do not care as much as you do — which is experienced as evidence of your own standards, not of your effect on theirs.
- A recurring feeling that you have to check everything yourself, because the checking has become necessary, because people have stopped volunteering problems.
- Genuine surprise at departures, followed by an explanation involving money, ambition, or the person not having been a good fit.
- An accurate memory for others’ errors and a generous, contextual memory for your own — not dishonesty, but the ordinary asymmetry of knowing your own reasons and only seeing others’ results.
- Impatience with what is perceived as excuse-making, which is often the sound of someone explaining a constraint you set.
Note that none of these feel like cruelty. They feel like conscientiousness under difficult conditions. That is what makes the pattern so durable: it comes with its own justification pre-installed.
The Dark Triad is the extreme, not the norm
The DISLEADERSHIP curriculum devotes a chapter to Dark Triad traits — narcissism, Machiavellianism and psychopathy — and it is important to be precise about why. It is not because most blaming leaders have them. The overwhelming majority do not.
It is because the small minority who do produce damage of an entirely different character, and they require an entirely different response. For the ordinary disleader, the behaviour is defensive and responds to structure. For the Dark Triad leader, it is strategic: blame is not a reflex under pressure but a tool used deliberately, often calmly, and often most intensely against the people best positioned to notice.
The distinction matters operationally. Coaching, feedback and structural constraints improve the first group. Applied to the second, the same interventions supply useful information about how to appear to have changed. Organisations that cannot tell these apart tend to spend years developing someone who was never going to develop, while the people around them leave.
How it spreads: in-groups, ballrooms and the status quo
Disleadership does not stay contained in the relationship between one leader and one report. It reorganises the team around itself, and it does so through a mechanism most people recognise immediately once it is named: the split into an in-group and an out-group.
The in-group is not composed of the most capable people. It is composed of the people who have learned the rules — what not to raise, when to agree, whose account of an event to adopt. Membership brings real benefits: information, protection, the benefit of the doubt. It is rational to seek it. Once enough people have, the team has acquired a second, unwritten performance standard that has nothing to do with the work.
What the curriculum calls the ballroom is the visible surface of this arrangement. Meetings become performances: well-attended, superficially harmonious, and almost entirely uninformative. The real conversations happen in pairs afterwards. Anyone who has worked in such a team knows the specific exhaustion of a meeting in which nothing false was said and nothing true was said either.
The status quo then does the rest. Nobody defends the arrangement, and nobody dismantles it, because the cost of raising it falls entirely on whoever raises it. This is why these environments are so stable, and why they usually change only when someone senior enough to be safe decides to spend that safety.
Destructive comments and fallout time
One of the most useful ideas in the programme is fallout time: the interval between a remark and the end of its effects. Leaders systematically underestimate it, and the underestimate is not small.
A dismissive comment made in eight seconds — in a corridor, at the end of a call, in a review of work the leader has already forgotten reviewing — can govern how a person approaches their work for months. They will not mention it. They may not consciously recall it. But they will stop proposing the kind of idea that drew it.
The asymmetry is total. The leader spent almost nothing. The recipient is still paying. And because the cost is paid in things that do not happen — the proposal not made, the flag not raised, the initiative not volunteered for — it never appears in any report. It shows up eventually as a team that is compliant, punctual and strangely inert, and the leader wonders where the energy went.
What actually interrupts the pattern
Because disleadership is protective rather than deliberate, awareness is necessary but reliably insufficient. Leaders who learn the vocabulary without changing the structure tend to produce better-disguised blame: the same attribution, delivered with more sophisticated framing. Four structural changes do more.
- The ten-minute rule. For the first ten minutes after something goes wrong, discussion is restricted to what happened and what the situation now requires. No names. This does not abolish accountability; it delays attribution until the reflex has passed and the facts are in, which is when attribution is worth anything.
- Separate the event review from the person review. Hold them on different days, with different documents. When they are merged, everyone present is managing their exposure rather than establishing what occurred, and the resulting account is worthless.
- Write decisions down before the outcome is known. Blame depends on the reconstruction of intent after the fact. A one-paragraph record of what was decided, by whom, on what information, makes that reconstruction impossible — which protects the team, and protects the leader too.
- Give someone standing to name it. The pattern is invisible from inside and unspeakable from below. It requires a person with enough security to say "that was blame" in the room, and a leader who has genuinely agreed in advance to hear it.
None of these depend on the leader becoming a better person. They constrain the moment in which the reflex operates. That is deliberate, and it is why they work on ordinary disleaders — which is nearly all of them.
Why this is worth the effort
The case for addressing disleadership is not primarily moral, though the moral case is real. It is informational. An organisation is a machine for noticing problems while they are still small, and blame is the most efficient way ever devised to switch that machine off.
When reporting a problem is risky, problems are not reported. They are absorbed, worked around, and quietly compounded until they are too large to conceal. By then the cost of fixing them has multiplied, and the organisation experiences the whole sequence as a sudden crisis that nobody saw coming — when in fact a dozen people saw it coming and had learned that saying so was not worth what it cost.
That is the real expense of disleadership, and it never appears as a line item. It appears as surprises.