Supervisor Curiosity: 8 Steps to a Safer Shift Routine

A supervisor who asks one more question before approving a task can expose a weak control that a polished checklist leaves untouched. The purpose is not to slow production with endless discussion. It is to make curiosity a repeatable part of the shift routine, especially when the crew is under pressure to accept familiar risk.

This guide gives supervisors an eight-step routine that can be introduced over 14 days. It turns curiosity into observable behavior, connects questions to control decisions, and creates a record of what the team learned without confusing psychological safety with permission to ignore standards.

What you need before starting

Start with one shift, one supervisor, and one recurring task that carries meaningful exposure. Choose work where the team already has a permit, a Job Safety Analysis, a pre-task brief, or another control that can be examined in the field. A narrow starting point is useful because the routine should reveal how decisions are made, not become another campaign.

Prepare a one-page question log with four fields: the question asked, the condition observed, the control decision, and the follow-up owner. The log is not a scorecard for individual workers. It is a management record whose value depends on whether questions change work, which means that a closed loop matters more than the number of questions collected.

As Andreza Araújo argues in Safety Culture: From Theory to Practice, culture becomes visible in the decisions that people make when the written rule meets operational pressure. Supervisor curiosity is useful only when it reaches that decision point.

Step 1: Choose one decision that deserves curiosity

Select a decision that happens often enough to practise and matters enough to expose the limits of routine. Examples include accepting a changed work area, releasing a contractor, restarting equipment, or deciding whether a control remains effective after a delay.

Write the decision in one sentence, then define the consequence of getting it wrong. This gives the supervisor a clear boundary for the routine. The goal is not to ask broad questions about safety; it is to test whether the current evidence supports the next action.

Verify the choice by asking the crew where the decision is usually made and who owns it. If nobody can answer, the first problem is decision ownership, not curiosity. A common error is choosing a topic that sounds important but has no observable decision attached to it.

Step 2: Ask for the expected condition

Before asking what went wrong, ask what should be true before the job continues. The supervisor can say, “What must we see here before we release this task?” This wording directs attention toward the control rather than toward the worker who may be closest to the problem.

Record the expected condition in plain language. It may concern isolation, access, line of fire, communication, competence, equipment status, or rescue readiness. The condition should be visible or verifiable, because an abstract answer cannot support a reliable decision.

Check the answer against the permit, JSA, procedure, or engineering requirement that governs the task. The conversation is stronger when the team can explain how the expected condition connects to a formal control. A common error is accepting “it looks fine” as evidence when the task requires a defined test or inspection.

Step 3: Invite the newest observation first

Ask the person who arrived most recently, changed the setup, or has the least history with the task to describe what they see. Fresh eyes often notice mismatches that experienced people have learned to treat as normal, while the supervisor receives a signal before senior voices shape the answer.

Use a neutral prompt such as, “What is different from the last time this job was done?” Do not rescue the silence too quickly. A pause gives the worker time to organise an observation that may otherwise remain unspoken.

Verify the observation by walking to the condition together. If the observation is valid, add it to the log without attaching blame. If it is not valid, explain what evidence resolves the concern. A common error is thanking the person and moving on without showing whether the concern changed the decision.

This practice reflects the distinction between psychological safety and unrestricted error tolerance. People should be able to raise a concern without humiliation, while the team still evaluates the concern against technical evidence and agreed requirements.

Step 4: Separate familiarity from control effectiveness

Ask, “What are we relying on because it is actually effective, and what are we relying on because it is familiar?” The question helps the crew examine routine conditions that feel safe simply because they have been repeated without a visible consequence.

Review the control in the order in which it prevents exposure. If the task depends on a guard, an isolation, a barrier, a competent person, or a communication step, ask how the team knows that element is working today. James Reason’s work on latent and active failures is useful here because a safe-looking task can still contain hidden weaknesses in the organisational layers around it.

Verify one control through direct evidence, such as a field check, a test, a current authorisation, or a documented handoff. A common error is turning the question into a philosophical debate about culture when the next action is a simple verification.

Step 5: Make dissent technically usable

Curiosity becomes practical when a supervisor makes it safe to disagree with a planned action. Ask, “What would make you pause this job?” Then define how the concern will be assessed, who can stop the work, and how the decision will be communicated to the rest of the crew.

This is not a request for unanimous agreement. A team can proceed while one person remains concerned if the concern is examined, the evidence is recorded, and the responsible decision-maker explains why the control is acceptable. That structure protects technical dissent from becoming either a personal confrontation or a ceremonial question.

Verify the routine by checking whether a concern produces a named response within the shift. A common error is praising courage while leaving the person to chase the answer alone. In more than 250 cultural transformation projects supported by Andreza Araújo’s work, the practical test of voice is whether management converts information into a visible control decision.

Step 6: Close the question with a control decision

Every meaningful question needs one of three outcomes. Continue because the evidence supports the control, pause because a condition must be restored, or escalate because the decision exceeds the supervisor’s authority. State the outcome aloud so that the crew hears how information becomes action.

Write the decision in the log using a verb and an owner. “Replace damaged barrier, maintenance supervisor, before restart” is stronger than “barrier issue discussed.” The wording should make the next action clear to someone who was not present.

Verify closure before the task moves past the decision point. A common error is recording a concern after the work has already continued, which teaches the team that documentation is separate from control.

Step 7: Review the pattern at the end of the shift

Reserve five minutes for the supervisor to review the log with the crew or with the next shift. Look for repeated questions, recurring weak controls, delayed responses, and concerns that were resolved by individual effort rather than by a reliable system.

Do not rank supervisors by the number of questions. A high count may show attention, or it may show that the process is confusing. A low count may show stable control, or it may show silence. The useful measure is the quality of the decision trail, which reveals whether curiosity is finding conditions that deserve management attention.

Verify the review by selecting one pattern for the next shift to test. A common error is closing the log with a general statement such as “keep communicating.” Choose one control or decision that can be examined again.

Step 8: Stabilise the routine over 14 days

Use the first three days to practise the questions, the next four days to improve the log, and the following week to review patterns with the person who owns the affected control. The exact cadence can change, but the routine needs enough repetition to show whether the behaviour survives production pressure.

At the end of the 14-day period, ask four questions. Which question exposed the most useful evidence? Which concern was hardest to close? Which control repeatedly depended on personal vigilance? Which decision should be redesigned rather than discussed again?

Verify the result by comparing the original decision with the current decision rule. If the team now knows what evidence is required, who decides, and what happens when the condition is not met, curiosity has become part of Safety Leadership. If the team only has a longer list of observations, the routine has created paperwork rather than learning.

For a related operating rhythm, see how to run a safety meeting that surfaces bad news. The meeting works best when it receives questions whose owners and decisions are already clear.

Final checklist for supervisors

• Choose one recurring decision with a meaningful safety consequence.
• Ask for the expected condition before asking what went wrong.
• Invite the newest observation before experienced voices frame the answer.
• Separate a familiar condition from an effective control.
• Define how technical dissent will be assessed and escalated.
• State the control decision aloud and assign an owner.
• Review patterns without ranking people by question count.
• Repeat the routine for 14 days, then redesign weak decisions.

Andreza Araújo’s Make The Difference: Be a Leader in Health & Safety is a useful companion for supervisors who want to turn this routine into daily Safety Leadership. Her approach keeps the focus on decisions, evidence, and the conditions that make safe behaviour possible.

Supervisors who want a broader diagnostic can also review the difference between psychological safety, trust, and error tolerance, then compare the result with the signs of conformity pressure. When the pattern needs a formal response, this bad-news meeting guide gives the supervisor a focused next step.