❌

Reading view

There are new articles available, click to refresh the page.

Plan Continuation Bias

Plan Continuation Bias, or “Get-There-Itis”

I got pretty sick this week. I was wiped out with a nasty bout of tonsillitis – high temperature, exhausted and felt awful. The doctor put me on strong antibiotics, painkillers, and told me, in no uncertain terms, to rest up and take it easy. 

What felt even worse than the illness was having to cancel a client workshop. As far as I can remember, we haven’t cancelled one in about four years. We usually manage to build in enough redundancy for someone else to deliver it, but this time, for various logistical reasons, it just wasn’t possible.

And we really wrestled with it. We spent far too long trying to find a way to make it work. Maybe I could load up on painkillers and caffeine. Maybe the 3 hour drive there, delivering the workshop, driving back and then collapsing wouldn’t be that bad. Maybe I could just power through on adrenaline. 

Looking back, I can see all the forces pulling us toward keeping the plan on track: a worry about disappointing the client; all the preparation, travel planning and childcare we’d already arranged; and, if I’m honest, the deeply normalised idea that “pushing through” is the right thing to do. All of that created a powerful feeling that we should still try to deliver.

In reality it would have been a very bad idea for me, for the client, and for other road users! Eventually, we contacted the client, postponed the session… and they were perfectly fine about rescheduling.

This fierce desire to continue with the plan, even though it no longer makes any sense, or is actually unsafe to do so, is a great example of plan continuation bias.

What Is Plan Continuation Bias?

Plan continuation bias (also known as get-there-itis in aviation, course correction bias, or “summit fever” in mountaineering) is the cognitive tendency to stick with an existing plan even when the conditions have changed and the plan no longer makes sense or isn’t safe to continue.

It’s best known in aviation, where get-there-itis means that pilots may press on with planned courses in bad weather, continue flights with marginal fuel, or persist with unstable approaches that should really demand a go-around. The same pattern is common in mountaineering, and I’ve got many experiences of this myself – I can particularly remember one occasion on Crib Goch where we reluctantly turned around after bad weather set in, but the decision itself was really hard, almost emotionally painful, because we were already well up onto the ridge.

climbing crib goch
crib goch ridge

It happens in healthcare too, where teams continue to attempt procedures when it’s time to stop or change (as in the tragic case of Elaine Bromiley), and we also see it in product or project teams, where people press on towards the original brief even though the context around them has completely changed.

It’s worth noting that plan continuation bias isn’t plain old stubbornness – it’s about how we humans make sense of the world, particularly when we’re under pressure, operating in uncertainty, and subject to social risk.

“You’ve got to know when to hold ’em, know when to fold ’em.”
— Kenny Rogers

Cognitive load and confirmation bias.

When we’re under high workload and time pressure, our attention naturally narrows on the task – the goal we’re trying to achieve. We may simply not have the bandwidth to process everything, and our confirmation bias means that we pay more attention to information that appears to support the plan, and discount, or don’t even see, information that suggests we should change course. So even when most of the signs point towards “turn back”, we cling to the scraps of evidence that say “it’ll be fine, keep going”.

This is one reason why we can often spot plan continuation in hindsight, and it can become something of a counterfactual, as “obviously wrong” after it’s already happened. Although to an outside observer afterwards, it seems obvious that we should have changed course, this may have been cognitively invisible to the person in the moment. 

Sunk cost fallacy

There’s a strong sunk cost element to plan continuation – when we’ve already invested time, money, effort, and reputation something, it means that stopping or changing direction feels like a failure: “We’ve put so much into this, we can’t stop now.”

But of course, that’s a fallacy, even though it feels right and noble to continue. It doesn’t make sense to keep pouring resources into something that’s no longer going to deliver value, or is actively unsafe to ourselves or others. Yet the more we have invested, and the closer we are to our goal, the more we tend to rationalise continuing.

Power, authority, and interpersonal risk

