How Cam Stevens Thinks About Psychosocial Risk in Safety Technology

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. The seed snapshot recorded 84 views, but the bigger signal is his thesis: safety technology only helps after leaders define the problem first, because the same tool can reduce exposure or intensify psychosocial pressure depending on how it is governed.

Psychosocial risk enters a safety-tech rollout when a tool changes how people are watched, how often they are interrupted, how quickly they are judged, and how safe it feels to raise a concern. That is why the conversation is not about software features alone. It is about work design, trust, workload, and the decision clock behind the screen.

If you want the shorter companion to this episode, read Cam Stevens on tech raising psychosocial risk.

Why psychosocial risk enters a safety-tech rollout

Cam Stevens is useful here because he does not begin with procurement. He begins with the problem, which is the only way to separate a useful tool from a polished distraction. Across 25+ years in executive EHS roles, 250+ cultural transformation projects, and work across 30+ countries, Andreza Araujo has seen the same pattern repeat. Technology looks neutral in the demo and costly in the field if the rollout adds monitoring pressure without changing the decision that matters.

That is why this topic belongs in the psychosocial risk from technology audit cluster. A site can buy speed, visibility, and data volume while quietly increasing interruption, attention switching, and fear of making the wrong call. If leaders do not name those effects, the rollout becomes a work-design change with no work-design review.

If you want the shorter companion to this episode, read Cam Stevens on tech raising psychosocial risk.

What Cam Stevens means by problem-first

Cam Stevens says, "If we're very clear on the problem to solve, then a technology catalog is excellent." That sentence matters because it sets a condition before the purchase. The problem must be clear, the owner must be clear, and the field change must be clear, or the catalog turns into a shopping list that can impress leaders while leaving the real exposure untouched.

The opposite sequence is common. Leaders start with the tool, then ask the field to adapt, and only later discover that the new system created more data entry, more checking, and more delay. Andreza Araujo describes that trap in A Ilusão da Conformidade, where a system can look complete on paper while the working reality stays unchanged. The lesson here is simple. A tool does not decide what matters. Leadership does.

This is also why the article on technology catalogs that turn safety tools into risk remains relevant. A catalog is useful only after the risk decision is named in plain language. If the decision is hidden, the technology may still report activity while the organization keeps the same blind spots.

If you want the shorter companion to this episode, read Cam Stevens on tech raising psychosocial risk.

Where the field feels the cost

Cam Stevens also says, "The changing shift in risk profile will be overwhelmingly psychosocial." That is the part many leaders miss, because they read rollout friction as resistance instead of exposure. A new app, alert stream, camera layer, or voice workflow can increase cognitive load, create a feeling of surveillance, and make workers slower to raise concerns when the system feels like it is watching them more than helping them.

In practice, the field experiences that cost as extra steps, repeated logins, interruptions during safety-critical work, and a new social fear that a message might be seen by the wrong person. That is why the right companion read is the voice technology pilot that changed safety signal governance. The real question is not whether the interface works. The real question is whether the interface changes the work in a way the team can actually live with.

If you want the shorter companion to this episode, read Cam Stevens on tech raising psychosocial risk.

How leaders should read the first month

The first 30 days should test whether the tool changes decisions, not whether people clicked through the screens. A clean pilot must show who receives the signal, how fast they respond, what changes in the field, and whether the team feels more or less pressure after the rollout. If the only improvement is more activity in the dashboard, the organization has added visibility without control.

That is why early pilots need a clear response clock. If a concern appears and no one can say who owns it by the end of the shift, the technology becomes a reporting layer that creates expectation but not action. The article on Cam Stevens and voice technology in EHS makes the same point from a different angle. A signal has value only when it reaches a person who can still change the work.

If you want the shorter companion to this episode, read Cam Stevens on tech raising psychosocial risk.

Comparison

The table below shows the difference between a tool-first rollout and a problem-first rollout. The practical test is not whether the platform looks modern. The test is whether it lowers psychosocial pressure while improving control quality.

If you want the shorter companion to this episode, read Cam Stevens on tech raising psychosocial risk.

What supervisors and HR need to lock down

Supervisors and HR do not need more slogans. They need guardrails around workload, privacy, and escalation. A new tool should answer four questions in plain language. Who sees the signal? Who acts first? How much time does the field have before the next step? What happens if the tool makes the job slower instead of safer? If those answers are vague, the pilot is not ready.

Andreza Araujo's experience matters because the same discipline that reduced accident ratios by 50% in 6 months at PepsiCo South America was not a dashboard trick. It was decision discipline. In more than 250 projects, the pattern has been consistent. When leaders change the condition, the result changes. When they only add reporting, the team absorbs the friction and the risk stays put. That is also the logic behind Sorte ou Capacidade, where well-managed risk is never left to luck.

If you want the shorter companion to this episode, read Cam Stevens on tech raising psychosocial risk.

Why Andreza Araujo's experience changes the test

Across 25+ years in multinational EHS, 250+ transformation projects, and 30+ countries, Andreza Araujo has seen that people do not reject useful change. They reject change that makes the job harder without making the work safer. That is why psychosocial risk belongs in the same review as productivity, quality, and safety. A tool that makes leaders feel informed but makes supervisors feel watched is not neutral. It is a management decision with a human cost.

This is where James Reason still helps. The visible problem at the end of the chain is rarely the first one that mattered. If a rollout raises stress, slows escalation, or teaches workers to filter what they send, the weak point is not the operator. The weak point is the design choice that put the burden on the wrong layer. That is the practical difference between a system that records activity and a system that can still learn.

If you want the shorter companion to this episode, read Cam Stevens on tech raising psychosocial risk.

Recommendation

Use this episode as a 30-day pilot review for one live safety technology. Write down the problem in one sentence, name the decision owner, set the response clock, and define the field proof that will count as success. Then ask the people doing the work whether the tool reduced friction or added it. If the answer is not clear, pause the rollout before it becomes normal.

The best next step is to compare the pilot with the three linked articles above, because they separate technology that changes control from technology that only changes reporting. When leaders can make that distinction, psychosocial risk stops being an afterthought and becomes part of the operating model.

Listen to the full conversation: Listen to the full conversation.