SPC vs Run Charts vs Heat Maps: Which Fits Safety

Safety dashboards fail when every chart is treated as if it answers the same management question. SPC, run charts, and heat maps can all help an EHS leader see risk, although each one distorts reality when it is used outside its proper decision range.

The practical question is not which visual looks more sophisticated. The question is which view should guide a decision when the board, the plant manager, and the EHS team need to know whether exposure is changing, whether a control is drifting, or whether one area needs urgent attention before a serious event makes the pattern obvious.

Evaluation criteria

A useful safety dashboard should protect judgment before it decorates a monthly review. Across more than 250 cultural transformation projects supported by Andreza Araújo, one recurring failure is that leaders read a colorful page as proof of control while the worksite is showing weak signals in observations, near misses, and corrective action quality.

The comparison below uses five criteria that matter for executive and EHS decisions. The first is signal detection, meaning whether the chart separates normal variation from a real change. The second is exposure visibility, because a graph that hides fatal exposure behind low injury counts can make a plant look safer than it is. The third is action clarity, which asks whether a manager can decide what to verify next. The fourth is data discipline, since some views tolerate messy data better than others. The fifth is misuse risk, because the most attractive visual often invites the weakest interpretation.

Andreza Araújo argues in Safety Culture: From Theory to Practice that culture appears in what leaders reinforce, tolerate, and verify. That sentence is especially important for indicators because a dashboard reinforces behavior even when nobody says it out loud. If the chart rewards low numbers without checking reporting quality, it teaches silence. If it rewards field verification and barrier strength, it teaches control.

SPC is best when leaders need to separate noise from signal

Statistical process control is the strongest choice when the organization has a repeated metric, a stable definition, and enough data points to see whether the process has changed. It works well for DART rate, recordable injury rate, serious near-miss volume, overdue corrective actions, control-verification pass rate, and audit finding closure, provided the measurement rule did not shift halfway through the year.

SPC scores high on signal detection because it uses a center line and control limits to distinguish expected variation from special-cause movement. That matters when a single bad month is about to trigger a campaign, a reprimand, or a bonus freeze. A leader who understands SPC is less likely to punish noise and more likely to ask what changed in exposure, supervision, reporting, or control verification.

The weakness is that SPC can create false maturity when the data stream is politically filtered. If workers have stopped reporting because they fear retaliation, the chart will still look orderly. If contractors use a separate reporting route, the chart may describe the boundary of the database rather than the boundary of risk. This is why SPC should sit beside near-miss quality checks, not replace them.

Use SPC when the decision is whether a process changed. Do not use it as a moral verdict on a supervisor, a proof that culture improved, or a shield against investigating a high-potential event. James Reason's work on latent conditions is useful here because a serious precursor can deserve action even when the point sits inside a statistical limit.

Run charts are best when the team needs speed and shared reading

A run chart is simpler. It plots data over time, often with a median line, and helps a team see direction, clustering, and obvious shifts. It is usually easier to explain in a production meeting than SPC, which makes it valuable for supervisors, shift leaders, and EHS managers who need a shared reading before they have enough data discipline for control limits.

Run charts score well on action clarity because they invite the right first question. Are we drifting up or down? Did the change begin after a new contractor, a shutdown, a staffing change, a reporting campaign, or a new verification routine? The chart does not prove causality, although it gives the team a time anchor for field checks.

The cost is weaker signal detection. A run chart can make random movement look like a trend, especially when leaders are anxious after a serious incident or proud after a long period without recordables. That weakness is not a reason to reject the tool. It is a reason to keep the interpretation modest and pair it with a stronger method when money, accountability, or public reporting depends on the conclusion.

Run charts are a strong bridge for organizations that currently review only monthly totals. They work well for leading indicators such as observation quality, field verification completion, overdue actions, and supervisor safety conversations. When the same organization later gains enough consistent data, the most important measures can graduate to SPC, as explained in the current SPC in safety metrics guide.

Heat maps are best when leaders must compare exposure across areas

Heat maps are useful when the decision is not whether a process changed over time, but where leadership attention should go first. A plant with ten departments, twenty contractors, or several operational sites may need a quick view of exposure concentration. The heat map can show which area carries more high-risk tasks, open actions, repeated deviations, or weak control-verification results.

Heat maps score high on exposure visibility when the underlying dimensions are well chosen. A map based only on injury frequency is weak because it favors areas where reporting is mature and punishes areas where people speak up. A better map combines exposure severity, control criticality, action aging, repeated findings, and field-verification results. That mix helps leaders see where a quiet area may still carry fatal risk.

