The Most Dangerous Leader in a Project: Reading Uncertainty Before It Becomes Crisis

On one project El Hassane Ben Ahmed describes, the greatest risk was not technical failure, budget pressure or stakeholder conflict. It was a leader who did not recognise that the project had entered a period of uncertainty.

On paper, everything looked acceptable. Reports were submitted, meetings happened, and from a distance the project seemed stable. On the ground, the team could feel the shift. Delays were becoming patterns. Small issues were turning into real risks. People were quieter in meetings, not because they agreed but because they no longer believed raising concerns would change anything. The team quietly managed reality while leadership managed appearances. Accountability stayed with the team. Authority did not.

That experience became Chapter III.3 of The Lessons That Stayed.

“Uncertainty rarely announces itself. It arrives quietly through delays, hesitation, and invisible tension. The leader who cannot read those signals does not simply fail to respond to the problem. They become part of it.”

The leader who does not see a decision coming

The chapter describes a specific kind of leader. They interpret the absence of visible crisis as evidence that no crisis exists. They treat silence as agreement rather than as the withdrawal of candour it often is. And they keep managing for the conditions that existed at the start of the project rather than the conditions that exist now.

What uncertainty looks like from the inside

The book identifies three signals.

Delays that become patterns

A single delay is an event with a cause. A series of delays is information about the project. When explanations start to repeat, or each delay is justified by a different external factor, the pattern is telling you something the individual explanations do not.

Silence in meetings

Teams in environments with low psychological safety do not argue with leadership assessments they think are wrong. They go quiet. A leader who reads that silence as agreement loses the most important early warning system they have.

Decisions made below formal authority

When team members start solving problems and managing risks without escalating them, it is rarely because they have decided to act alone. It is because they have concluded that formal leadership cannot provide what the project needs, and they have adapted.

Why leaders do not see it

Diane Vaughan’s analysis of the Challenger disaster introduced the normalisation of deviance: the gradual process by which conditions outside acceptable limits come to feel normal because they have happened before without catastrophe. Each small deviation lowers the threshold for the next.

There is also a structural reason. Formal reporting is designed to summarise, and summaries strip out exactly the weak signals that indicate emerging uncertainty: hesitation, tone, informal workarounds. Bent Flyvbjerg’s work on large projects documents how consistently plans underestimate risk. A leader who relies only on reports is relying on a filtered view.

What separates leaders who can read uncertainty

The chapter names three disciplines.

1. Seek information below the reporting layer

Talk regularly to the people doing the work, not only to those reporting on it. Ask open questions: what worries you about the next month? What is taking longer than expected? What are we not talking about?

2. Interpret silence actively

When a meeting goes quiet on a topic that should generate debate, treat that as a signal. Ask specific people for their view. Follow up privately. Make it explicitly safe to bring bad news.

3. Name uncertainty before it crystallises

Ronald Heifetz and colleagues describe “getting on the balcony”, stepping back to see the whole pattern. The leader who says “I think we may have entered a period of real uncertainty, and I want to understand it before we decide what to do” gives the team permission to tell the truth. Naming uncertainty is not weakness. It is the first step in managing it.

When the team manages reality alone

A team that has started managing reality without its leader usually passes through a predictable sequence: concerns are raised and not acted on, concerns stop being raised, and problems start being solved informally. Two consequences compound over time. Leadership’s picture of the project grows steadily less accurate, and the team carries accountability for outcomes it has no formal authority to shape. Eventually the gap becomes visible, usually at the worst possible moment.

Questions for project leaders

• When did someone last bring me bad news early?
• Which delays have repeated, and what do the repetitions have in common?
• In my last three meetings, which topics went quiet?
• Are decisions being made that I did not know about? Why did nobody bring them to me?
• If I asked the team privately how the project is really going, would their answer match the report?

The decision that was never made

The most dangerous moment in a project, the chapter concludes, is not the visible crisis. It is the long, quiet period before it, when the signals are there and nobody with authority acts on them. The lesson is not that project leaders should be pessimistic. It is that they should be attentive.

“The most dangerous leader is not the one who makes the wrong decision. It is the one who believes there is no decision to make.”