Plan continuation bias is compounded when the plan was defined by someone in power – a CEO, senior leader, major client, or powerful stakeholder. In these cases, we may well predict that challenging that goal is likely to incur interpersonal or career risk. None of us want to disappoint our boss, and challenging decisions that were made by someone with power over our employment status or career success is rarely easy. And of course, there are other risks too. We might worry that in raising concerns about the plan, we’ll be seen as a poor team player, as not being “committed enough”, or as the negative one in the group.

We humans tend to have a deep need for harmony and belonging, so continuing with the plan often feels more coherent, comfortable and socially safe than being the dissident who says, “We should stop.”

Symbolic goal fixation 

Some goals become symbolic of what overall “success” means – in mountaineering, it’s the summit, but in organisations, it might be a launch date, a target, or an OKR. This is especially true if that goal has been made public, or committed to with large posters and announcements. Sometimes organisations even use mountaineering metaphors to describe these lofty and ambitious goals. All this can mean that we drift into an all-or-nothing mindset where summit = success, and turning back = failure.

If you’ve read Jon Krakauer’s Into Thin Air about the Everest disaster in the ’90s (Everest is the colonial name for the mountain known locally as Sagarmāthā in Nepal and Qomolangma in Tibet), you’ll be familiar with this story: along with other errors and misjudgements, some climbers pushed for the summit even after bad weather set in and the safe window had closed. Summit fever, along with a great deal of sunk cost (it’s expensive to climb Everest, and climbers spend months preparing) meant that climbers became fixated on this singular goal of summiting Everest at any cost. For many of them, that cost was their lives. 

But as one of my climbing instructors used to say “Getting up is optional. Getting down is mandatory.” (I don’t think he was the first to say this!)

The same goes for organisations delivering projects and products: the real failure isn’t “we didn’t ship,” but shipping something that no longer makes sense and delivers no real value. It’s much wiser to be here the following day to try something new, than to risk the business, or our lives, on a potentially already failed project.

“Hazardous attitudes”

CRM (Crew Resource Management) in aviation talks about five “hazardous attitudes” that make plan continuation bias more likely:

  • Macho: “I can handle it. I’m the expert.” This is practically one of the definitions of toxic masculinity: a sense of superiority, or an anxious need to prove oneself in the face of adversity.
  • Impulsivity and a bias to action: “We should do something.” We often assume that action is better than inaction, and we tend to regret waiting, or pausing, more than we do taking a step – even a misguided one. In many organisations, people are punished more for not doing something (for holding back until they can make a better informed move) than for acting too quickly, even when it would make greater sense to pause and allow more information to surface.
  • Invulnerability: “It won’t happen to me.” Success can incubate failure. Just because it’s gone right in the past, doesn’t mean it will this time. Indeed, if it had gone wrong in the past, we possibly wouldn’t even be here to make this judgement.
  • Resignation: “What’s the use? I can’t change this.” We may feel that once we’ve settled on a plan, we’re stuck on the railway tracks, unable to change direction. But we are not trains – we can make decisions based on new information, and change direction. And even trains have brakes.
  • Anti-authority: “I’m special. The rules don’t apply to me.” In so many books and movies, the hero is the subversive renegade who breaks the rules and succeeds. But real life doesn’t always play out the way movies do. Ignoring new risks because we believe we’re the exception doesn’t actually make the risk go away. 

All of these can mean that we’re more likely to press on than to pause, turn back, or “go around”.

Organisational Examples: Projects, Products, and OKRs

In product teams this shows up all the time. We might carry on building a feature even after a competitor has released something better and captured most of the market. We may stick to an OKR even though conditions have shifted and the objective is no longer a good idea. We become so fixated on achieving the “key result” that we stop asking whether it’s still a useful or sensible result. 

If the objective is the summit and the key result is “Reach the summit camp by 3pm”, what happens when a storm rolls in at midday?