The tool is risky because color looks authoritative. Red, amber, and green can make a subjective score appear mathematical, especially when the scoring rule sits in a spreadsheet nobody challenges. In Andreza Araújo's work with executive teams, this is one of the most common dashboard traps. The color persuades before the evidence is tested, and the meeting moves from inquiry to defense.

Use heat maps when the decision is prioritization across locations, work groups, or hazard families. Do not use them to prove trend, improvement, or cultural maturity. A heat map can direct a leader to the field, but it cannot replace the field. It also needs periodic calibration, otherwise last quarter's red area remains red because of reputation while a new exposure grows quietly somewhere else.

Decision matrix

This matrix also shows why no single chart should dominate a mature dashboard. SPC protects leaders from reacting to noise. Run charts help teams see movement while the evidence is still developing. Heat maps help executives allocate attention across competing exposures. The danger appears when one tool is asked to perform all three jobs.

Recommendation per context

For a board or executive committee, start with a heat map for exposure concentration, then use SPC for the few metrics that should govern escalation. The board does not need thirty charts. It needs to know which fatal exposures are changing, which critical controls are weakening, and which numbers may be too clean to trust. That is also where lagging indicator limits must be made explicit, because a low injury rate cannot prove control over serious exposure.

For a plant management team, use run charts for weekly rhythm and SPC for monthly decision discipline. The plant manager needs enough speed to ask about last week's drift, but enough rigor to avoid changing priorities every time a metric moves. This combination works well for open corrective actions, verification pass rate, near-miss quality, and repeat audit findings.

For an EHS manager, use all three but assign a different owner to each interpretation. The analyst maintains SPC rules. The field team reviews run charts against what supervisors actually see. The site leadership team challenges heat-map scoring before resources are moved. When one person owns the whole interpretation alone, the dashboard becomes vulnerable to confirmation bias, especially after a serious event or a period of public success.

For supervisors, keep the first view simple. A run chart tied to the team's own work is usually better than a corporate heat map that feels remote. The supervisor should be able to ask which task, shift, contractor, or control changed. If the chart cannot lead to a worksite question within two minutes, it is not serving the supervisor.

Common traps when choosing the chart

The first trap is selecting a chart by audience status instead of decision need. Executives often receive heat maps because they look strategic, while supervisors receive lists because they look practical. That split is lazy. A board may need SPC when it is about to judge performance, and a supervisor may need a local heat map when several task types compete for attention.

The second trap is treating more advanced visuals as more mature leadership. A control chart built from weak definitions is not mature. A heat map with hidden scoring weights is not strategic. A run chart that sends a supervisor to verify a weak isolation practice may be more valuable than a complex dashboard that nobody challenges.

The third trap is forgetting reporting behavior. When reporting changes, the chart changes even if risk does not. A rise in near misses after a speak-up campaign may indicate better visibility rather than higher exposure. A fall in observations after a punitive review may indicate fear rather than improvement. This is why dashboard redesign should connect to observation quality, not only to volume.

The fourth trap is allowing the chart to end the conversation. The right chart should start verification. If SPC shows a signal, the team should inspect the process. If a run chart shows drift, the supervisor should ask what changed in the work. If a heat map turns one area red, leaders should test whether the score reflects exposure or only reporting discipline.

How to build the dashboard sequence

Start with the decision calendar. Weekly reviews need speed, so run charts often belong there. Monthly reviews need discipline, so SPC belongs there once the data stream is stable. Quarterly executive reviews need prioritization, so heat maps can help if their scoring rules are open enough to challenge.

Then connect each view to a required action. A run chart should trigger a field question. An SPC signal should trigger a verification plan. A heat-map red zone should trigger resource review, leadership presence, or deeper control testing. Without that action rule, the chart becomes a reporting object rather than a management instrument.

Finally, audit the dashboard for false confidence. Ask which chart would reveal underreporting, which chart would reveal a weak critical control, and which chart would reveal a repeated precursor before an injury appears. If the answer is unclear, the dashboard is probably built around available data rather than decision risk. The practical next step is a focused safety KPI audit for false confidence.

Final recommendation

Choose SPC when the decision depends on whether a process has changed. Choose run charts when a team needs a fast, shared reading of movement. Choose heat maps when leaders must compare exposure across areas and decide where attention should go first. The mature dashboard does not force one winner because the three tools answer different questions.

The strongest sequence is usually heat map for exposure focus, run chart for operating rhythm, and SPC for disciplined escalation. That sequence keeps the board from reading color as proof, keeps managers from chasing every monthly movement, and keeps supervisors connected to the work conditions where risk is either controlled or normalized.

Review Andreza Araújo's safety culture work at andrezaaraujo.com if your organization needs indicators that change leadership behavior instead of only improving the slide deck.