The quarter closed above target. The team hit every milestone. Morale was high, reviews were glowing, and there was a particular kind of energy in the room — the kind that shows up when people feel like they are winning. The leadership team celebrated, as they should have. Good work deserves recognition. Then they moved on to the next quarter, carrying the quiet assumption that whatever they had been doing was working — and would keep working.

Six months later, three of their best people had left. A competitor had entered the space with a leaner model. The metrics that once climbed were flattening, and nobody could explain why. Nothing dramatic had changed. There was no crisis, no scandal, no catastrophic error. What happened was subtler and, in many ways, harder to fix: they had stopped learning from their own success. The win had become a blindfold.

This pattern is so common it barely registers as a pattern. We treat failure as instructive — we run post-mortems, we ask “what went wrong,” we build recovery protocols. But success? Success gets celebrated and filed. Nobody runs a post-mortem on a win. Nobody asks, “What conditions made this possible, and are those conditions still true?” The assumption is that if it worked, you understand why. That assumption is almost always wrong.

What Success Actually Does to Your Thinking

Most strategic failures are caused by past successes that stopped being questioned. Wins create narratives — “we’re great at X” — that outlive the conditions that made the win possible. The narrative hardens. The conditions shift. And the gap between the story you are telling yourself and the reality you are operating in widens until something breaks.

When things go well, the brain does something predictable: it reduces error-checking. This is not a moral failing. It is a neurological efficiency. If the current approach is producing good outcomes, there is less reason to scan for threats, question assumptions, or invest energy in alternatives. The system that was working gets promoted from “current strategy” to “proven strategy” — and once something feels proven, curiosity about whether it is still correct drops sharply.

At the individual level, this looks like confidence settling into complacency. At the organisational level, it looks like culture calcifying around a particular way of doing things. Dissent becomes harder. Questions feel disloyal. The phrase “why are you being negative?” starts appearing in meetings where someone raises a concern. Leading indicators are ignored because the lagging indicators still look good. By the time the lagging indicators catch up, the window for easy correction has usually closed.

The mechanism is not complicated. Success reduces perceived threat. Reduced threat reduces vigilance. Reduced vigilance means weak signals get filtered out. And weak signals — the early warnings that something is shifting — are exactly the data you need most when things appear to be going well.

Three Success Delusions

There are three specific ways that success distorts thinking. They operate at every level — individual, team, and organisation — and they are worth naming clearly so you can recognise them when they show up.

Delusion 1: Outcome Equals Process

“We won, therefore our process is correct.” This is the most seductive of the three because it feels so logical. But outcomes are noisy. They are influenced by timing, market conditions, competitor mistakes, luck, and dozens of variables that have nothing to do with the quality of your process. A good outcome can emerge from a mediocre process that happened to encounter favourable conditions. If you do not separate these — if you let the outcome validate the process without examining the process independently — you will optimise for a system that worked once rather than a system that works reliably.

Pattern in Practice — Market Tailwinds Mistaken for Skill

A team launches a product into a rising market. Demand is strong. Growth exceeds projections. Internally, the narrative becomes: “We read the market perfectly. Our strategy was right.”

But much of the growth was environmental. The market was lifting everyone. Competitors were distracted. Timing was fortunate. The team’s actual contribution — the part that was genuinely skilful — was perhaps 30% of the outcome. The other 70% was tailwind.

When the tailwind shifts, the team applies the same strategy with more intensity, expecting the same result. It does not come. The strategy was never as strong as the outcome suggested. But by the time this becomes clear, the team has doubled down on an approach that was built on conditions that no longer exist.

Delusion 2: The Repeatability Assumption

“The environment will stay the same.” Every successful strategy is a response to a specific set of conditions. Those conditions change — sometimes slowly, sometimes abruptly. The assumption that what worked last year will work this year is not a strategy; it is an unexamined bet. And the longer the success has lasted, the more invisible the bet becomes, because the evidence of past success reinforces the belief that the approach is fundamentally sound rather than contextually sound.

Delusion 3: Identity Lock-In

“We are the type of organisation that always wins.” This is perhaps the most dangerous of the three because it shifts the success from a description of what happened to a description of who you are. Once winning becomes part of the identity, anything that threatens the winning narrative threatens the identity itself. This makes it psychologically expensive to acknowledge problems, question assumptions, or admit that a particular approach might be failing. The identity needs to be protected, so the data gets reinterpreted to fit the story rather than the story being updated to fit the data.

Wins create blind spots. And the bigger the win, the bigger the blind spot — because nobody questions the thing that made them successful.

How Success Kills Feedback