In other cases in organisations, we simply keep burning money and time on a project that clearly won’t deliver the hoped-for return. Often because the goal has been cascaded from “higher up”, and as with symbolic goal fixation, not hitting it is framed as failure. “We said we’d deliver X by date Y” becomes more important than checking “Is X still the right thing to do?” This pressure intensifies when goals are publicly announced, a tactic often intended to “motivate” teams to deliver but which frequently drives teams to chase the original commitment rather than pursue the best outcome

Without psychological safety and sound decision practices, teams will often keep climbing to the summit because that’s the OKR, even when it’s clearly unsafe or pointless.

A Plan Continuation Feedback Loop

Plan continuation bias is dangerous because it becomes a feedback loop:

  • The closer we get to the goal, the harder it feels to turn back.
  • The more we invest, the more we rationalise continuing.
  • The more things go wrong, the more urgent it feels to “just get it done”.

Research in aviation suggests that a large proportion of decision errors, (some suggest the majority of errors) are essentially plan continuation errors: pressing on when the safer option was to stop, divert, or go around. Charles West wrote about this goal proximity dynamic in “The Barn Door Effect”: pilots who would normally deviate widely around severe convective weather while en route often continue final approaches directly beneath dangerous thunderstorms when landing, simply because they can see the runway (the “barn door”) and because aircraft ahead of them have done so successfully (social proof of the Normalisation of Risk).

This certainly isn’t unique to pilots. It’s fundamental to how humans behave in dynamic, uncertain environments.

Where Psychological Safety Fits with Plan Continuation Bias

Psychological safety doesn’t magically remove plan continuation bias, but it can provide some counter-pressure that helps to interrupt this feedback loop. In groups with higher psychological safety, people are generally more willing to say things like “Are we still doing the right thing?”, and point out issues like a storm coming or a competitor’s similar product launch. People feel safer in pulling the Andon Cord, call to Stop Work, or suggest a go-around. 

However, in teams with lower psychological safety, plan continuation bias is structurally reinforced, because people are more likely to stay silent with those insights, perspectives or concerns. If we’re in a team with low psychological safety, we don’t want to disrupt the group harmony, offend someone in power, or risk damaging our own status or reputation. We may end up pressing ahead not because it’s the right thing to do, but because it feels less interpersonally risky than challenging the plan itself.

How to Reduce Plan Continuation Bias

Plan continuation bias is a deeply human tendency shaped by many different cognitive biases and heuristics, so we can’t eradicate it, but we can reduce its impact through some practical approaches:

1. Define exit criteria in advance. We agree in advance that if certain criteria are met, we stop, change direction, or take an opportunity to re-evaluate. For example, if a competitor releases an equivalent or potentially better product, we reconsider the business case. Or if certain safety thresholds are crossed – deteriorating weather conditions or issues with the equipment – we pause or “go around”. Pre-defining the criteria for interrupting the loop takes some of the emotional and interpersonal load off making the call in the moment.

2. Establish decision points at regular intervals. Similar to above, we can also build in regular check-in points to re-evaluate and consider “Should we still be doing this?” or simply regularly ask ourselves “Do we continue, pivot, or stop?”. If we were climbing a mountain, we may check in every 30 minutes and simply ask “Are we all still good to go?” The point is to deliberately reopen the question, not simply assume the plan is still valid.

3. Invite dissent explicitly. Sometimes called “devil’s advocate”, but I prefer the less evocative and more straightforward practice of “inviting dissent” by asking things like “What are we missing?”, “How could we see this differently?”, or even “We’re not leaving this meeting until we’ve heard five reasons why this is a bad idea.” We may even designate a small “red team” whose job is to be strategically awkward: to poke holes in the plan and look for reasons we shouldn’t continue.

4. Train people to recognise hazardous attitudes. This is deeper work, often part of CRM and similar training, to help people notice these hazardous attitudes emerging – in themselves and in others. That might include an inappropriate bias to action, a sense of invulnerability, resignation or resistance to authority. The aim isn’t to blame or single people out, but to build shared literacy and the skill to spot and respond to the attitudes that make continuation bias more likely.

