
Safety may appear first in the strategy, but employees discover its real importance by observing what leaders notice, ask about and follow up.
A safety policy cannot shape daily behaviour on its own. Priorities become real through management routines, shopfloor conversations and the response leaders give when they encounter a deviation.
One short exchange during a factory visit showed me how quickly those signals can influence an organisation.
The difference between the stated priority and the visible priority
In many factories, safety appears first on the list of priorities.
It is written above People, Quality, Delivery, Cost and Environment. It appears in policies, presentations and communications from senior management.
Although new employees are told that safety comes before production, people discover the organisation’s real priorities by watching what leaders notice, ask about and follow up.
I was mentoring a factory director during a shopfloor walk when we approached an operator who was not wearing gloves. The director greeted him and shook his hand, as he had done with the other employees along the way. We then continued to a production follow-up board, where he spoke with the team leader.
-“Is everything ok?”
-“Where is this part? It is needed.”
The conversation immediately moved to delivery.
The missing gloves had been visible, but they had generated no question. The missing production part received attention straight away.
That short sequence communicated the factories real priorities more powerfully than any poster or policy could.
People watch what leaders notice
Leaders communicate whenever they walk through a factory, including when they say nothing.
If a director walks past a safety deviation without seeing or commenting on it, that deviation gains a degree of acceptance. When this happens repeatedly, it gradually becomes normal.
The operator sees that it was not questioned. The team leader sees that it did not interrupt the visit. Other employees see that production receives more attention.
Nobody needs to announce that delivery is more important than safety. The pattern of leadership attention communicated it for them.
The same principle applies beyond safety. If leaders only ask about today’s output, teams will concentrate on today’s output. If they consistently ask why the plan was missed but rarely ask why the plan was unreliable, people learn to explain results rather than improve the planning system.
The organisation becomes attentive to whatever the leaders repeatedly notice.
Safety indicators arrive after the event
Most safety results are lagging indicators. They tell us what has already happened: an accident occurred, somebody was hurt or time was lost.
These measures matter, but they do not tell us whether safe working conditions are being maintained today.
That evidence is found on the shop floor:
- Are people using the required personal protective equipment?
- Does the workstation safety documentation match the work being performed?
- Have changes to the process, workstation or team introduced new risks?
- Do operators understand the standard?
- Can they raise an inconsistency and receive a useful response?
These conditions exist before an accident appears in the indicators.
A leader who observes the work, compares it with the standard and speaks with the operator can act while the information is still a warning. Waiting for the safety results means waiting for something to go wrong before giving the system management attention.
A two-minute leadership intervention
During the mentoring session, I asked the director to return to the operator and request the safety document for the workstation.
It took approximately two minutes and involved the team lead. The document confirmed that gloves were required.
The exchange between the director and the operator was constructive. They looked at the requirement together and clarified what was expected.
The following day, we walked through the area again. The operator was wearing his gloves.
More importantly, he has identified another inconsistency.
Changes had been made in the area, including changes to workstation and the arrival of new operators. If gloves were required for his activity, he believed they should also be required at another workstation. However, that workstation’s safety document did not specify them.
The director’s question had achieved more than correcting one visible deviation. It encouraged the operator to examine the wider situation and expose a weakness in the documentation.
If the director had simply instructed him to put on his gloves, the immediate problem might have disappeared. By requesting the workstation document and involving the operator and team leader, he created an opportunity to compare the written requirement with the real working conditions.
The operator became part of improving the system.

How leadership questions shape behaviour
This principle also becomes visible during daily management meetings.
After an accident, it may be accepted that no initial description is available within 24 or even 48 hours, but when production is delayed, missing parts, lost hours and recovery actions are challenged immediately.
A complete accident investigation can take time. Evidence must be gathered, causes understood and effective countermeasures developed. However, the organisation should still establish the basic facts quickly:
- What happened?
- Where and when did it happen?
- What immediate action was taken?
- Is the same risk present elsewhere?
If leaders tolerate delays in answering those questions whilst demanding immediate explanations for lost production, employees notice the difference.
The published priority may say Safety first. The management routine says something else.
Observe safety before asking about delivery
This does not mean leaders should stop asking about delivery. Customers depend on the operation, and delivery problems need to be understood.
The sequence matters.
Before asking why a production target has been missed, a leader walking through the workplace can first observe how the work is being performed. Look at the personal protective equipment. Compare the task with the workstation standard. Speak with the people doing the work. Ask whether recent changes have created a new difficulty or inconsistency.
A few questions can reveal whether the standard is understood, usable and still appropriate.
This also prevents every deviation from being automatically treated as an operator failure. In the glove example, the first visible issue concerned one person. The conversation then revealed that changes in the area had created a wider question about the safety documentation.
The operator’s behaviour mattered, but so did the management system around him.

Making safety first visible in practice
When I enter a factory, I first try to understand its rules and the requirements of its sector.
I then respect those rules visibly. I wear my safety cap and protective glasses throughout the shopfloor visit, even when they are compulsory only in specific areas. This avoids ambiguity and helps me lead by example.
When I am uncertain, I ask. My question may come from experience in another factory or simply from encountering a process I do not yet understand. The purpose is to compare what I am seeing with what should be happening while respecting the knowledge of the people doing the work.
I also challenge leadership teams when an incident has not been described within 24 hours. The full problem-solving process can take longer. The organisation still needs to establish the initial facts, take immediate protective action and determine whether others face the same risk.
Strategy becomes credible through repeated management behaviour.
If Safety is genuinely the first priority, it should receive the first observation, the first question and the same disciplined follow-through that leaders already give to Delivery.
Primus Passus Consulting helps manufacturing leaders connect their stated priorities with daily management behaviours. By observing the real operation, making deviations visible and involving the people closest to the work, leadership teams can create safer and more reliable working routines without adding another layer of bureaucracy.
