The green day that needs investigating: when success is measured by what is seen and failure hides in what is not counted

At the end of the day, the screen showed that everything had gone well.

Shipments had gone out on time. Productivity had hit its target. The average processing time had improved. No critical deviation had been recorded.

The indicators were green.

The manager glanced at the table, leaned back in his chair and smiled. It was one of those days when he would not have to prepare explanations for his superiors. The figures spoke for themselves.

On the other side of the operation, an employee was finishing the correction of some mistakes that were not included in the productivity measure. Another had put off until tomorrow a task that did not affect the day's target. Some problems had been solved by individual intervention, outside the normal flow of work.

None of this changed the colour of the table.

And that was precisely the most interesting part of the whole story.

Because the numbers were not necessarily wrong.

The problem was that nobody was asking what had been left outside them.

In management, performance indicators are one of the most important tools of leadership.

Without measurement, many decisions would rest on impressions, intuition or people's selective memory. We would not know whether a process is improving, whether an intervention has worked or whether resources are being used efficiently.

An organisation that measures nothing sooner or later risks mistaking belief for proof.

But an organisation that measures everything can fall into another mistake.

To believe that what can be measured is everything that matters.

Here begins one of the greatest contradictions of modern management.

The more we perfect the ability to turn work into numbers, the more we risk forgetting that a number represents only a part of reality.

An indicator can tell us how fast a process finished.

It does not automatically tell us how much work it took to correct the mistakes it produced.

It can tell us that a customer got an answer within the deadline.

It does not necessarily tell us whether his problem was solved.

It can show that a department hit its productivity target.

It does not always show whether it did so through a sustainable process or thanks to people who kept working at the limit of their capacity.

Measurement is necessary.

But interpreting it is a responsibility.

And it is in that responsibility that leaders who administer indicators begin to part from those who understand operations.

There is a simple mechanism that can change the behaviour of an organisation.

Set a target. Link it to performance evaluation. Demand that it be reached consistently.

After a while, people will begin to organise their work around that target.

This is natural. In many cases it is even desirable.

But what happens when the indicator does not fully represent the result the organisation wants?

If only the speed of completion is measured, people may begin to give priority to tasks that close quickly.

If only the number of cases processed is valued, the more complicated cases may be left behind.

If a department is judged only by its own cost, it may take decisions that cut its expenses but raise costs elsewhere in the organisation.

Nobody has to manipulate data for this to happen.

It is enough that people understand what is rewarded.

And gradually, instead of the indicator helping us understand the work, the work starts to adapt so as to look good in front of the indicator.

This is the moment when the instrument of control risks becoming the real objective.

And the purpose for which it was created fades into the background.

Take a common example.

An operation must be finished within a set deadline.

The leader has defined the target. The team knows it. Everyone knows that delays will call for explanations.

On a hard day, the load is heavier than usual. Some technical problems appear. Part of the staff is absent.

The team tries to save the result.

Some secondary tasks are postponed. The most capable employees take on extra responsibility. The checking of part of the work is done later. People finish the shift tired, but the target is reached.

The report is green.

At first glance, this is a success story.

And it may truly be one.

In an exceptional situation, the team's ability to keep the service going is of great value.

But if the same situation repeats again and again, the leader should begin to worry.

Because what one day can be considered extraordinary dedication may, over time, turn into an ordinary way of hiding the weaknesses of the system.

And here arises the question that many performance reports do not contain:

How much did it really cost us to reach this target?

Not only in money.

In time shifted elsewhere. In work left unfinished. In mistakes that will need correcting. In accumulated tiredness. In the capacity we may lack tomorrow.

Because a target reached today is not necessarily a success, if the way it was reached makes it harder to reach tomorrow.

One of the most underrated indicators of the quality of management is not simply the result.

It is the ability to repeat that result without constantly demanding extraordinary sacrifices.

A good system must be able to work even when people are not at their best.

When an employee is absent for a legitimate reason.

When the load changes within predictable limits.

When a customer makes a more complicated request.

When an ordinary mistake needs correcting.

If every small change calls for the immediate intervention of one particular person, then we have reason to examine the robustness of the process.

But performance tables do not always tell apart this weakness.

They see the finished result.

Not necessarily the fragility of the way it was produced.

That is why a day with excellent indicators may deserve as much attention as a day with poor results.

Not because success should be treated with permanent suspicion.

But because we must understand what made it possible.

If the result came from an improved process, then the organisation has something to learn and to repeat.

If it came from an extraordinary individual effort, then the organisation has something to appreciate, but also a weakness to examine.

The difference is decisive.

In the first case, success may have become part of the system.

In the second, the system may have survived thanks to someone.

Another problem appears when departments begin to live within the limits of their own indicators.

For the first department, the work ends when the product leaves the processing area.

For the second, success is measured when the transport departs on time.

For the third, the target is met when the complaint is logged and receives its first answer.

Each can reach its own result.

But the customer does not live within these administrative boundaries.

He cares whether the product arrived complete, whether the service was done as promised and whether the problem he reported was solved.

An organisation can have several departments with green results and a customer who has had poor service.

This is not necessarily a mathematical contradiction.

It is a problem in the way success has been defined.

