3 Questions Cam Stevens Raises Before Safety Technology Changes the Psychosocial Risk Profile

Episode 15 of the Headline Podcast features Cam Stevens, Safety Technologist and CEO of PKG. His conversation with Andreza Araújo and Dr. Megan Tranter asks a question that many technology programs avoid. What changes in the work after the device, platform, model, or automated alert arrives?

That question matters because a tool can reduce one exposure while adding another. A dashboard may improve visibility, yet alert overload can drain attention. A wearable may support a control, yet constant monitoring can reduce autonomy. A voice channel may make reporting easier, yet collecting more messages without a response can teach people that speaking up is pointless.

Safety technology should follow a defined problem, as this companion explains how digital systems can create psychosocial risk, a weak decision, and a testable improvement. Stevens puts the sequence plainly. “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.” The point is not anti-technology. It is a demand for diagnosis before procurement.

Many teams begin with a product demonstration. They see a sensor that identifies movement, a model that ranks risk, or a platform that turns observations into a score. The organization then searches for a business case that fits the product. That order makes it difficult to know whether the tool changed the risk or simply changed the amount of information on a screen.

A stronger starting point names the exposure in work terms. A maintenance crew may lose the handover detail needed to verify isolation. A supervisor may receive warnings too late to change the task. A worker may have no practical way to report a concern while wearing gloves or moving between locations. Each problem implies a different decision, owner, response time, and evidence standard.

The psychosocial dimension enters before the first installation. If the intervention increases surveillance pressure, uncertainty about evaluation, interruption frequency, or perceived loss of control, the technology has changed the work design. ISO 45003:2021 gives organizations a useful lens because psychosocial risk is managed through the conditions of work, not through a wellness slogan placed beside a new application.

Question 1: Which decision should the signal improve?

A technology signal has value only when a named person can use it to make a better decision within a defined time. Before approval, leaders should identify the decision, the owner, the available response, and the point at which the signal is no longer useful. Without that chain, an alert is information without control.

Consider a model that flags fatigue risk. The output might be technically interesting, but the operational question is different. Who decides whether the person changes task, takes a pause, receives support, or continues? What information is available to distinguish fatigue from illness, medication, grief, or a temporary loss of concentration? Which response protects dignity as well as safety?

The same test applies to computer vision, connected permits, location tracking, and voice reporting. A system that identifies a condition but leaves the supervisor without authority, time, or resources can increase frustration on both sides. The worker sees another mechanism that produces no action. The supervisor sees another queue that competes with production and existing controls.

Write the decision chain in one sentence before comparing vendors. For example, “When this signal appears, the shift supervisor reviews the condition with the worker within ten minutes and either restores the control or pauses the task.” If the sentence cannot be written honestly, the organization needs to redesign the response before it buys the detection layer.

Question 2: What new psychosocial exposure could the tool create?

Every safety technology should be assessed for the risk it introduces into attention, autonomy, privacy, workload, trust, and relationships. A tool is not neutral simply because it targets a physical hazard. Its effect depends on how people are monitored, scored, interrupted, and treated when the signal is wrong.

Stevens says that technology can elevate the human experience, while also recognizing that there are times when it should not be used. That distinction is important for leaders who want to show innovation. The decision to avoid a tool can be as disciplined as the decision to deploy one, especially when the intervention would turn ordinary work into continuous observation.

A field trial should therefore ask workers what the system makes harder. Does it create more notifications than the team can process? Does it encourage people to keep working while mentally managing the device? Does it make a supervisor less likely to have a direct conversation? Does a low score become a hidden label that follows a person into the next shift?

Privacy also requires an operating boundary. The organization should state what is collected, why it is collected, who can see it, how long it is retained, and what it will never be used to decide. These limits need to be understandable to the people whose work generates the data, because trust weakens when the purpose expands after implementation.

Question 3: Will the tool improve voice, or only collect it?

Voice technology improves safety only when a concern moves through acknowledgment, assessment, ownership, action, and feedback. Making it easier to speak is useful, but the reporting loop must also make it credible to expect a response. Otherwise the organization measures participation while confidence declines.

A worker may use a voice interface because typing is impractical, language is a barrier, or the concern appears during a moving task. That access can remove friction. It does not remove the leadership responsibility that follows the message.

The first test is acknowledgment. Can the person tell that the concern was received by a real owner? The second is assessment. Does someone distinguish an immediate exposure from a request for improvement? The third is action. Does the response change a control, schedule, resource, or decision? The fourth is feedback. Can the person who raised the concern see what happened without having to chase the organization?

This loop also protects against a common mistake. Leaders may celebrate a rise in reports as proof that culture improved, although the number could reflect a new channel, a temporary campaign, or unresolved frustration. The better evidence is whether reports receive timely decisions, whether repeated concerns reduce, and whether people continue participating after disagreement.

The same technology can support control or create control theatre

Technology supports control when it changes the condition of work, clarifies ownership, and gives people enough time to respond. It becomes control theatre when it produces dashboards, scores, or notifications that look active but leave the underlying decision unchanged.

The table forces the organization to connect the feature to the work. It also exposes a weak business case quickly. If the technology promise cannot be translated into a changed decision, the organization may be buying activity rather than prevention.

What leaders should test before scaling a safety technology

A field trial should compare the work before and after deployment, not only the number of logins or alerts. Leaders need evidence about decision time, control quality, worker experience, response ownership, and unintended exposure. Scaling should follow a demonstrated improvement rather than enthusiasm for the product.

Start with one operational problem whose boundaries are visible. Record how the decision is currently made, how long it takes, where information is lost, and what workers do when the control is weak. Then define the smallest technology intervention that could improve that decision.

During the trial, review both the signal and the response. A useful signal that arrives after the task has changed is not useful in practice. A fast signal that nobody owns is also not useful. Ask the people who receive the notification whether it changes their next action, and ask the people who perform the work whether the tool changes their attention, discretion, or confidence.

Use a stop rule for the trial. If false alerts create unsafe distraction, if the intervention discourages reporting, or if the data is being used outside the agreed boundary, pause the deployment. That pause is not a failure of innovation. It is evidence that the organization is treating the work as more important than the tool.

Technology decisions belong to safety leadership

The executive question is not whether a technology looks advanced. It is whether the intervention improves a safety decision without weakening trust, autonomy, attention, or the right to challenge the system. Leaders own that tradeoff because the purchase changes how work is organized.

Stevens also connects technology to the changing risk profile of organizations, arguing that psychosocial risk will grow as technology usage expands. That observation gives safety leaders a broader responsibility. They must understand the physical exposure the tool addresses, while also examining how the tool changes relationships, workload, privacy, and judgment.

Andreza Araújo’s work on culture and leadership points in the same direction. A value becomes credible when people can see it in decisions, not when it appears on a poster. If an organization says that people matter, the technology governance process should show it through worker participation, clear boundaries, response rights, and the ability to stop an intervention that creates more harm than control.

The practical standard is demanding but clear. Define the problem. Name the decision. Set the boundary. Test the human effect. Verify the response. Then decide whether the technology deserves to scale.

Listen to the full Headline Podcast conversation with Cam Stevens

Cam Stevens treats safety technology as a decision about work, not a race to acquire more devices. The strongest deployment is the one that improves a defined decision, protects the people who use it, and makes the control more reliable without creating a new psychosocial burden.

Listen to the full conversation with Cam Stevens on the Headline Podcast, then ask your team the three questions from this article before the next technology proposal reaches the budget meeting.

Explore more Headline Podcast conversations about leadership, safety culture, and work design.