Why Problems Should Surface Before They Become Crises

A manager receives an urgent message.

Something has gone wrong. A customer issue has escalated. A deadline is now at risk. A dependency has failed. A small operational issue has become visible to senior leaders because it has finally affected the outcome.

The manager gathers the team quickly.

As people explain what happened, a familiar pattern appears. The problem did not begin today. There were earlier signs. Someone noticed the handover was becoming fragile. Someone else had concerns about workload. A recurring customer complaint had been mentioned before. A workaround had become normal. A delay had been absorbed quietly several times.

The crisis feels sudden, but the problem was not new.

It had been present in the system for some time.

This is one of the difficult truths of management. Many crises are not completely unexpected. They are problems that were sensed, softened, worked around or postponed until they became too large to ignore.

Problems should surface before they become crises.

Why problems stay below the surface

Problems often stay hidden for understandable reasons.

People may not want to create trouble. They may think the issue is not serious enough yet. They may believe they should solve it themselves before raising it. They may worry that escalating too early will make them look incapable, negative or difficult.

Sometimes the culture rewards smooth reporting more than honest visibility. Teams learn to present confidence, tidy updates and progress narratives. Small problems are described as manageable. Repeated issues are framed as exceptions. Workarounds become invisible because they have become part of how the team gets things done.

Managers can unintentionally reinforce this. If a manager reacts badly to early concerns, people may wait until they have no choice. If every problem becomes a blame conversation, people will protect themselves. If only good news travels easily, the organisation loses the chance to learn early.

This does not mean people are hiding the truth deliberately. Often, they are trying to be helpful. They absorb friction, protect others from noise, and keep the work moving.

But a problem that is repeatedly absorbed is still a problem.

If it is not surfaced, the system does not get a chance to improve.

Early signals are easier to manage than late surprises

A problem is usually easier to handle when it is still small.

An early concern gives managers options. They can investigate, adjust resources, clarify ownership, reset expectations, change the sequence, involve the right people, or decide consciously to accept the risk.

A crisis reduces options.

By the time the issue has escalated, time is shorter, emotions are higher, stakeholders are more exposed and the cost of action is usually greater. The conversation shifts from learning to urgency. People may focus on who knew what, who should have acted, and why the issue was not raised sooner.

That is why managers need to pay attention to weak signals.

A weak signal may be a repeated small delay, a recurring exception, a workaround that keeps appearing, a handover that depends on one person, a customer complaint that sounds familiar, a team member who keeps saying “we are managing” with visible strain, or a metric that looks fine only because people are pushing harder underneath it.

Weak signals do not always mean a crisis is coming.

But they deserve enough attention to decide what they mean.

The practical lesson

The practical lesson is this: managers should create routines where problems can surface early, before urgency becomes the only teacher.

A manager can use a few practical questions:

  • What problem are we working around instead of solving?

  • Where are small issues repeating?

  • What feels harder than it should?

  • What has become dependent on individual effort rather than a reliable process?

  • Where are people absorbing pressure quietly?

  • What issue would become serious if one more thing went wrong?

  • What are we not escalating because we still think we can manage it?

  • What conversation would be easier to have now than later?

These questions help managers move from late reaction to earlier visibility. They also reduce the emotional weight of problem-raising. The point is not to create alarm. The point is to make reality visible early enough for good judgement.

Managers do not need every small issue to become a major escalation.

They do need a way for repeated friction, emerging risk and important weak signals to enter the management conversation.

Surfacing problems requires trust

Problems surface earlier when people trust the response.

If a team member raises an issue and the first response is blame, frustration or dismissal, they may think twice next time. If the response is curiosity, clarity and shared problem-solving, the team learns that early visibility is useful.

The manager’s response matters.

Instead of asking, “Why did this happen?”, the manager might first ask, “What are we seeing?” Instead of asking, “Who owns this?”, the manager might first ask, “What does the system need?” Instead of treating the concern as failure, the manager can treat it as information that helps the team act earlier.

This does not remove accountability. If standards have been missed, they still need to be addressed. But accountability works better when it is grounded in reality. If problems surface late, accountability becomes more emotional and less useful. If problems surface early, accountability can focus on ownership, learning and prevention.

Trust does not mean avoiding hard conversations.

It means people believe hard realities can be raised before they become harder.

The real work

The real work is not only solving crises quickly. It is building the management conditions where problems can surface before they become crises.

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 problems and risks often become serious when the team has sensed them but not yet brought them fully into the open. The issue may not be hidden by lack of intelligence. It may be hidden by politeness, optimism, workload pressure or fear of creating noise.

Managers help teams when they make early truth-telling normal.

A good management rhythm creates places for reality to appear: regular reviews, one-on-ones, retrospectives, risk discussions, customer feedback loops and operating meetings where weak signals are taken seriously.

The aim is not to make the team anxious.

The aim is to make the team aware.

When problems surface early, the team has more choice. It can think, learn, adjust and act before the issue becomes a crisis.

One question for reflection:

What problem in your team needs to surface now, while it is still manageable?

 

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

What the System Falls Back on Under Pressure

Next
Next

What Risk Are We Pretending Is Not There