5. Build diverse teams. The more diverse the team in background, expertise, perspectives, and experience, the more likely it is that people in the team will see what others have missed. Diversity, in its many facets, increases the chances that someone will notice the storm building on the horizon.

6. Finally, normalise and reward course correction. This is perhaps the biggest cultural shift, and the most impactful (but rather more difficult, organisationally). Stopping, cancelling, or changing course when it no longer makes sense to continue should be seen as success, not failure. That might look like celebrating teams who say, “This project no longer makes sense so we’re stopping it and moving onto something of higher value,” or explicitly rewarding people who highlight new risks or factors reducing the value of a project. Storytelling can be a powerful tool here too, by having open discussions about times when not continuing saved money, delivered greater value, or saved lives. Fundamentally, changing the plan should be framed as competent, expert, adaptive behaviour, not as failure.

reduce plan continuation bias with these 6 practices

Summarising Plan Continuation Bias

Reflecting on this piece, I’d describe plan continuation bias like this: 

Plan continuation bias is the cognitive, emotional and social tendency to stick with an established plan even when new information or changing conditions mean it no longer makes sense, is unlikely to deliver value, or increases risk to intolerable levels. It’s amplified by confirmation bias, workload and pressure, ever higher sunk costs and proximity to the goal, symbolic goal fixation, power dynamics, and the myriad interpersonal risks of challenging the plan; and it often leads individuals and teams to press on long after they should adapt or stop.

And sometimes, avoiding it is as simple (and as difficult) as admitting that you might be too poorly to drive across the country and deliver a workshop.

Further resources on plan continuation bias:

Managing Plan Continuation Bias with Mike Adolph on the Delivering Adventure Podcast

Orasanu, J., Martin, L., Davison, J. and Null, C.H., 1998, January. Errors in aviation decision making: Bad decisions or bad luck?. In Fourth Conference on Naturalistic Decision Making. https://ntrs.nasa.gov/api/citations/20020063485/downloads/20020063485.pdf 

“Just a Routine Operation” Martin Bromiley.

Continuation Bias: SKYbrary Aviation Safety. https://skybrary.aero/articles/continuation-bias

West, C.A., 2009. The “Barn Door” Effect. In Proceedings of the 14th Conference on Aviation, Range, and Aerospace Meteorology. https://ams.confex.com/ams/pdfpapers/162457.pdf 

The post Plan Continuation Bias appeared first on Psych Safety.

Counterfactuals

Counterfactuals

If, like me, you grew up during the Friends era, you might remember the scene where Ross is upset because he has to tell Rachel that Emily insists they can’t be friends.

Ross: “I don’t want Rachel to hate me. I don’t know what to do.”
Joey: “You want my advice?”
Ross: “Yes! Please!”
Joey: “You’re not gonna like it.”
Ross: “That’s ok.”
Joey: “You got married too fast.”
Ross: “That’s not advice!”
Joey: “I told you.”

For once, Ross is absolutely right. That isn’t advice. It’s a counterfactual: a redundant statement that sounds wise because the outcome is already known. It’s the illusion of clarity after the fog has lifted, after the complexity has collapsed into certainty. We all know the feeling of wanting to tell someone (or rather often ourselves) what should have been obvious. But that sense of “obviousness” only exists from where we’re standing now, in 20/20 hindsight, not from where the decision was made.

Counterfactuals are seductive. They tidy up messy stories. “If only we’d done X.” “If only they’d noticed Y.” They sound analytical, but they’re fictional. As the saying goes, “If my grandmother had wheels, she’d be a bicycle.” Once we start changing the facts, we’re not talking about reality anymore: we’re imagining a different one that didn’t happen.

