The glory of what did not happen: for the people who do the work well but have no catastrophe to prove it

At two in the morning, the hotel was quiet.

At reception, an employee was finishing the usual checks of the night shift. The reports had to match. The financial entries had to be accurate. Every discrepancy needed an explanation before the work was handed over to the next shift.

In one of the checks, something did not match.

A small difference. Nothing that gave the immediate impression of a serious problem. It could have been left for the morning, with a short note for the colleagues.

But he decided to look into it.

He checked the entries, compared the information and found the source of the error. He corrected it according to procedure, documented it and carried on with his work.

In the morning, his colleagues took over an orderly shift.

There was no debate about that entry. No long investigation was needed. Nobody lost time looking for an explanation that had already been found.

The manager read the report.

No significant incident.

Everything normal.

The employee went home.

And the work he had done remained almost invisible, precisely because he had done it well.

In the world of operations there is a particular injustice in the way attention is distributed.

We see the people who solve crises.

We remember those who step in when a process has failed, when a customer has become angry, when a system has stopped or when a problem has gone out of control.

And often, rightly, we appreciate them.

Taking responsibility in a difficult situation takes experience, resolve and the ability to keep your judgement when others are under pressure.

But there is another category of professionals too.

They are the ones who notice problems before they become crises.

Those who check a detail others consider unimportant. Those who ask one more question before approving an action. Those who refuse to close a task just because the system lets them press the finish button.

Their work usually has no dramatic moment.

No urgent phone calls, no extraordinary meetings, no people running along corridors.

Just a problem identified, an action taken in time and a day that goes on normally.

And in many organisations, normality is so unspectacular that nobody thinks to appreciate it.

It is easier to tell the story of a crisis solved than the story of a crisis that did not happen.

In the first case we have a beginning, a conflict and an ending.

The system failed. The operation was interrupted. A professional stepped in. The situation returned to normal.

The contribution is visible.

In the second case, the story can be summed up in one sentence:

Everything went well.

But that sentence can hide whole hours of professional work.

There may have been checks, analyses, small interventions and careful decisions that kept the process within standard.

There may have been people who identified risks, corrected errors and documented weaknesses that needed attention.

Their work did not produce a big event.

It produced the absence of one.

And here lies the paradox.

The better prevention works, the fewer visible reasons the organisation may have to notice it.

Yet a distinction has to be made that is often lost in the effort to praise prevention.

The fact that a problem did not happen does not automatically prove that someone prevented it.

A machine may not break down even without the last technical check. A mistake that was caught might not necessarily have led to any serious consequence. A risk that was identified might have had a very low probability of materialising.

So it is not honest to present every preventive action as a catastrophe avoided.

A serious organisation does not need to invent hypothetical disasters to justify the value of professionalism.

It is enough to understand what risk existed, what check was carried out, what was found and how the chance or the impact of a failure was reduced.

This is the difference between evaluation based on evidence and praise that wants only a good story.

Because good prevention is not magic.

It is discipline in the face of uncertainty.

It does not promise that nothing bad will ever happen.

It tries to lower the chance that something goes wrong and to limit the consequences if it does.

And that takes a kind of professionalism that often has no reason to step into the spotlight.

There is a strange contradiction in many workplaces.

An employee steps into a crisis and stays several hours beyond his shift to restore normality.

The managers congratulate him. His contribution is mentioned in meetings. Perhaps he even gets a special recognition.

Another employee had been warning for weeks about the weakness in the process that caused the crisis.

He had documented the problem. He had asked for an extra check. He had suggested a small change that could have reduced the risk.

His proposal had been put off.

Perhaps because it did not look urgent.

Perhaps because it took time.

Perhaps because, at that moment, everything was still working.

When the problem erupts, the organisation enthusiastically rewards the man who solved it.

But it rarely goes back to the warning it had received before the situation got worse.

So a silent message is created.

Preventing is useful.

Saving the situation is glorious.

People begin to understand which actions draw attention and which are considered an ordinary part of the duty.

And without meaning to, the organisation may begin to reward the ability to cope with consequences more than the ability to reduce their causes.

It is not that the people who solve crises do not deserve recognition.

The problem is that those who work to prevent them stay outside the success story.

But this injustice has a deeper dimension too.

Preventive work often requires doing something that modern organisations do not much like.

Slowing down for a moment.

An employee stops a process because he notices a discrepancy.

A supervisor asks for a document to be reviewed before approval.

A technician refuses to declare a machine ready without finishing the necessary check.

In an environment where speed has become the main measure of success, these people can look like an obstacle.

Why do we have to check again?

Why are we losing time?

Why must work stop for a problem that may never happen?

These questions are not always unreasonable.

Time costs. Unnecessary checks can weigh down a process. And not every doubt justifies interrupting an operation.

But a manager must be able to tell professional care from needless bureaucracy.

Because there is a great difference between a check carried out only because it has always been done and a check that guards against a real risk.

The first deserves to be reviewed.

The second deserves to be understood and kept.

An organisation that does not make this distinction can become faster and faster while slowly losing the mechanisms that kept it reliable.

And here a question appears that managers must take seriously.

What happens to an employee who keeps identifying problems before they create consequences?

At first he may be considered careful.

Later, if his warnings get no attention, he may begin to look like a man who sees problems everywhere.

Someone will tell him he should be more practical.

Another that he need not worry about every detail.

He may even hear the most dangerous sentence of an organisation that has begun to confuse luck with competence:

“We've always worked this way and nothing has happened.”

But the absence of a previous incident is not a guarantee of the safety of a process.

A practice may have worked for years because of favourable conditions, the experience of the people or simply because the risk has not yet materialised.

This does not mean that every warning is accurate.

It means that warnings must be examined on the basis of facts, not on the comfort the past gives us.

