Safety Leadership: 4 Myths About Field Presence That Keep Leaders Decorative

A plant manager walks the production floor, greets a few operators, asks whether everything is safe, and leaves with a positive impression. The visit is recorded as leadership visibility. Yet the permit is still being rushed, temporary barriers are still missing, and supervisors still believe that raising a concern will slow the line.

Field presence matters only when it changes what leaders can see and what the operation is required to decide. Across more than 250 cultural transformation projects supported by Andreza Araujo's team, the recurring lesson is uncomfortable: a leader can be physically present and operationally absent. The difference is not the number of visits. It is the quality of the questions, the response to bad news, and the follow-through after the visit.

Why field presence is often mistaken for safety leadership

Field presence is the direct observation of work by someone with enough authority to understand conditions and act on what the team reports. It includes walking the job, asking about the plan, testing whether controls are usable, and deciding what happens when production pressure conflicts with the safe method.

A visit becomes decorative when it produces a photograph, a completed checklist, or a pleasant conversation without changing a decision. That distinction aligns with James Reason's distinction between visible actions and latent conditions. The person closest to the event may be the last link in a chain whose earlier links include planning, maintenance, supervision, staffing, design, or resource allocation.

The purpose of a leadership visit is therefore not to prove that the leader cares. It is to expose the conditions that the normal reporting system can hide, then make the responsible decision visible before a serious event makes it unavoidable.

Myth 1: A walk is successful when the leader is seen

Visibility is useful because employees notice what leaders attend to. It becomes misleading when presence itself is treated as the outcome. A leader who appears every week but never removes a recurring obstacle teaches the workforce that speaking up is ceremonial.

The better test is whether the visit produces a clear operational consequence. Did the team stop a task, redesign a step, repair a barrier, change a staffing assumption, or escalate a decision that was previously trapped at the front line? If the answer is no across repeated visits, the routine may be functioning as public relations rather than control verification.

Leaders should record three linked facts after each visit. First, what exposure was observed. Second, who owns the decision that can change it. Third, when the leader will verify that the change reached the work. A log with only observations creates a museum of problems.

Myth 2: The safest question is “Are you safe?”

Most people know how to answer that question without revealing much. They can say yes because they want the interaction to end, because they do not trust the response to bad news, or because they have learned that the question is a greeting rather than an invitation to examine the work.

Specific questions make the actual work easier to discuss. Ask which part of the plan does not match the task, which control is hardest to use, what the previous shift had to improvise, and what would make the job safer without adding a paper step. These questions move the conversation from personal reassurance to operating conditions.

The leader also has to respond in a way that reinforces accuracy. When every concern receives an immediate promise, the team may learn to report only simple problems. When every concern receives blame, the team learns silence. The mature response is to clarify the exposure, assign the decision, and return with evidence that the concern was handled.

Myth 3: A checklist makes leadership visits consistent

A checklist can protect the routine from memory gaps, especially when several leaders share responsibility. It cannot create attention, judgment, or the authority to act. A completed form may show that a question was asked while concealing that the answer was vague, the control was not tested, or the person who could fix the issue was not present.

Use the checklist as a prompt, not as the visit's central product. A useful field review should combine a planned dimension, such as critical controls or handover quality, with one question chosen from what the leader can see in real time. That combination prevents the visit from becoming a scripted audit and helps the leader notice deviations that the template did not predict.

Review the quality of the evidence, not only completion. A strong record identifies the task, the exposure, the control in use, the gap between the plan and the work, and the decision owner. It also shows whether the issue was verified later. Without those elements, the checklist can make weak leadership look orderly.

Myth 4: Leaders should solve every problem during the visit

Immediate action is essential when a serious exposure is active. However, solving every issue personally creates a dependency that weakens the operating system. Supervisors wait for the senior visitor, EHS becomes the routing desk, and the workforce learns that ownership belongs to whoever has the highest title.

Effective leaders separate urgent containment from durable ownership. They stop or control the immediate exposure, then ask which role should have detected the condition, which decision right was missing, and which routine should prevent the same problem from returning. The leader remains accountable for the system without becoming the permanent owner of every local correction.

This is where the leadership principle in Andreza Araujo's book Make The Difference: Be a Leader in Health & Safety becomes practical. Care is not the same as personal rescue. A leader builds a chain of decisions that keeps care present when the leader is not on the floor.

What to do instead of performing field presence

Start by choosing one exposure that the ordinary dashboard does not describe well. It might be a temporary control, a rushed handover, a maintenance backlog, or a production decision that repeatedly changes the planned method. The focus should be narrow enough to observe and important enough to require leadership judgment.

Before the visit, identify the decision you need to understand rather than the photograph you want to collect. During the visit, let the person doing the work describe the mismatch between the plan and reality. Ask for a demonstration of the control when it is safe to do so, because a verbal assurance cannot establish whether the control is available, usable, and maintained.

After the visit, assign one owner with the authority and resources to act. Set a verification date that is close enough to preserve urgency, but far enough to test the changed condition under comparable work. Then review whether the action changed the task or merely added another instruction.

• Observe a real task rather than a prepared demonstration.
• Ask for the plan-to-work mismatch and the hardest control to use.
• Separate immediate containment from the decision that prevents recurrence.
• Assign ownership outside the visit when another role should control the condition.
• Verify the change in comparable work and record what evidence was found.

Field presence earns its place in a safety leadership system when employees can predict what happens after they report an exposure. The visit should make risk more visible, decisions more traceable, and control quality more testable. If it only demonstrates that a leader was present, it has not yet demonstrated leadership.

Andreza Araujo's work on safety culture connects this shift from symbolic activity to operating evidence with the broader question of whether declared values survive daily decisions. Her book Safety Culture: From Theory to Practice is a useful reference for leaders who want to examine that gap without confusing ceremony with culture.