It’s easy to laugh at Joey, but we all do it. Just look at all the hot takes on the large AWS outage this week. We look back at a failed project, a near miss, an incident or accident, and feel the seductive pull of “they should have..” or “they shouldn’t have…” because we crave causality and coherence. When something goes wrong, we want to believe that there was a single point of failure that we can fix for next time, reassuring ourselves that it won’t happen again. But as Dekker reminds us, 

“…[counterfactuals] make you spend your time talking about a reality that did not happen (but if it had happened, the mishap would not have happened.)” (Dekker, The Field Guide to Understanding Human Error, 2006, p. 39). 

Counterfactuals don’t actually explain why people acted as they did. 

Hindsight gives us the feeling that we’re seeing more clearly, when in fact we’re seeing differently. It turns messy events into clean, neat, linear stories where the outcome seems inevitable. After the fact, we reconstruct a chain of events so neatly that it feels like it couldn’t have unfolded any other way. But at the time, it could have unfolded many ways.

In complex systems, whether in tech, healthcare, or flying planes, everything seems to make sense until it suddenly doesn’t. Karl Weick describes this as the “collapse of sensemaking”, where a lack of relevant information, conflicting or contradictory data, distractions, or cognitive biases prevent accurate interpretation of the situation. As Richard Cook said, “All practitioner actions are gambles.” Every decision is made under various degrees of uncertainty, using local cues, imperfect data, and competing goals, constraints and pressures. When we uncritically apply hindsight, we risk erasing that uncertainty and turning those gambles into moral judgments. A decision that led to a failure is considered a mistake; but the same decision, if it led to success, is considered high expertise. The same action has a different label depending on its outcome.

This is the core of counterfactual thinking: imagining an alternative world where things turned out differently. Psychologists describe two main types:

  • Upward counterfactuals: “We’d have been ok if we had…”, which can be painful but sometimes useful. If we’re careful in their use, they help us see what might be improved for the future.
  • Downward counterfactuals: “It could have been worse…”, which might feel comforting and soothing, but is rarely instructive.

Both kinds risk making the world seem more controllable than it really is. Counterfactuals whisper in our ear that different choices would have guaranteed a different outcome. But the real world doesn’t work like that – if we change one variable, the network of interactions shifts in unpredictable, potentially cascading ways. And there’s no control group for the past: we can’t A/B test reality, so we can’t really say that another approach would have turned out differently.

Dekker calls counterfactual reasoning one of the biggest traps in investigation. It’s not that counterfactuals are evil, because used effectively, they can help us think about future prevention – but they can’t explain human behaviour. Saying what people didn’t do tells us nothing about why they did what they did. To learn, we have to reconstruct what the world looked like from their perspective at the time, not ours. To paraphrase Dekker – we need to get in the tunnel with them.

dekker counterfactuals tunnel
Dekker’s Tunnel. From The Field Guide To Understanding Human Error. P.33

That reconstruction (the “unfolding mindset”) is the work of effective investigation and learning. It means asking what information was available and visible, what explicit and implicit goals were people working towards, what pressures, constraints and distractions were present, and what state the people were in. It’s slower and messier than counterfactual shortcuts, but it’s the only way to understand Local Rationality – why a decision that now looks foolish made sense at the time.

This connects directly to psychological safety. Psychological safety isn’t just about speaking up in the present: it’s about how we talk about the past. Do people feel safe to be candid about their past actions, decisions, perspective and pressures? When we replay an incident, do we talk about what people missed, or do we ask what they saw? Do we focus on what should have happened, or on what actually made sense given their constraints and context? Do we treat decisions as expert gambles rather than tests of character? The way we tell the story shapes whether we learn or blame (and in the majority of cases, we can’t do both).

Put hindsight, counterfactuals, and the fundamental attribution error together, and we get a recipe for unhelpful investigation:

  1. Hindsight bias says the outcome was obvious.
  2. Attribution error says someone failed to see it because of who they are.
  3. Counterfactuals provide the tidy fix: “They should have done X.”