Because a process can be efficient at one point and harmful to the overall result.

A department can improve its own indicator by shifting the work to another.

A team can cut handling time by leaving more work for correction later.

And each leader, confined within his own report, may have accurate proof that he has done a good job.

The problem does not necessarily lie with the individuals.

It lies with an organisation that asks people to win in their own part, without making sure that all the wins together make a good result.

Here a particular temptation of management appears.

To treat every green indicator as proof that earlier decisions were correct.

It is an understandable temptation.

Leaders are responsible for results. They must evaluate performance, report progress and show that the organisation's resources are being used properly.

But there is a difference between being responsible for results and being interested only in the results that protect your reputation.

A leader who sees the report as proof of personal success may begin, without realising it, to avoid the questions that complicate that success.

Why was there work left for the next shift?

Why were so many manual interventions needed?

Why were extra people needed to reach the target?

Why did the number of completed cases rise while unresolved problems keep piling up?

These questions do not devalue the achievement.

They put it in context.

And a leader who cannot bear this context may sooner or later begin to defend the report instead of defending the organisation.

But another extreme must also be avoided.

Not every green indicator hides a problem.

Not every tired employee is proof of a failed system. Not every task put off until tomorrow is a sign of mismanagement. There are reasonable compromises, operational priorities and situations where the best decision is not the one that ensures every task is finished within the day.

A management system must not turn into a machine of suspicion where every positive result calls for a disciplinary investigation.

On the contrary.

It must create the chance to understand results without fear.

If a team has performed exceptionally well, the leader must appreciate it.

But he must also ask what worked better than usual.

If the result was reached thanks to a temporary measure, it must be documented as such.

If a better way of working was identified, the possibility of making it the standard must be considered.

If a problem was put off, it must not vanish from attention just because it did not affect the main indicator.

That is why indicators must come with a clear understanding of what they measure, with quality checks and with a view of the consequences the process produces.

Speed must be seen together with accuracy.

Productivity with the work that needs correction.

Meeting deadlines with the tasks left open.

Cost with quality and sustainability.

Not to create an endless number of tables.

But to avoid the situation where one indicator improves by damaging something else the organisation has a responsibility to protect.

There is a very simple method for bringing leadership closer to reality.

Follow a process from start to finish.

Not only on the screen.

In the work being done.

See what happens before a task is logged as completed. Understand whether there are steps employees carry out outside the system because the official procedure does not provide for them. Examine the cases that call for repeated intervention.

And above all, talk to the people who do the work.

Not to ask whether they are satisfied with the result, because the report already gives that answer.

But to ask what they had to do to reach it.

What got harder today?

What was left unsolved?

Which problem will repeat tomorrow if we change nothing?

These questions can bring to light information that a table was not built to record.

But they have value only if people are not punished for the answers.

Because an organisation that rewards only the green indicator and then asks for transparency about the problems that came with it is giving employees two messages that may collide.

Do not fail.

But tell us every difficulty.

A mature leader must make it possible for both demands to live together: responsibility for results and honesty about how they were reached.

Without this, reporting turns into an exercise in self-defence.

In the end, a performance indicator is a tool.

No indicator has moral responsibility for the decisions taken in its name.

It does not decide whether an employee should be asked to take on an extra load. It does not decide whether a check can be skipped. It does not determine what level of quality should be accepted for the sake of speed.

These are human decisions.

And responsibility for them cannot be transferred to a formula.

A leader cannot say something was right just because it helped reach the target.

Just as he cannot claim a process was successful only because the system recorded it as such.

In the world of operations, reality has an unpleasant habit.

It does not obey the colours of tables.

A mistake that was not corrected will demand attention again.

A task that was put off will go on existing.

A weak process will show its weakness again, even if for some days it was held up by the extraordinary dedication of people.

That is why the value of a report lies not only in its ability to show whether the target was reached.

It lies in how it helps us understand what must be kept, what must be changed and which risks must not pass unnoticed.

At the end of that day, the manager could have done something else.

He could have looked at the green table and congratulated the team.

Then he could have gone down to the operation.

He could have asked what had worked well and what had had to be compensated for to reach the result.

Perhaps he would have found that the improvement was real and lasting.

Perhaps he would have found a new way of working that deserved wider use.

Or perhaps he would have understood that the targets had been reached only because some people had taken on costs and responsibilities the system did not see.

In all three cases he would have gained something more valuable than a beautiful table.

He would have gained knowledge.

Because leadership does not require you to doubt every success.

It requires you not to take success as a reason to stop thinking.

A red indicator calls for an explanation.

But a green indicator also deserves to be understood.

Not to look for failure where there is none.

But to know whether the organisation has truly built a better way of working, or has simply learned to reach the target by leaving consequences outside the measurement.

Because a report can prove that the target has been reached. It cannot by itself prove that the way it was reached was right, healthy or sustainable.

And if a leader uses it only to prove success, he risks losing the most important function of measurement: the chance to discover what still does not work.

In the end, the most important question of a green day is not always:

“Did we reach the target?”

Sometimes it is:

“What did we have to not see, for everything to look in order?”

Because the numbers may be accurate.

And still, our conclusion may be wrong.