Hearts and Minds in Practice: 5 Traps That Turn Culture Maturity Into a Label

A plant can describe itself as proactive while operators still wait for permission to report a weak control. That contradiction is why Hearts and Minds is useful only when it leads leaders back to observable decisions, not when it becomes a flattering label.

The maturity lens helps a leadership team ask whether safety is driven by fear, reaction, calculation, initiative, or shared ownership. It does not certify that a culture has reached a higher stage. Across 25+ years in multinational EHS leadership, Andreza Araújo has seen the same pattern repeatedly: language changes faster than the work, so the diagnosis must test what people do when production, maintenance, and safety priorities collide.

Why maturity language can mislead a plant leader

Culture maturity is not a personality test for an organization. It is a working hypothesis about how decisions are made, how concerns travel, and whether leaders act on evidence that is inconvenient.

Hearts and Minds is strongest when it helps a plant compare stated expectations with field behavior. The test is practical. Can a supervisor pause a restart when a safeguard is incomplete? Can an operator challenge a plan without being treated as difficult? Can a manager fund a control whose benefit will not appear in this quarter's injury statistics?

Andreza Araújo makes a similar distinction in Safety Culture: From Theory to Practice. A mature culture is not created by choosing a better word for the current state. It becomes visible through repeated choices that protect people when the easier option is to proceed.

Trap 1: Treating the model as a scorecard

The first trap is turning a maturity model into a score that a site can improve from three to four. The number feels objective, which makes it attractive to executives, consultants, and audit teams.

The problem is that a single score compresses different realities. A site may have strong worker participation in maintenance and weak escalation during production interruptions. It may have disciplined incident reviews and poor control verification during night shifts. One label hides the unevenness that leaders need to manage.

A questionnaire can identify a perception gap, but it cannot prove that a barrier works. The safety climate evidence should be compared with interviews, decision records, field observations, and unresolved actions.

Use the model as a conversation structure, then report the evidence underneath it. A plant leader should see the maturity hypothesis, the behaviors that support it, the contradictions that weaken it, and the decisions required next.

Trap 2: Confusing participation with influence

Many organizations celebrate participation because meetings are full, surveys receive responses, and suggestion systems collect ideas. Participation matters, but attendance is not influence.

People learn whether their voice matters by watching what happens after they speak. If a crew reports a recurring exposure and receives a poster, a reminder, or a promise to discuss it later, the system has recorded participation without transferring decision power.

In Safety Culture Diagnosis: Learn how to do your own, Andreza Araújo's diagnostic approach places attention on the distance between what people say and what the organization rewards. That distance is often more revealing than the participation rate itself.

Plant leaders should track three follow-through questions. Who received the concern? Who owned the response? What changed in the task, equipment, schedule, or decision rule? A voice system becomes a management control only when the answer can be found without asking the person who raised the concern to chase it.

Trap 3: Assuming training creates maturity

Training can introduce a common language, but it cannot repair a work design that makes the safe choice impractical. When a site uses a Hearts and Minds workshop as proof of cultural progress, it may be measuring exposure to concepts rather than changes in decisions.

This trap seems reasonable because training produces visible activity. Attendance is easy to count, certificates are easy to file, and leaders can report completion quickly. The harder question is whether the new expectation survives a breakdown, a short shutdown window, or a contractor handover.

James Reason's work on organizational accidents explains why the final action is rarely the whole story. Latent conditions in design, supervision, maintenance, information, and scheduling shape the choices available to people at the point of work.

After training, sample the decisions that training was meant to influence. Review a live change, a permit, a restart, and a near-miss response. If the same constraint still pushes people toward workarounds, the culture has not matured because the slide deck was delivered.

Trap 4: Calling compliance a generative culture

Strong compliance can coexist with weak ownership. A site may have complete forms, high audit scores, and timely corrective-action closure while people still learn that production urgency outranks an unresolved control.

This is the central warning in The Illusion of Compliance, Andreza Araújo's critique of systems that look complete on paper while leaving real exposure untested. Compliance is evidence of conformity to a requirement. It is not evidence that the requirement works under pressure.

Leaders should separate document quality from control quality. Ask whether the control was present, whether it was used as designed, whether someone verified it, and whether a worker could challenge it without personal cost. Those questions turn a cultural label into an operational examination.

The four evidence layers of safety culture are helpful here because they force a comparison between stated values, management systems, leader behavior, and shift-level decisions. A certificate belongs in the evidence set, but it cannot stand for the whole set.

Trap 5: Ignoring local contradictions

The final trap is assuming that a site has one culture. Large plants have several operating realities, shaped by shift, contractor population, maintenance backlog, supervisor behavior, and the history of previous reporting.

A day-shift team may describe escalation as normal because its manager responds quickly. A night-shift team may stay silent because earlier concerns were treated as interruptions. A contractor may follow the written rule while permanent employees rely on an unwritten shortcut. An average score can make those differences disappear.

Culture diagnosis should therefore follow risk and decision points, not only organizational charts. Compare how teams handle the same control during normal work, abnormal work, and restart. Look at where the system bends, who is expected to absorb the strain, and which leader has authority to change the condition.

More than 250 cultural-transformation projects supported by Andreza Araújo's team point to a practical conclusion. Leaders do not improve culture by asking people to be more committed in the abstract. They improve it by changing the conditions in which commitment is tested.

What plant leaders should do now

Use Hearts and Minds as a disciplined hypothesis, not as a badge. A useful 30-day review can move from language to evidence without creating another survey campaign.

• Select three high-consequence decisions, such as restart, isolation, and temporary repair.
• Interview people from different shifts and employment groups about what happens when the plan no longer matches the field.
• Compare those accounts with permits, change records, escalation logs, and direct observations.
• Identify one contradiction that leaders can remove through a resource, authority, design, or schedule decision.
• Recheck the same decisions after 30 days and report what changed, not only what was communicated.

For a deeper diagnostic sequence, see Andreza Araújo's Safety Culture Diagnosis resources. The commercial value of a maturity model is not the label it gives a plant. It is the quality of the decisions the label makes possible.

FAQ about Hearts and Minds and safety culture maturity

What is Hearts and Minds in safety culture? Hearts and Minds is a maturity lens that helps organizations discuss how safety is understood and practiced, from reactive behavior to more proactive and shared forms of ownership. It should be tested with field evidence rather than treated as a certification or universal score.

Can a safety culture be called generative because audit results are strong? No. Audit results show that selected requirements were checked. They do not prove that leaders respond well to bad news, that controls remain effective under pressure, or that workers can challenge unsafe decisions without retaliation.

How should a plant leader measure culture maturity? Compare perceptions with observable decisions. Review how teams handle escalation, restart, temporary controls, change, and reported concerns across shifts and contractor groups. The strongest measure is evidence that decisions become safer when conditions become difficult.

Does Hearts and Minds replace a safety culture survey? No. The model can help structure a survey and interpret themes, but a survey is only one source. Interviews, worksite observations, decision records, and control verification are needed to test whether perceptions match practice.

What is the most common mistake when using a maturity model? The most common mistake is reporting the maturity label as the result. Leaders should report the evidence behind the hypothesis, the contradictions that remain, and the specific decisions that must change.

Safety is about coming home. A mature culture is the set of choices that makes that outcome more reliable when the work is pressured, unfamiliar, or changing.