Safety Culture Maturity: 3 Assumptions That Keep Leaders Stuck

Safety culture maturity is the degree to which a company can prove, through field behavior, leadership decisions, and control evidence, that safety is managed before harm appears in the injury record.

Many leaders want a maturity label because labels feel decisive. A site is called dependent, independent, interdependent, reactive, calculative, proactive, or generative, and the meeting moves on as if the word itself changed the operation. The field is less polite. It asks whether supervisors stop weak work, whether managers fund controls before the injury, and whether workers still tell the truth when production pressure rises.

Across 25+ years in executive EHS roles and more than 250 cultural transformation projects, Andreza Araujo has seen a recurring pattern: companies overestimate maturity when they measure what is easy to display and underestimate immaturity when the evidence is uncomfortable. A polished survey result can coexist with poor handovers, cosmetic safety walks, weak contractor control, and managers who still treat silence as alignment.

Why maturity assumptions keep culture cosmetic

Maturity assumptions keep culture cosmetic because they turn a diagnostic question into a status claim. Once leaders believe the organization has already reached a higher stage, they stop asking whether the claim survives field verification. The culture conversation then becomes ceremonial. People repeat the model, show the heat map, compare business units, and avoid the harder question of which decisions still protect output at the expense of control.

Patrick Hudson's maturity work is useful when leaders treat it as a mirror, not a medal. Edgar Schein's work on organizational culture also matters here because visible artifacts do not always reveal the assumptions that govern behavior under pressure. A plant can have banners, committees, audits, and leadership visits, while the real operating rule remains, "do not delay the line unless the risk is impossible to ignore."

Assumption 1: A higher maturity score means the site is safer

The first assumption says the survey score is a reliable proxy for safety. It sounds reasonable because surveys are structured, scalable, and easy to compare across sites. The weakness is that a score captures perception at a moment in time, while serious risk often sits inside tasks that most respondents do not see, such as non-routine maintenance, contractor interfaces, temporary changes, shutdown work, and abnormal operations.

A high score can hide weak control evidence. Workers may rate leadership commitment well because managers speak respectfully, attend meetings, and approve campaigns, although the same managers may still defer engineering fixes, accept late corrective actions, or allow supervisors to close safety walks with observations instead of decisions. Perception matters, but it does not replace proof.

In Safety Culture: From Theory to Practice, Andreza Araujo argues that culture must be read through repeated decisions, not only declared values. That view changes the maturity conversation. Leaders should compare the survey with field evidence from safety culture survey, maturity, and field evidence, then ask where the score and the worksite disagree.

The better question is not whether the score improved. The better question is whether the improvement appears in control quality, escalation speed, permit discipline, contractor supervision, corrective action closure, and the authority of frontline leaders to slow work before exposure becomes visible as an event.

Assumption 2: Interdependent language proves interdependent behavior

The second assumption appears when leaders adopt advanced culture vocabulary before the organization has changed its operating routines. People say they care for each other, challenge unsafe work, and own safety collectively, yet the supervisor may still carry the entire burden when a crew is short, the planner may still release work with missing controls, and the manager may still praise recovery from a bad plan instead of challenging the plan itself.

Language can travel faster than behavior. A company can teach the right phrases in workshops and still reward the old choices in production meetings. When the hidden reward system values speed, silence, and heroic recovery, workers learn that the mature language is expected in public while the practical rule remains different in the field.

James Reason's analysis of organizational accidents helps keep the discussion honest because it points attention to latent conditions, not only the final visible action. If the organization says it is mature but keeps tolerating poor planning, weak maintenance windows, unclear stop-work authority, and repeated overdue actions, the culture is not operating at the level the language claims.

Leaders should test language against decisions. Review the last ten times someone raised a weak signal, stopped a task, challenged a permit, asked for more time, or rejected a shortcut. If the person paid a social or career price, the culture has not reached the maturity stage printed on the slide.

Assumption 3: More safety activities mean more mature culture

The third assumption confuses activity volume with cultural depth. More talks, campaigns, observations, audits, committees, and dashboards can help, but activity becomes noise when it does not change how risk is controlled. Many sites are busy with safety work and still weak at safety decisions.

This trap is especially common after an incident or leadership change. The organization adds meetings, forms, posters, and reporting channels because visible action reduces anxiety. After a few weeks, the calendar looks full, the dashboard looks active, and leaders feel momentum. The field may feel something else: more paperwork, less clarity, and no real change in staffing, sequencing, supervision, or control verification.

Andreza Araujo's A Ilusao da Conformidade, glossed as The Illusion of Compliance, is a useful anchor for this risk. Compliance evidence can become a substitute for operational truth. A completed activity proves that something occurred, but it does not prove that a critical control is stronger, a supervisor has more authority, or a worker can speak up without retaliation.

The maturity test should move from volume to consequence. Did the safety walk generate a funded decision, as discussed in safety walks that keep culture cosmetic? Did the audit expose a cultural assumption, as shown in paper safety culture distortions? Did the committee remove a barrier or merely record one more concern?

Signals that the maturity claim is ahead of the culture

The maturity claim is probably ahead of the culture when leaders use the model mainly for ranking sites, when weak signals require personal courage instead of a clear route, and when the same overdue corrective actions appear month after month with better explanations than progress. Another signal is the gap between corporate language and contractor reality. If direct employees hear mature culture messages while contractors experience rushed induction, poor supervision, and unclear escalation, the maturity claim is partial at best.

There is also a behavioral signal that executives often miss. In immature cultures, people become skilled at presenting safety evidence upward. They know which indicators will be praised, which problems will be reframed, and which delays will be treated as excuses. The dashboard becomes clean because the organization has learned how to package risk, not because risk has been reduced.

A serious maturity review should therefore read artifacts, decisions, and field evidence together. Leaders can use five evidence types in safety culture artifacts to separate visible symbols from operating assumptions, then compare those findings with incident precursors, safety walk quality, contractor control, and worker voice.

What leaders should do now

Leaders should stop asking only, "What maturity stage are we in?" and start asking, "Which decisions still contradict the stage we claim?" That question is harder because it names ownership. It points to funding, staffing, planning, maintenance priorities, production pressure, contractor management, and the leader's response when a supervisor brings an inconvenient truth.

Run a 30-day maturity evidence review with three lenses. First, compare survey results with field verification from safety walks, permits, observations, and contractor interfaces. Second, review ten recent weak signals and document whether they received action, delay, or polite acknowledgment. Third, select five important safety activities and ask what decision changed because each activity happened.

The standard should be practical, not theatrical. A mature culture is not the site with the most sophisticated vocabulary. It is the site where people can name risk early, leaders can change the plan before harm, and control evidence is stronger than the story told about it.