Key Takeaways

  • A green risk or safety dashboard means the selected measures met their thresholds; it does not establish that every critical safeguard is functioning.

  • Lagging indicators describe recorded outcomes, while leading indicators can reveal whether preventive activities and controls are working. Both are needed, according to OSHA.

  • The crucial question is whether the dashboard measures the conditions that actually keep the operation reliable, rather than merely the completion of administrative activity.

A management dashboard can be entirely accurate and still give leaders an incomplete picture. It may show no serious incidents, completed training, and an acceptable audit score while the operation beneath it is becoming harder to control. That does not necessarily mean the numbers are wrong. It means the numbers describe only what was chosen for measurement, at a particular point in time. OSHA's guidance on leading and lagging indicators makes precisely this distinction: past outcomes and preventive performance answer different questions.

Why can a dashboard stay green while risk increases?

A dashboard can remain green because its indicators are too distant from the actual mechanisms of failure, because reporting is incomplete, or because conditions have changed faster than the measures. Consider an illustrative operation that records 100% completion of scheduled inspections. The completion figure may be correct. But it says nothing, by itself, about whether inspections were capable of detecting the most important faults, whether identified defects were resolved, or whether new pressures changed the equipment's operating conditions. Completion is evidence of an activity, not automatically evidence of protection.

The UK Health and Safety Executive's HSG254 guidance on process safety indicators makes an unusually useful distinction. If leading measures look healthy while lagging outcomes are poor, the control system may not be delivering its intended result. If lagging outcomes look healthy while leading measures are weak, the leading measures may be too remote from the critical control. Either mismatch calls for investigation rather than a reassuring average. HSG254 was developed for major-hazard industries; its logic is useful for thinking about measurement elsewhere, but the specific indicators should not be transplanted unchanged into ordinary office work.

What is the difference between leading and lagging indicators?

Lagging indicators record events that have already occurred: injuries, failures, incidents, and other observed outcomes. Leading indicators track preventive activities or conditions that may reveal problems before a serious event occurs. OSHA recommends using both because neither is sufficient alone (OSHA, Program Evaluation and Improvement).

In practice, the difference is not always as clean as the labels suggest. A near-miss report concerns an event that already happened, but patterns in those reports can also prompt preventive action. A training-completion percentage looks forward because training is intended to reduce future risk, yet it may be a weak indicator if the relevant problem is equipment design rather than knowledge. The label matters less than the relationship between the measure and the failure it is supposed to help prevent.

OSHA's process-safety metrics factsheet describes leading measures as indicators of key work processes, operating discipline, and protective layers. This is a more demanding standard than simply counting how many tasks have been checked off. It asks whether the organization is measuring the operation of its defenses.

What can a low incident rate tell leaders?

A low incident rate tells leaders that relatively few incidents meeting the reporting definition were recorded during the period. It does not prove that underlying exposure or vulnerability is low. A rare event can remain rare even while the conditions that make it possible are deteriorating. Equally, an increase in reports can reflect either more hazards or improved willingness to report them; the count alone cannot distinguish those explanations.

This is not an argument to distrust data. It is an argument to ask what the data represents. OSHA explicitly cautions against relying on a single injury or illness rate to judge a safety program and advocates multiple leading and lagging measures (OSHA interpretation letter, 2016). A sensible interpretation considers reporting practices, exposure, severity, control condition, and the time between changes in the operation and their appearance in a report.

Why is this an organizational reliability problem rather than a reporting problem?

It is tempting to respond to a misleading dashboard by adding more metrics. Sometimes that helps. But an organization can collect more data without improving its ability to notice change. A manager may see one set of numbers, frontline staff may notice another reality, and the connection between them may be weak. The problem is not simply missing data; it is whether different parts of the organization can form a usable picture together.

AeroLeadership's interpretation is that a dashboard should be treated as one part of an organizational sensing system. It condenses information for decisions, which is valuable, but condensation necessarily discards detail. The more consequential the decision, the more important it becomes to understand which information has been compressed out. This is related to the problem explored in why employees stop sharing bad news with managers: information that exists at the operational level is not always information that reaches decision-makers.

There is also a time problem. Measures designed for stable conditions can become less informative when work changes: a new supplier, a different workload, an altered process, or reduced recovery capacity. A historical threshold may still be met even though the conditions that made it meaningful no longer hold. The result is a form of apparent certainty: the report is consistent, while the situation it describes has moved.

What should leaders take from a green dashboard?

They should take it as evidence that the reported measures met the defined criteria, not as an unconditional declaration of safety or reliability. A useful discussion is whether the measures still correspond to the controls and conditions that matter, whether important signals are being lost before they reach the dashboard, and whether the organization can recognize when its assumptions have become outdated. These are questions of judgment and organizational design, not simply data visualization.

The point is not to make every dashboard red or to demand perfect prediction. No measurement system captures everything, and there are costs to monitoring. The aim is to avoid confusing a convenient summary with the system itself. The AeroLeadership Framework examines how awareness, communication, leadership, and risk interact; a green dashboard is a useful illustration of why those capabilities cannot be assessed in isolation.

Sources and further reading