How to uncover hidden struggles behind green dashboards

Theme 2 reveals the uncomfortable truths of operational leadership, with green dashboards illustrating key insights.
What senior leaders need to see behind a good result
Executive summary
A green dashboard confirms that a defined target was met. It may say little about the rework, extra transport, postponed tasks or management intervention needed to achieve it.
Reliable reporting connects the customer result with the work and cost behind it, makes uncertainty visible and shows variation across shifts.
Senior leaders also influence what gets reported through their response to bad news.
The aim is to build an operation that delivers consistently with less recovery work, creating opportunities to improve service and cost together.
Imagine the morning review at a distribution hub.
Departures are on time.
Additionally, productivity is above target, and labour spending is within budget.
The green dashboards display the current status.
During the night, however, supervisors moved people away from returns to clear the outbound work. An experienced manager arranged an extra vehicle. Incorrect shipment information required manual correction, and a planned training session was cancelled. The customer commitment was protected, but some costs sit elsewhere and some work is waiting for the next shift.
In this illustrative shift, the figures can all be correct. The conclusion that the operation is performing well is still open to question.
In my operations experience, long-serving managers sometimes saved performance when forecasts were wrong. Sometimes their judgement was wrong too. That is why I want to understand what happened behind the result before treating it as evidence that the operation is under control.
The first article in this series examined whether the operating plan reflects how work actually runs. This article asks whether the dashboard tells us how that plan was delivered.
The result depends on what you count
A vehicle leaving on time is useful information. It does not establish that all due shipments were loaded correctly. A service ticket marked closed may still lead to another customer call. A completed production order may have passed inspection only after substantial rework.
Before comparing results, leaders need a shared definition of completed work. What starts and stops the clock? Which orders are included? How are cancellations, missing scans and exceptions treated? If a promised date changes, can we still see performance against the original commitment?
Inconsistent answers can make two teams appear comparable when they are measuring different things. A changed definition can also create an apparent improvement without any improvement for the customer.
This does not always involve manipulation. A dashboard can become misleading through incomplete data or a definition that no longer fits the operation. Missing information should remain visible as unknown, with an owner and a date for checking it.
Show what it took to deliver
I would want a small amount of additional information beside the headline result. Enough to distinguish a well-executed shift from one that depended on repeated recovery.
| Headline result | What leaders also need to see |
|---|---|
| On-time departures | Due shipments left behind, extra vehicles and recovery work. |
| Productivity | Correctly completed work, repeated handling and changes in work mix. |
| Labour spending | Agency hours, costs booked elsewhere and unfinished work. |
| Backlog cleared | Age and urgency of remaining work, and tasks moved to another team. |
These are prompts for choosing useful measures, not a requirement to add every item to every dashboard. Start with the recurring losses that could change a management decision.
Tucker and Edmondson’s field research in nine hospitals describes how staff resolved immediate problems while the underlying causes remained. The work continued, but the fixes could prevent problems from reaching the people able to improve the system. [1] It is healthcare research, not a logistics benchmark. The mechanism is relevant: successful recovery can make a weak process less visible.
Some recovery is justified. An extra vehicle may be the right response to an unpredictable disruption. Record what it cost and why it was needed. Recurring corrections deserve a different discussion from a genuine one-off event.
Avoid false precision. Where exception handling is poorly recorded, begin with an explicit estimate and checks against actual shifts. If historical productivity already includes rework, do not add that time again. Costs not yet booked should be identified as provisional; postponed work needs its own visibility.
A result is only useful when we can see what it took to achieve it.
Jan Salomons
The average can hide the operational problem
A weekly service percentage may meet target while the same departure fails repeatedly. Average turnaround time can improve while the oldest urgent orders wait longer. A lower cost per item may reflect a higher share of easy work.
Show the result over time, and look at the shift, route, customer group or work type where a decision is needed. Keep the relevant volume and work mix alongside it. Large and small groups should not disappear into an unweighted average of percentages.
Meeting a target also differs from having a stable process. NIST’s statistical guidance distinguishes control limits, which help assess consistency, from specification limits, which describe required performance. [2] A process can be consistently below the required standard. Equally, a few green days do not establish dependable delivery.
For leaders, the practical question is whether the pattern reflects an identifiable disruption, ordinary variation or a lasting change. One red day is a reason to investigate; it is not, by itself, proof that a supervisor has lost control.
Your response to red affects the next report
If every red indicator leads to public criticism, while green ends the discussion, managers have an incentive to protect the colour. They may spend more effort explaining away exceptions than understanding them.
Bevan and Hood’s analysis of performance targets in English healthcare documents measurement problems and gaming, including cases where reported achievement came at the expense of aspects of service outside the target. [3] Their findings warn against treating a narrow measure as a complete account of performance.
I would apply that warning by asking how the result was achieved, including when it is green. What required intervention? What remains unfinished? What does the team need a senior leader to decide?
An honest red result still requires action. A manager should explain the evidence, immediate containment and follow-up. Senior leaders should provide clear priorities and authority where the decision exceeds the manager’s remit. Deliberate misreporting and an openly reported operational problem need different responses.
Use the Obeya room to connect results with decisions
An Obeya room can help when it brings service, cost and the work behind them into the same conversation. A wall full of charts will not do that on its own.
Return to the illustrative hub. The review should show that departures were protected, an extra vehicle was used and returns work was carried over. The team can then distinguish the immediate decision to protect service from the recurring causes that need improvement.
Incorrect shipment information might require action with the sending location. Repeatedly postponed training might require protected capacity and a decision above the shift manager’s authority. Each needs an owner, a review date and evidence that the change has reduced the problem.
Removing errors can reduce relabelling, extra transport and missed commitments together. That is one way service reliability and cost efficiency can build on each other, a relationship I will examine more deeply later in this series. Time released becomes capacity; it becomes a financial saving when spending actually changes. Some service commitments will still require additional capacity.
Make green credible
Before relying on a dashboard, I would expect three basic requirements to be in place:
- Shared definitions and traceable data, with material exclusions, estimates and unknowns made explicit.
- Visibility of the result and its consequences, including recovery work, deferred tasks and relevant variation between shifts.
- A review process that turns evidence into decisions, with clear ownership and follow-through on recurring problems.
These requirements take more than a reporting redesign. They depend on leaders who stay close enough to the work to question the numbers and respond constructively when the picture is uncomfortable.
At the next performance review, take one green result and ask the team to explain what it took to achieve it. If the answer includes repeated rescue work, the improvement discussion belongs on the agenda even though the target was met.
In my operations leadership and culture development programme, I work with management teams, sometimes help them introduce an Obeya room and coach the operations manager or the level above to turn these conversations into consistent decisions and follow-through.
References
1. Tucker, A. L. and Edmondson, A. C. (2003). Why Hospitals Don’t Learn from Failures: Organisational and Psychological Dynamics that Inhibit System Change. California Management Review, 45(2), 55–72.
2. NIST/SEMATECH. e-Handbook of Statistical Methods, section 6.3.2, What are Variables Control Charts? Guidance on process consistency and the distinction between control and specification limits.
3. Bevan, G. and Hood, C. (2006). What’s Measured Is What Matters: Targets and Gaming in the English Public Health Care System. Public Administration, 84(3), 517–538.
