The Worker Who Arrived Today

Yesterday, he was one of your safest employees.

Twenty years of experience, well trained, no recent incidents. He knows the machine, the procedure, the hazards and the controls, and he has performed the same operation thousands of times.

Nothing in your risk assessment changed overnight.

Same machine. Same procedure. Same PPE. Same workplace. Same employee.

Except that he is not quite the same employee.

Last night he barely slept. This morning, before leaving home, he had an argument with his wife — the kind of argument that does not end when the conversation ends. His body arrived at work at 7:00. Part of his mind is still at home.

At 7:12, he reaches toward the machine.

And suddenly a question appears that is much harder to capture in a risk matrix: who exactly came to work today?

The person our systems expect

Safety has become remarkably good at understanding work. We identify hazards, assess risks and define controls. We analyse tasks, train people and verify competence. We investigate incidents and study human factors.

When we describe the person performing the task, however, we tend to reach for relatively stable categories: trained, competent, experienced, authorised, medically fit. The risk assessment needs this abstraction. We cannot redesign it every morning according to how each employee feels.

But an abstraction can quietly become an assumption. We begin to imagine a relatively stable human being entering a changing workplace, when real life is almost the opposite. The employee who was competent yesterday remains competent today — but competence and available human capacity are not necessarily the same thing. The machine may be unchanged. The human never entirely is.

What crosses the factory gate with us

A worker does not leave their life in the car park. A parent worried about a child does not stop being a parent when putting on safety shoes. Grief does not disappear when someone scans their badge, and an argument does not automatically end when the shift begins. Neither do financial worries, loneliness, excitement, fear, love, uncertainty or hope. We carry our lives with us.

Research has already shown that this matters for safety. In one of the first studies to look directly at the question, Cullen and Hammer (2007) found that conflict between family life and work was associated with lower safety compliance and lower safety participation — and, tellingly, it was the interference of family with work, rather than of work with family, that carried the effect. Later studies have linked the same kind of conflict to cognitive failures at work and to fatigue. The details vary across industries and samples, but the broader message should not surprise anyone who has spent enough time around real workplaces: what happens outside work can affect how we function inside it.

This is not an argument for employers to investigate people's private lives. Quite the opposite. There should be a boundary. But respecting that boundary does not require us to pretend that nothing exists beyond it.

Human Factors — and the human beyond the factors

Human Factors has transformed safety for the better. It has taught us to think about fatigue, workload, cognition, attention, ergonomics, limitations, system design and the conditions in which people actually work. Safety-II pushed us further, reminding us that human variability is not merely a source of failure; it is also one of the reasons complex systems work at all. People adjust, interpret, compensate and adapt.

These developments corrected an old and damaging idea: that if we could simply make people behave correctly, safety would follow.

But I wonder whether another step remains. We have become very good at understanding human performance. We may still have something to learn about human existence.

A human being does not arrive at work carrying only cognition, competence and behavioural tendencies. We arrive carrying relationships, fear and hope, identity and responsibility, loss and conscience, uncertainty, dignity and meaning. These are not hazards to be entered into a register. They are not disorders to be diagnosed, nor variables that management needs to measure. They are simply part of being human — and our understanding of safety becomes incomplete when we recognise the human factor but lose sight of the human being.

Human-as-Imagined and Human-as-Arrived

There is a distinction I have started thinking about. It borrows its shape from Erik Hollnagel's contrast between Work-as-Imagined and Work-as-Done, but it points at the person rather than the task.

We might call the first person Human-as-Imagined: the one our systems necessarily describe — trained, competent, experienced, fit, authorised.

Then there is Human-as-Arrived: the actual person who walked through the gate this morning.

Usually the two overlap closely enough. Sometimes they do not. The competent worker may be exhausted. The experienced supervisor may be grieving. The normally attentive technician may have received frightening news ten minutes earlier. The careful operator may simply be having the worst morning of his year. His competence has not disappeared; his available capacity today may have changed.

That leads me to a simple proposition: competence may be relatively stable. Human capacity is not.

If that is true, it has consequences for how we think about safety.

A good safety system should survive a bad day

The wrong conclusion would be that managers need to know everything happening in employees' lives. They do not. Another wrong conclusion would be to create yet another checklist — Are you emotionally fit for work today? — which could quickly become intrusive, superficial and potentially harmful.

There is a better question: how much human imperfection can our system safely tolerate?

Engineering safety learned this lesson long ago. We do not protect someone from a dangerous machine merely by telling them to be careful. We use guards, interlocks, isolation, fail-safe design and redundancy. We build layers because we know that attention is not constant and human beings are not perfect.

The same principle deserves a broader interpretation. A mature safety system should not require every good employee to arrive as the best version of themselves every morning in order to go home safely. That does not lower personal responsibility. It acknowledges reality.

Design not only for human error, but for human life.

Sometimes the control is another human being

Not every barrier is engineered.

Imagine the same worker at 7:10. A colleague looks at him and says: "You don't seem yourself today. Are you okay?"

Maybe the answer is "I'm fine", and nothing more is needed. But perhaps the answer is: "Not really. I need another pair of eyes on this one."

That sentence may never appear in an incident database. There will be no corrective action, no investigation, no lost-time injury. No KPI will record what was prevented. Yet it may be one of the most sophisticated safety behaviours in the building.

For it to happen, however, several things must already exist. People must notice one another. Asking for help must not be read as incompetence. Supervisors must be able to tell vulnerability from weakness. And the culture must make it possible to say: I am competent. I am responsible. And today I am not at my best.

That is not the opposite of safety competence. It may be one of its highest forms.

Perhaps we have been asking only half of the question

For decades, the field has refined its understanding of the human at work: human error, human reliability, Human Factors, human performance, human adaptation, safety culture. Each has moved us forward.

But another question is waiting for us. Not only how does the human affect the system? Nor only how does the system affect human performance? But: who is the human being inside that system?

And eventually, an even more uncomfortable question: what kind of human being does the system itself help create? Does it develop judgment or dependence? Responsibility, or compliance alone? The courage to speak, or the instinct to remain silent? Care for another person, or responsibility only for one's own task?

Those questions go beyond the worker who had an argument before coming to work. They lead somewhere much larger, because safety systems do more than manage hazards. They are environments in which human beings spend thousands of hours of their lives. And environments shape people.

The person behind the risk

There is a human assumption underneath every risk assessment that we rarely write down. Before probability, before severity, before ALARP, before compliance, before any ISO standard, we have already decided something: this person is worth protecting. Not because they are productive. Not because they are experienced. Not because losing them would affect our KPIs. Because they are a person.

That simple truth deserves a larger place in the future of safety.

Our risk assessments will never know everything about the person who arrives at work, nor should they. But our systems can be designed with enough humility to recognise that the human being standing in front of the machine is larger than the role written beside their name.

Tomorrow they will arrive again.

Same badge. Same training record. Same job description.

But carrying another day of being human.

And perhaps the future of safety depends not only on understanding how humans work. Perhaps it also depends on understanding what it means to be human.