Healthy organisations run on feedback. Not praise, not criticism — signal. Accurate, timely information about what is working, what is not, and what is changing. Success degrades this signal in at least three ways.

Dissent becomes socially punished. When things are going well, raising concerns feels like ingratitude. The person who says “I think we might be overextended” in the middle of a winning streak is not heard as prudent — they are heard as negative. Over time, people stop raising concerns. Not because the concerns disappear, but because the social cost of voicing them becomes too high. The organisation gets quieter about risk at exactly the moment it most needs to hear about it.

Leading indicators are ignored. Lagging indicators — revenue, growth, market share — still look good. So the leading indicators — employee engagement, customer complaints, competitor moves, talent pipeline — get dismissed. “The numbers are fine” becomes the answer to every concern. But lagging indicators are, by definition, backward-looking. By the time they turn, the damage is already in motion.

Weak signals get filtered out. In a successful environment, the filtering mechanism shifts. Information that confirms the current narrative passes through easily. Information that challenges it encounters friction — it gets qualified, contextualised, or simply lost in the noise. This is not usually deliberate. It is a natural consequence of cognitive load: when you believe something is working, your brain allocates less processing power to evidence that it might not be.

Pattern in Practice — Star Performer as Single Point of Failure

A team’s success concentrates around one person — the high performer who drives results, manages key relationships, and holds institutional knowledge that nobody else possesses. The team celebrates this person’s contribution. The organisation rewards them. On the surface, everything is working brilliantly.

Underneath, a fragility is growing. Knowledge is not being distributed. Processes are not being documented. Succession planning does not exist because the person is not going anywhere — or so the assumption goes. The success has created a single point of failure disguised as a competitive advantage.

When that person leaves — and eventually, they always do — the gap they leave is not proportional to their role. It is proportional to the dependency the team unknowingly built around them. The success hid the fragility. The celebration prevented the audit.

The Antidote: Learning From Wins

The solution is not to become paranoid about success or to drain the joy from achievement. Celebration matters. Recognition matters. The solution is to add one step that almost nobody takes: treating wins as data rather than conclusions.

A failure post-mortem asks: “What went wrong?” A success audit — what I call a Win Review — asks a different set of questions:

These questions are not negative. They are protective. They preserve the win by making its conditions visible, so that when those conditions change — and they will change — you can adapt rather than be blindsided.

Failure teaches you because it hurts. Success can make you complacent because it soothes. The discipline is not in handling adversity — most capable people can do that. The discipline is in staying curious when everything appears to be working.

The Win Review Memo

The Win Review Memo is a one-page document completed after any significant success. It takes thirty minutes. It produces disproportionate value because it forces you to separate what you did from what happened to you — and to identify the conditions that made the outcome possible rather than assuming the outcome validates everything that preceded it.

Practical Tool

The Win Review Memo (WRM) — One Page

  1. What was the win? Define it precisely. Not “great quarter” but the specific outcome, measured against the specific target. Precision here prevents the win from being inflated or generalised.
  2. What were the enabling conditions? List the external factors that supported the outcome: market conditions, timing, competitor behaviour, regulatory environment, team composition. Be honest about how much was environment versus execution.
  3. What did we do that we should standardise? Identify the specific actions, decisions, or processes that genuinely contributed to the win and that can be repeated. These are the elements worth protecting and embedding into your operating system.
  4. What did we do that won’t scale? Some wins involve heroic effort, unsustainable hours, or one-off conditions that cannot be replicated. Name them. If the win depended on something you cannot do again, that is critical information.
  5. What assumptions are now stale? Every strategy carries assumptions about the market, the customer, the competition, and the team. Which of those assumptions were formed during a different context and have not been re-examined? Stale assumptions are the most common source of strategic drift.
  6. What early indicators would warn us first? If this win were about to stop repeating, what would you see first? Define the leading indicators — the signals that would tell you the conditions are shifting before the lagging indicators catch up.

Complete this within a fortnight of the win, while the details are still fresh. File it alongside your risk register. Review it quarterly. The value is not in the document itself but in the thinking it forces.

Culture Move: Reward Truth Over Optimism

The Win Review only works if the culture supports honest assessment. If the culture rewards optimism and punishes concern-raising, the Win Review will produce sanitised answers that tell you nothing useful.

This is a leadership responsibility. It requires making it safe — genuinely safe, not performatively safe — to say things like:

These statements are not pessimism. They are precision. And precision, when it comes to understanding your own success, is one of the most valuable things a team can practise. The norm you are building is simple: curiosity is loyalty. The person who asks “will this keep working?” is not undermining the win. They are protecting it.

Curiosity is a leadership duty. If your culture punishes questions during a winning streak, your winning streak has an expiry date you cannot see.

