How Cam Stevens Thinks About Problem-First Technology in EHS

Episode 15 of Headline Podcast, published on March 18, 2026, brings Cam Stevens into a conversation with Andreza Araujo and Dr. Megan Tranter about safe-tech adoption and technology-driven psychosocial risk. His central thesis is that a technology catalog only helps when the problem is already clear, because the wrong digital fix can raise noise, workload, and confusion while leaving the real exposure untouched.

Why Episode 15 matters now

Episode 15 matters because it cuts through the habit of shopping for tools before naming the problem, and that habit is where safety technology most often becomes busywork. Cam Stevens is not arguing against technology. He is arguing that technology only earns its place after the problem, the decision path, and the response rule are already clear, which is why the same software can help one operation and frustrate another.

That matters in safety because a tool that adds clicks, alerts, or duplicate entries can raise pressure before it lowers exposure. OSHA describes management leadership as an active part of safety and health programs, and the same logic applies to technology choices. A rollout without ownership usually becomes a dashboard with a budget, while the field keeps carrying the same risk.

Across 25+ years of executive EHS work, Andreza Araujo has seen the same pattern repeat in different plants and countries. A system that cannot explain what problem it solves often ends up solving an easier one, which is making the slide deck look current instead of making the work safer.

What problem-first technology means

Problem-first technology means the organization names the operational problem before it compares vendors, sensors, or software. The question is not what tool can we buy. It is what failure path are we trying to change, who owns the response, and what field decision should get easier after deployment. That sequence sounds ordinary, yet it is the step most rollouts skip.

On Headline Podcast, Cam Stevens said, 'If we're very clear on the problem to solve,' and later added, 'technology catalog is excellent.' The full sentence is the point. Technology helps when it is selected after the problem has been framed, because then the tool can fit the work instead of forcing the work to fit the tool. A platform whose design does not match the job only moves friction from one place to another.

In Safety Culture: From Theory to Practice, Andreza Araujo treats culture as repeated decisions, which is why a new platform that does not change the decision path is only a polished accessory. Headline readers can compare that idea with control automation in safety, because automation without problem clarity often amplifies the same blind spots it was meant to remove.

Across 250+ cultural transformation projects, Andreza Araujo has seen that the best tools are almost invisible when they are right, because they remove a specific barrier and then get out of the way. The worst tools stay visible all day, which is usually the sign that the job and the software never belonged together.

When safety technology becomes psychosocial risk

Technology becomes psychosocial risk when it changes the pace, visibility, and emotional cost of work. A platform can help a team see more, yet it can also create a second job by adding alarms, surveillance, re-entry, or decision fatigue, which means the person now manages the tool while trying to manage the task. The risk is not only technical. It is also human, because the work itself starts to feel less like control and more like monitoring.

On Headline Podcast, Cam Stevens said, 'The changing shift in risk profile will be overwhelmingly psychosocial.' That warning matters because the damage is not always dramatic. Sometimes it shows up as silence, role confusion, or the quiet sense that every click is being counted, which is why people start to comply with the tool instead of using it to improve the work.

NIOSH frames Total Worker Health as an approach that connects hazard protection with worker well-being, and the World Health Organization notes that mental health at work is shaped by work design, social interactions, and managerial support. Those principles matter here because a tool whose output nobody trusts can increase strain instead of reducing it.

Headline readers can compare this with Workload Trigger Matrix Explained for Psychosocial Risk, because workload, alert load, and role ambiguity are often the hidden costs of a tech rollout. A dashboard which adds notifications but never reduces effort is not neutral, it is another source of demand.

How leaders should read the prediction promise

Prediction is useful only when the organization has a clear response rule for the signal it receives. A model that forecasts heat stress, fatigue, or psychosocial strain but does not trigger a supervisor, a work stop, or a design change just adds another number to watch. The promise sounds advanced, but the practical effect is often the same old delay with a better interface.

During Andreza Araujo's PepsiCo South America tenure, the accident ratio fell 50% in 6 months, but the mechanism was not a gadget. Leaders changed how they saw the work, verified critical controls, and answered bad news before it hardened into routine. The lesson is simple. Signal improves when the decision routine improves, because the organization starts acting on what it sees.

Safety Decision Log in 30 Days belongs in the same reading set, because the decision log makes ownership visible before the next alert arrives. Across 30+ countries, Andreza Araujo has seen that a tool becomes credible only when the response is named in advance and the site can show who will act within the shift, not after the meeting.

What changes when technology starts with the problem

The comparison below shows why the same software can help one operation and frustrate another. The difference is not the vendor pitch. The difference is whether the operation has already named the problem, the exposure, and the decision that must change when the signal appears.

OSHA's worker participation guidance matters here because the people who live with the tool should help shape the response rule, not just receive the rollout email. That is why an article like Safety Decision Log in 30 Days belongs in the same reading set: if leaders cannot show who owns the next move, the technology will only produce more questions.

Andreza Araujo often frames this as a governance test, not a gadget test. The stronger the involvement of the people who touch the work, the less likely the rollout becomes a shadow process that looks advanced while adding friction.

Recommendation

The next 30 days should be spent on three questions, not three demos. First, what exact problem is this technology meant to solve. Second, what exposure or decision will move if it works. Third, who will act when the signal appears, and within what time window. If the answer to any of those questions is vague, the rollout is not ready.

A tool whose purpose can only be explained in vendor language will usually create more administration than control. In The Illusion of Compliance, Andreza Araujo warns against neat process that hides weak reality, and that warning applies here as much as it does in audits or incident reviews. The organization should be able to explain the risk in one sentence before it buys a single screen.

Use the next pilot to test whether the tool changes a field decision in the first 7 days, then test whether the same change survives the next 30. If it does not, the program should be redesigned before scale, because scale only makes a weak design more expensive. That is also why How to Build a Safety Decision Log in 30 Days is a useful companion read for the rollout team.

Do not let a digital purchase sit ahead of problem clarity. The organization should be able to explain the risk in one sentence before it buys a single screen.

What to do after listening

Cam Stevens gives safety leaders a clean filter for technology. Start with the problem, not the catalog. Ask whether the tool changes a decision, not whether it looks modern. That filter protects both the work and the people who have to live with the work, which is why a digital program that adds strain but not control should be treated as a risk decision, not an innovation story.

If you want the full argument and the surrounding conversation with Andreza Araujo and Dr. Megan Tranter, listen to the episode and then check it against your next rollout. Episode 15 is useful because it turns a vague tech conversation into a practical leadership test, and that test is whether the work becomes clearer, faster, and safer for the people who actually do it. Listen to the full conversation: Episode 15 with Cam Stevens.