How Cam Stevens thinks about problem-first technology in EHS

Episode 15 of Headline Podcast, published on March 18, 2026, features Cam Stevens, safety technologist and CEO of PKG, in conversation with Andreza Araujo and Dr. Megan Tranter.

His thesis is direct: technology only helps after leaders define the problem they want solved, because a tool without a decision owner can make EHS look busier without making it safer.

Why the problem statement comes before the tool

Cam Stevens says that a technology catalog is excellent when the problem is clear, and very dangerous when the problem is vague. That distinction matters because many EHS pilots start with a demo, not with the exposure pathway the organization needs to change.

This is where Executive Safety Dashboard: 7 Metrics C-Level Leaders Need is a useful companion article. A dashboard, like any digital tool, only earns its place when it changes a decision, and a decision can only be changed when the problem has been named in plain language.

Across 25+ years of executive EHS work, Andreza Araujo has seen the same failure repeat itself in new software clothing. Leaders buy a tool before they define the risk, then ask the tool to discover what the leadership team never wrote down.

As Andreza Araujo argues in Safety Culture: From Theory to Practice, culture is what the organization repeatedly permits, rewards, corrects, and measures when work gets uncomfortable. If the pilot does not change those four things, it is not a management system. It is a screen.

What a signal owner must decide

A signal only matters when someone owns the response. The owner must know what type of signal it is, what must change before the next shift, who can verify the change, and how fast the field should expect a reply.

In more than 250 cultural transformation projects, Andreza Araujo has seen that weak ownership is where good tools stall. The software may capture a report in seconds, yet the signal still ages if EHS, operations, IT, and HR treat it as someone else’s problem.

That is why Corrective Action Aging: 7 Metrics Leaders Need belongs in the same reading path. A signal without a clock becomes a queue, and a queue without ownership becomes a polite form of delay.

As Andreza Araujo also shows in Antifragile Leadership, the real test is whether a system learns before the next exposure repeats the same pattern. Signal ownership is the first place where that learning either happens or dies.

Why adoption can lie

Adoption data can flatter a pilot. A site can reach high usage, high completion, and full app installation while the same control gaps remain untouched in the field.

That is why Near-Miss Quality: 7 Signals Your Metrics Are Lying is relevant here. A healthy number on a dashboard does not prove that the organization reduced exposure, changed supervision, or closed the loop with the crew.

Cam Stevens’ episode is strongest when it separates activity from control quality. If the tool makes reporting easier but the response still takes two weeks, the organization improved intake while leaving the work system slow.

Across projects supported by Andreza Araujo, that pattern appears often enough to deserve respect as a leadership trap. The metric goes up, the meeting gets more colorful, and the field keeps working around the same weak barrier.

Why psychosocial risk belongs in the pilot

Cam Stevens does not treat technology as a neutral layer. He says that the changing shift in risk profile will be overwhelmingly psychosocial, driven by technology usage in organizations.

That matters because new systems change workload, monitoring pressure, autonomy, and the social cost of speaking up. A tool that looks efficient on paper can still add friction to the team that has to live with it every shift.

In Safety KPI Weighting: 6 Dashboard Traps, the same lesson appears from another angle. More data is not the same as better control when the extra data adds noise, tension, or a false sense of precision.

Andreza Araujo has seen this in multinational work for more than 25 years, and the point has not changed. If the pilot rewards more submissions but ignores the pressure the tool creates, the organization may be collecting data at the cost of trust.

Where human judgment still matters

Cam Stevens draws a clear boundary around technology when he says, “We can elevate the human experience with technology, but there are certainly times when technology should absolutely not be used.” That is the right boundary for EHS because some decisions need local context, timing, and the authority to stop work before the dashboard agrees.

If the same concern appears in the field, in the supervisor review, and in the app, but no one changes the task, the system is informing people without enabling action. At that point, the tool functions as an archive, not as a control.

This is also where Safety Decision Rights: 7 Tests Leaders Need fits well. A pilot is only as good as the decision path behind it, and the decision path is a leadership design choice, not a software feature.

As Andreza Araujo writes in Safety Culture: From Theory to Practice, the organization shows its real priorities when pressure rises. If the response path is unclear, the technology will record that confusion, not fix it.

Comparison: technology-first rollout vs problem-first governance

The difference between the two models shows up in evidence, ownership, and time. The comparison below is a practical way to test whether a pilot is changing work or only changing the interface.

This comparison is one reason the episode stays useful after the listening window closes. It gives leaders a decision lens, not a product review.

Recommendation for a 30-day pilot review

Use Episode 15 as a 30-day governance review for one live digital pilot. Start with a two-week problem-definition sprint, then ask the sponsor to write down the problem, the owner, the evidence, the response clock, and the verification method.

If they cannot write those five items clearly, the organization is not ready to buy or scale the tool. That is a better decision than a rushed rollout that only proves the team can purchase software fast.

The same discipline belongs next to corrective action aging and near-miss quality, because a pilot should be judged on field change, not on decorative usage data.

Andreza Araujo has seen in more than 250 cultural transformation projects that leaders often miss the weak link between signal and decision. Once that link is visible, the next move is usually simple: redesign the workflow, shorten the response clock, or stop using the tool where it cannot protect the work.

Conclusion

Cam Stevens’ episode is not a celebration of technology. It is a warning that technology only helps when the organization already knows the problem, the owner, and the proof that work changed.

Headline Podcast listeners who use that lens will make better pilot decisions, ask sharper questions, and stop confusing more data with better control.

Listen to the full conversation: Headline Podcast Episode 15 with Cam Stevens.