Implementation: Building the Cadence

A one-off Win Review is better than nothing, but the real value comes from cadence — a regular rhythm of learning from success that prevents complacency from accumulating silently between crises.

Monthly: Win Review in the Leadership Team

Once a month, the leadership team identifies the most significant win of the past thirty days and completes a Win Review Memo together. This takes sixty minutes. The conversation matters more than the document. What you are building is a habit of examining success with the same rigour you apply to failure.

Quarterly: Assumption Refresh

Every quarter, pull out the assumptions listed in your most recent Win Reviews. Ask: “Are these still true?” This is not a lengthy strategic review. It is a focused check on whether the conditions that supported your recent successes are still in place. If they are not, you have a lead on a problem that has not yet shown up in your numbers.

Tie It to the Risk Register

Every Win Review should generate at least one entry in the risk register. Not because every win contains a disaster, but because every win contains assumptions — and assumptions are risks that have not yet been tested. Linking wins to risks ensures that the learning from success is not just intellectual but operational. It enters the system that governs your planning.

Common Mistakes Leaders Make

The Relief Mistake

There is a subtler version of this pattern that operates at the personal level, and it is worth addressing directly because many of the people reading this will recognise it in themselves before they recognise it in their organisations.

When a period of pressure eases — when a difficult project lands, when a strained relationship stabilises, when anxiety drops after months of intensity — the nervous system exhales. You feel lighter. More confident. More capable. And in that moment of relief, a quiet assumption forms: I am past it. The hard part is over. I can relax the structure now.

Relief feels like stability. But relief is not stability. Relief is the absence of acute pressure. Stability is the presence of systems that keep you grounded regardless of whether the pressure is high or low. When you confuse the two — when you let relief convince you that the structure is no longer needed — the drift begins. Not dramatically. Gradually. The small disciplines that created the good period start to feel optional. Sleep slides. Boundaries soften. Check-ins are skipped. And because the lagging indicators still look fine, you do not notice the erosion until it has accumulated into something that feels like a sudden collapse but was actually a slow fade.

Relief is the nervous system exhaling. It is not evidence that the structure is no longer needed. The structure created the conditions for the relief. Removing it because the pressure eased is like removing the scaffolding because the building looks solid — before the concrete has cured.

Early Warning Signs of Success-Driven Drift

Whether you are watching yourself or watching your organisation, these are the early indicators that success is quietly degrading your systems. You will not see all of them. You do not need to. If you recognise three or four, it is worth paying attention.

Protecting What Works

The point of all of this is not to become suspicious of success or to create an environment where achievement is met with scepticism. The point is to protect what works by understanding why it works — and to do that understanding while the conditions are still favourable, not after they have changed.

Wins should make you humbler and smarter. If they make you lazier, you have built a fragile empire — one that depends on conditions remaining constant, on luck continuing to land, and on the narrative holding together long enough to get through the next quarter. That is not strategy. That is hope dressed up in a spreadsheet.

The leaders who sustain performance over time are not the ones who celebrate the loudest. They are the ones who, in the quiet moment after the celebration, ask: “What made this possible? Is it still true? And what would we see first if it stopped being true?”

Those questions cost nothing to ask. The cost of not asking them is incalculable.

Key Takeaways

Series boundary: This post covers how success creates blind spots and what to do about it. If the constraint is more about post-mistake recovery → see Return to Form.
← Impostor Load: When Threat Kills Signal Signal Under Pressure Compassionate Rigour: Sustainable Excellence →

If you want help installing win reviews, protecting learning systems, and building the kind of curiosity that sustains performance — that is the work I do.

Get in Touch

Frequently Asked Questions

Why do teams stop improving after a big win?

Success reduces perceived threat, which lowers the brain’s error-checking. Wins create narratives — “we’re great at this” — that outlive the conditions that made the win possible. Without deliberate review, the narrative hardens into assumption and assumption drifts into complacency.

What is a Win Review Memo?

A one-page document completed after a significant success. It separates what you did from what happened to you, identifies enabling conditions, flags what won’t scale, surfaces stale assumptions, and defines the early warning signs that would tell you the conditions are shifting.

How do I stay consistent without becoming rigid?

Protect a small set of non-negotiable structures — the disciplines that created the good period — and allow flexibility everywhere else. Consistency is about preserving what works, not controlling everything. The goal is a stable foundation, not a rigid cage.

How often should we run Win Reviews?

Monthly in the leadership team for the most significant win. Quarterly for an assumption refresh — checking whether the conditions that supported recent successes are still in place. Link findings to your risk register so the learning becomes operational, not just intellectual.