A disturbing number of real incident reports follow this pattern.

counterfactual
“He should have dived to his right.”

The alternative is slower but more honest: reconstruct rather than rewrite. We can attempt to reconstruct the unfolding mindset of the people involved. We can ask what looked risky or safe from their vantage point. As Dekker and David Woods both emphasise, people’s actions almost always make sense in context, even if that context is now invisible to us.

James Reason’s “substitution test” can help here – asking whether another well-motivated, equally competent person might have done the same thing in that situation. 

“Substitute the individual concerned, for someone else coming from the same domain of activity and possessing comparable qualifications and experience. Then ask the question ‘In the light of how events unfolded and were perceived by those involved in real time, is it likely that this new individual would have behaved any differently?’”

If the answer is yes, the issue isn’t the person, it’s the system. However, there’s a big caution here: the substitution test is highly vulnerable to hindsight too because we still have to reconstruct the at-the-time context before we apply the test.

Substitution decision tree. From James Reason, 2003
Substitution decision tree. From James Reason, 2003

Here are a few practical ways to mitigate counterfactual reasoning and shift our posture from judgment to learning:

  • Consider various alternatives to the actual outcome. Explore how it may have unfolded in different ways
  • Name the bias early. Simply saying, “Let’s watch for hindsight bias.” can help people notice when it creeps in. It’s not a fix though.
  • Reconstruct, don’t rewrite. Ask things like “What did we know then?” and “What options looked viable?” Try to keep current knowledge out until the end.
  • Use neutral language. “The decision was made based on X,” instead of “Bob failed to see Y.”
  • Broaden the view. Bring in different roles, disciplines, and perspectives. Complexity looks different from other angles.
  • Reframe counterfactuals as system questions. Instead of “They should have…” ask “What features of the system made that outcome more likely?”
  • Separate accountability from blame. Accountability can coexist with empathy, apologies and amends, but without context, accountability is just punishment.
  • Don’t ignore emotional counterfactuals. “I wish I’d done X instead of Y” can be a healthy part of processing regret. It helps us move on before real learning begins.

Joey, like most of us, was satisfied by a simple story, rewritten with 20/20 hindsight. But the real world doesn’t work that way. The goal of learning isn’t to find who “should have known better” – it’s to understand how the system and context made that decision a rational one at the time, and how we can make better outcomes more likely in the future.

Further Reading


Psychological Safety in Practice

Stammering and speaking on the phone

For people who stammer, stutter, tic, or have other speech differences, phone calls can be a nightmare. Just the pressure of having to speak at the right time, and the fear that being silent for too long means the call could be dropped, can be overwhelming. Everyone who knows me knows that I absolutely hate speaking on the phone! 

If you stammer, it could mean that when you finally get through to your GP after a long wait, you get hung up on because they think you’re not there. This report shows that many people with a stammer often can’t get through voice recognition systems, and are sometimes hung up on when they stammered on a call.

This amazing campaign by Stamma encourages businesses “Don’t hang up, hang on” and give people time to speak. Find out more here. 

Staying on stammering, this is a powerful episode of the Distraction Pieces Podcast with Scroobius Pip, titled “Dissecting Disfluency” with Cherry Burns). In this, Pip discusses his stammer, and how stammering is not the problem, it’s how the world meets the stammer that is the problem.


Neuroinclusivity and psychological safety

As we so often say, psychological safety looks different for everyone, but most psychological safety models assume that everyone processes feedback, attention, and risk the same way. Nicola Knobel pulled together this great aggregation of neurodiversity and psychological safety research, and put it into this table:


Imagining and implementing a responsibility culture in healthcare

Here’s a great paper by Philip Berry about patient safety and investigations, and trying to find the balance between delivering what many patients wish to see and fostering a culture that is not centred on blame – which seems very hard to achieve. 

The post Counterfactuals appeared first on Psych Safety.

❌