The psychology of project escalation: Why reality travels so slowly

Most projects do not suddenly become Red. They drift there.

Long before governance catches up, project leaders usually sense that something has changed. Delivery slows subtly. Conversations become more cautious. Confidence becomes qualified rather than certain. Recovery plans become increasingly optimistic while the mood within the team quietly shifts.

Looking back, everyone asks the same question: Why didn't we raise this sooner?

A better question is why intelligent, experienced people delay escalating concerns that, with hindsight, were already visible.

Why escalating concerns feels so difficult

Most organisations already have governance processes. They have RAID logs, steering committees, programme boards and escalation routes. The problem is psychological. Escalation is ultimately a human decision, and human decisions are rarely made through logic alone.

Escalating a technical issue is relatively straightforward. Escalating concerns about delivery confidence, programme viability or team performance is something else entirely because delivery is deeply personal. Admitting that a programme is drifting can therefore feel less like reporting operational information and more like questioning professional competence.

Research by social neuroscientists Naomi Eisenberger and Matthew Lieberman suggests that threats involving status, belonging and credibility activate many of the same neural systems associated with physical danger. Project delivery is hardly life-threatening, but our brains respond as though our professional identity is under attack.

The psychological biases that delay project escalation

That instinct is reinforced by several well-established psychological biases. Daniel Kahneman and Amos Tversky transformed our understanding of judgement under uncertainty, work for which Kahneman later received the Nobel Prize in Economic Sciences. Their work laid the foundations for our understanding of cognitive biases such as optimism bias, the tendency to consistently overestimate positive outcomes. In projects, that optimism rarely sounds irrational. Another sprint will stabilise things. Recovery is just around the corner. Each judgement appears reasonable in isolation. Collectively, however, they encourage organisations to postpone acknowledging what the evidence is already beginning to suggest.

Their work on Prospect Theory adds another important dimension. People experience potential losses more intensely than equivalent gains. Escalating a concern may protect the programme, but it can also feel like accepting the loss of confidence, control or credibility. Maintaining hope often feels safer than confronting deterioration.

Leon Festinger's influential theory of cognitive dissonance explains how people unconsciously seek to reduce the psychological discomfort caused by conflicting beliefs. When a capable delivery team begins to recognise that a programme may no longer be under control, that discomfort often leads people to reinterpret the evidence rather than accept the emerging reality. Missed milestones become isolated incidents, delivery trends become temporary setbacks and governance reporting drifts slightly ahead of operational reality. Importantly, this is rarely dishonest. It is a human attempt to reduce psychological tension.

How organisational culture reinforces silence

As these individual behaviours become shared, they begin shaping the organisation itself. Social psychologist Irving Janis introduced the concept of groupthink to explain how cohesive groups can suppress challenge in favour of consensus. In pressured programmes, optimism can become self-reinforcing because few people want to be the first to challenge the prevailing narrative.

Alongside this sits pluralistic ignorance, where individuals privately believe something is wrong but assume everyone else remains confident because nobody else is saying otherwise. It is entirely possible for an executive steering group to leave a meeting with every member privately concerned while each believes they were the only one with doubts.

Over time, this becomes what sociologist Diane Vaughan described as the normalisation of deviance, a concept developed through her landmark research into the Space Shuttle Challenger disaster. Small departures from accepted standards gradually stop feeling unusual simply because they did not cause immediate failure. Repeated milestone slippage, compressed testing or overloaded teams become accepted features of delivery rather than signals that something fundamental needs to change. Without anyone consciously deciding to lower expectations, the organisation quietly moves its own escalation threshold.

Why some leaders escalate risks earlier than others

Yet not everybody responds in the same way. Some leaders consistently escalate earlier than others despite having access to the same information. The difference is rarely technical competence. More often, it lies in how they interpret uncertainty.

Leaders who escalate early separate their professional identity from programme performance. They see emerging risks as information worth sharing rather than evidence they have failed. Uncertainty becomes the reason to start a conversation, not the reason to delay one. Leaders who wait often seek certainty before speaking. In complex projects, certainty usually arrives only after recovery options have begun disappearing.

Psychological safety is the foundation of effective escalation

This is why governance alone rarely changes organisational behaviour.

Amy Edmondson's work on psychological safety (see Building a Psychologically Safe Workplace) showed people are more willing to raise concerns when they believe they can do so without embarrassment, blame or reputational damage. Psychological safety is frequently misunderstood as lowering standards or avoiding difficult conversations. The opposite is often true. Teams with high psychological safety surface problems earlier because people feel able to discuss uncertainty before it becomes failure.

Every leadership response teaches the organisation something. When leaders react defensively to difficult news, dismiss emerging concerns or criticise people for escalating too early, they unintentionally increase the psychological cost of honesty. Concerns are raised later and governance reporting becomes more cautious.

Reality begins travelling more slowly through the organisation.

How leaders can create a culture of early escalation

Conversely, leaders who respond with curiosity rather than judgement change the psychology of escalation. They ask what people are seeing before asking who is responsible. They treat uncertainty as valuable information rather than evidence of incompetence. Over time, those behaviours make escalation routine.

More often, projects fail because reality travelled too slowly through the organisation for intervention to remain possible.

Ultimately, the psychology of project escalation is not about encouraging people to speak up. It is about understanding why intelligent, capable and well-intentioned people often remain silent, and creating environments where telling the truth becomes psychologically easier than protecting optimism.