Because the person who identifies a weakness is not necessarily an enemy of productivity.

Sometimes he is the only one trying to protect tomorrow's productivity.

There is another reason why prevention does not always get the attention it deserves.

It is hard to claim as a personal success.

When a manager solves a crisis, he can tell what he did.

When a team keeps normal operation for months on end, the contributions are spread out.

One has followed the procedures.

Another has improved the planning.

Another has reported a deviation before it became a problem.

Someone has trained the new employees.

Someone else has corrected a small weakness that kept recurring.

None of them necessarily has a spectacular story to tell.

But together they have created something every organisation should value.

Reliability.

And reliability is not built by a single heroic act.

It is born of hundreds of small actions done properly, even when nobody is watching.

Yet here too another mistake must be avoided.

Prevention cannot become an excuse for creating endless checks.

An organisation can fill up with forms, checklists, approvals and procedures that once had a reason to exist, but that nobody remembers any more.

Every new check adds time and effort.

Some are essential. Some are useful only under certain conditions. Some may have become redundant after technological or organisational changes.

A good manager must not defend them all blindly.

He must understand them.

What risk is this procedure meant to control?

How serious would the consequences of a failure be?

Is this check the best way to reduce the risk?

Is there a simpler, safer or more automated solution?

And, if the procedure is removed, what will replace its protective function?

These are the questions of mature management.

Because professionalism does not lie in carrying out as many checks as possible.

It lies in understanding which checks matter and why.

An organisation that wants to value prevention must also change the way it understands performance.

It is not enough to count incidents.

It must also look at the risks identified, the discrepancies corrected, the checks that reveal real weaknesses and the measures put in place to avoid their recurrence.

But these measures too need care.

If the number of reported problems becomes a target to be reduced at all costs, people may begin to report less.

If the number of risks discovered becomes a target to be raised, trivial matters may start to be recorded too.

Indicators must help judgement.

They must not replace it.

A serious manager does not ask only how many problems were reported.

He wants to understand whether the reporting was reliable, whether the risk was dealt with and whether the organisation learned something that made the process more robust.

This is the difference between collecting statistics and building a culture of prevention.

Because a process does not become safer just by recording its weaknesses.

It becomes safer when someone takes responsibility for correcting them.

Perhaps the most important question is what kind of professionalism we want to build.

Do we want people who know how to act only when the situation becomes urgent?

Or do we want people who have the skill, the authority and the calm to identify problems before they take on large proportions?

The ideal answer is both.

An organisation needs professionals who know how to step into a crisis.

But it must not build its identity around the crisis.

It must not take chaos as proof of the importance of the work.

It must not teach people that they have to wait until a problem becomes serious to deserve attention.

And above all, it must not confuse the calm of a well-organised operation with a lack of effort.

Because the people who keep a process stable are not necessarily less capable than those who step in when it fails.

Sometimes their work takes more patience, more discipline and a kind of responsibility that is not rewarded with the adrenaline of urgency.

It takes doing the right thing before there is a dramatic reason to do it.

This responsibility is not always easy.

The person who works to prevent problems may grow tired of seeking attention for risks others do not see.

He may begin to doubt whether his effort makes sense.

He may see that the colleague who solved an incident receives public thanks, while his work to prevent similar incidents passes unmentioned.

But this must not lead us to a competition between two kinds of professionalism.

The person who steps into a crisis is not the opponent of the one who works to prevent it.

Both can be indispensable to an organisation.

The problem is the way leadership sees, values and rewards their contributions.

A good manager has no need to declare a hero of every employee who completes an ordinary check.

But he must understand that part of the most valuable work is not visible in the final results.

He must know how to value reasonable care, honest reporting, process improvement and the avoidance of needless work that would arise from mistakes.

Not with mechanical praise.

With attention, with support, with chances to develop and with decisions that show the organisation takes that kind of work seriously.

In the end, everything comes back to the way we understand success.

In a world that prefers dramatic stories, an uneventful day seems like something not worth telling.

A system that did not stop.

A customer who had no reason to complain.

A mistake that was found during a check.

A risk that was dealt with before it caused consequences.

These can be important results.

But they are not always visible proof of anyone's skill.

And precisely for that reason they need managers who know how to see beyond what makes noise.

Because there are two ways a day can end without problems.

In one, nothing went wrong because conditions were favourable.

In the other, people identified the risks, respected the necessary checks and took decisions that made failure less likely.

From the outside, both days may look the same.

In the report, both may have the same result.

But a manager who regards them as equal just because they ended without incident has not yet understood the difference between luck and a reliable system.

On the morning after that quiet night, the employee finished his shift and went home.

Nobody asked him to explain a crisis.

Nobody phoned him about an unsolved error.

Nobody congratulated him for a big problem he had avoided, because nobody had proof of how big that problem might have become.

But something concrete existed.

A discrepancy had been identified. An error had been corrected. The work had been documented and handed over in good order.

That was all.

And perhaps that was enough to call it good work.

Not because he had saved the world.

But because he had taken seriously a responsibility he could have neglected.

And this is a kind of professionalism that should not need catastrophes to earn respect.

A mature manager must know that not every success has the shape of a problem solved at the last minute.

Some successes have no spectators.

No applause.

No photographs for the year-end presentation.

They have only a system that keeps working and people who can do their job without having to face the consequences of an avoidable mistake.

And perhaps this is the hardest form of professional glory: to contribute decisively to a result, without needing anything to go wrong to make your contribution visible.

Because an organisation that sees people only when the crisis erupts risks sooner or later losing precisely those who took care that it would not erupt.

Then it will understand, perhaps too late, the value of their work.

Not from what they had done.

But from everything that, in their absence, will begin to happen.