What Risk Are We Pretending Is Not There

A manager sits in a project review.

The plan is still on the screen. The milestones are mostly unchanged. The team has worked hard to keep the work moving, and there is a strong desire to stay positive. No one wants to sound negative, slow momentum, or raise a concern too early and look difficult.

So the conversation stays polite.

A delivery dependency is mentioned, but only briefly. A customer concern is described as something to monitor. A capacity issue is softened as a short-term pressure. A weak signal from the market is acknowledged, then quickly parked. Everyone knows there may be a risk, but the team does not really name it.

The risk is present, but it is not yet discussable.

This is one of the quieter challenges of management. Risk does not always arrive as a crisis. Often, it begins as a discomfort people can sense but have not yet made explicit.

What risk are we pretending is not there?

Why risks remain unnamed

Most teams do not ignore risk because they are careless.

They often avoid risk because naming it creates discomfort. If a manager names a risk, the team may have to revisit assumptions, adjust expectations, involve senior leaders, disappoint stakeholders or make harder choices. Naming the risk may reveal that the plan is weaker than people hoped, or that a promise made earlier now needs to be challenged.

There may also be social pressure. Teams want to appear confident. Managers want to show control. People may worry that raising risk will be interpreted as complaining, resisting, blaming or lacking commitment.

So the language becomes softer than the reality. “We should keep an eye on this.” “It may be worth monitoring.” “There could be some pressure later.” “We are still working through a few details.”

These phrases can be appropriate, but they can also become hiding places. They allow the team to acknowledge something without facing it directly. The problem is that unnamed risk does not disappear. It usually becomes more expensive, more emotional and more difficult to manage later.

Early risk is often easier to handle than late crisis.

Managers need to make risk discussable before it becomes unavoidable.

The difference between fear and foresight

Talking about risk is not the same as being negative.

This distinction matters. Some managers avoid risk conversations because they do not want to create fear or lower morale. But good risk conversations are not about pessimism. They are about foresight.

Fear says, “This will go wrong.”

Foresight asks, “What could go wrong, and what would we do if it did?”

Fear freezes the team. Foresight helps the team prepare.

A useful risk conversation does not assume failure. It tests the conditions for success. It asks where the plan is most exposed, what assumptions need to hold, what signals would tell us something is changing, and what options we should prepare before pressure increases.

This helps managers protect confidence rather than undermine it. People often feel more confident when risks are named clearly and handled thoughtfully. Silence may create calmness on the surface, but underneath it can create uncertainty.

When risk is not discussed, people may still sense it. They may talk about it privately, work around it quietly, or become cautious without saying why. The team loses the chance to think together.

The practical lesson

The practical lesson is this: managers should name risk early enough for the team to think, not late enough only to react.

A manager can open this conversation with a few practical questions:

  • What risk are we all aware of but not yet naming?

  • What assumption in this plan needs to be true for success?

  • Where are we relying on hope rather than evidence?

  • What signal would tell us this risk is becoming real?

  • What would be the cost of waiting?

  • Who needs to know earlier rather than later?

  • What action could reduce the risk now?

  • What option should we prepare if the risk increases?

These questions help risk become a management conversation rather than a late surprise. They also move the conversation away from blame. The point is to understand where the work is exposed and what can be done.

Managers do not need to dramatise risk. They need to make it visible enough to manage.

Risk needs a safe enough conversation

For risk to surface, people need to believe the conversation is safe enough.

This does not mean risk discussions should be soft or vague. It means people should not be punished for raising early concerns in good faith. If every risk becomes a personal failure, people will learn to hide problems until they can no longer be hidden.

Managers shape this environment through their response. When someone raises a concern, the manager can ask, “What are you seeing?” rather than, “Why did this happen?” They can ask, “What do we need to understand?” before jumping to judgement. They can distinguish between a weak signal, an emerging issue and a confirmed problem.

This helps the team speak earlier.

It also helps the manager avoid overreacting. Not every risk needs escalation. Not every concern needs a major change. But every meaningful concern deserves enough attention to decide what it is and what should happen next.

The goal is not to make the team risk-averse. The goal is to make the team risk-aware.

The real work

The real work is not only managing problems once they appear. It is creating the conditions where risks can be named, understood and acted on before they become harder to handle.

This is also one of the core reflection questions behind 100 Questions Every Manager Should Ask: What risk are we pretending is not there?

It is a useful question because many risks are not hidden by lack of information. They are hidden by hesitation, optimism, pressure or the desire to keep the plan looking clean.

The team can move from polite silence to shared awareness, from vague concern to practical preparation, and from late reaction to earlier judgement.

Risk does not need to dominate the work. But it needs a place in the conversation.

One question for reflection:

What risk needs to be named now, while there is still time to do something about it?

 

Continue Your Leadership Journey

If this article was useful, explore the practical resources designed to help you become a more confident and thoughtful manager.

 

📘 100 Questions Every Manager Should Ask

A practical reflection companion with 100 questions for real management situations.

 

🎓 Riverstone Mini Courses

Short practical video courses with workbooks and tools you can apply immediately.

 

Stay Connected

Receive new articles and practical leadership ideas as Riverstone grows.

Riverstone Coaching Cafe

Riverstone Coaching Cafe shares practical leadership reflections and resources for emerging managers.

Previous
Previous

Why Problems Should Surface Before They Become Crises

Next
Next

When a Scorecard Becomes a Conversation