8 insights from Episode 15 with Cam Stevens

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 straightforward. When leaders start with the technology catalog instead of the problem, they can make EHS look modern without changing the exposure, the decision, or the response that actually shapes risk.

What problem was Cam Stevens trying to solve?

Cam Stevens makes the starting point clear when he says, "If we're very clear on the problem to solve, then a technology catalog is excellent. If we're not clear on the problem to solve, a technology catalog is very dangerous." That is not a software complaint. It is a governance rule, because a tool can only improve work when the organization has already named the hazard, the decision owner, and the response clock.

OSHA's safety management guidance frames effective safety programs around leadership, worker participation, hazard identification, hazard prevention, and program evaluation. That frame matters here because the wrong pilot often begins with a vendor demo, not with the field condition that leaders need to change.

Across 25+ years of executive EHS work and more than 250 cultural transformation projects, Andreza Araujo has seen the same pattern repeat itself. Teams buy the tool first, then ask it to reveal a problem they never defined clearly enough for a manager to act on.

This is why the companion article Psychosocial Risk from Technology: 30-Day Audit belongs in the same reading path. Both pieces start from the same operational question, which is whether technology changes the work or only changes the appearance of control.

What changes inside the job when technology enters the system?

Technology changes more than data collection. It changes workload, monitoring pressure, autonomy, trust, and the social cost of speaking up, especially when people spend 8 hours a day inside the same digital workflow and cannot ignore the alerts, logs, and dashboards that follow them across the shift.

On Headline Podcast, Cam Stevens said, "The changing shift in risk profile will be overwhelmingly psychosocial, driven by technology usage in our organizations." That line matters because a new system can create a safer-looking report while increasing friction for the person who has to use it under time pressure.

NIOSH describes Total Worker Health as an approach that integrates protection from work-related safety and health hazards with promotion of injury and illness prevention efforts to advance worker well-being. The point is not that every tool harms people. The point is that every tool changes the conditions under which people decide, report, and recover.

Andreza Araujo's book The Illusion of Compliance is useful here because it separates clean reporting from real control. A dashboard can be accurate and still leave the team under pressure if the response path is slow, unclear, or owned by the wrong function.

Comparison: technology-first rollout vs problem-first governance

The table below is a practical test. If a pilot looks like the first column, it is probably adding activity. If it looks like the second column, it is changing the system that produces the risk.

The logic behind that table is simple enough to test in one team, one shift, or one site. A tool that increases visibility without changing the decision path is not yet a control. It is a more polished queue.

That is also why Workload Trigger Matrix Explained for Psychosocial Risk is a useful companion. If the tool changes alerts but not workload thresholds, the organization may have modernized the interface while leaving the pressure intact.

Why human judgment still needs authority

Cam Stevens draws a clear boundary 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 safety work because some decisions depend on local context, timing, and the authority to stop work before the dashboard agrees.

ISO 45003:2021 frames psychosocial risk inside the occupational health and safety management system, which means leadership has to examine how the work is organized, supervised, and measured. If a technology pilot removes discretion but gives people more data, the pilot may increase certainty while weakening judgment.

There is a simple operational test. If the same concern appears in the field, in the supervisor review, and in the digital system, what changed before the next shift? If nothing changed, the organization is informing people without enabling action, and the person closest to the risk is carrying the burden alone.

Andreza Araujo has seen this in more than 250 projects across 30+ countries. The strongest sites do not treat technology as a replacement for supervision. They treat it as one input inside a decision system that still requires a manager who can listen, verify, and act.

Why psychosocial risk belongs in the pilot

Psychosocial risk belongs in the pilot because the pilot changes how people work before it changes any metric. If the tool adds clicks, surveillance, or delay, the crew feels that pressure long before the executive dashboard shows a problem.

WHO's guidelines on mental health at work emphasize organizational interventions, manager training, worker training, and return-to-work support. That is a useful reminder that the best pilot is not a technology trial alone. It is a test of whether the organization can protect people while it changes the work.

A practical pilot review should ask 4 questions. What changed for the worker, who owns the response, how fast does the signal age, and what proof shows the field condition improved? If a sponsor cannot answer those 4 questions clearly, the pilot is still a promise, not a control.

This is the same reason the article Psychosocial Risk from Technology: 30-Day Audit is a good next step. The first 2 weeks should define the problem, and the next 2 weeks should verify whether the technology changed workload, autonomy, trust, or escalation speed.

Recommendation

Use Episode 15 as a 30-day governance review for one live digital pilot. Start with 3 live initiatives, then require each sponsor to write a one-page brief that names the problem, the affected team, the decision owner, the 24-hour response clock, and the verification method.

After that, check the field. Does the pilot reduce confusion? Does it shorten escalation? Does it change the supervisor's decisions in the same shift? If the answer is no, pause the scale-up and redesign the workflow before the tool becomes a clean record of the same old delay.

The review does not need a larger meeting. It needs 1 owner, 1 response clock, 1 field check, and 1 decision about whether the pilot deserves more air time. Anything broader risks turning governance into ceremony.

Conclusion

Episode 15 is not a celebration of technology. It is a warning that technology only helps when the organization has already named the problem, the owner, and the proof that work changed.

Leaders who use that lens will ask better questions, catch psychosocial side effects sooner, and stop confusing more data with better control.

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