The 5-minute arrival scan

When I arrive on site, there's usually a moment, sometimes several minutes long, where I feel a bit lost. The work is happening around me. People are moving, doing things, solving problems I can't yet see, and often it’s a new type of work and workplace that I’m not familiar with. And I'm standing there, not quite sure where to look or what to make of any of it.

That feeling used to make me reach for a question quickly. Something to anchor me, to feel purposeful, to signal that I was there to engage. What I've learned, slowly, is that the rush to ask is worth resisting. Because the longer I stay with the discomfort of not yet knowing, the more I start to see.

Something catches my eye. A tool that's been modified in a way that wasn't in any manual. Someone's posture, reaching a bit further than seems easy. A label that's faded past reading. A space that should be clear but isn't. And from those small observations, the questions that actually matter start to form. Not from a list I brought with me, but from what's right in front of me.

That's the idea behind what I've been calling The Five-minute arrival scan (link to pdf below). Before you open your mouth, take a moment to look. Five things tend to be worth paying attention to:

Bodies. Posture carries information people rarely think to mention. Someone bent at an angle, reaching further than feels comfortable, holding a position that requires continuous effort. It doesn't always mean something is wrong. But it usually means the work is costing more than it looks.

Hands. Hands are often where adaptation becomes visible first. How many hands does this task take? What did someone have to put down to do it? When a person is using their body as a third hand — bracing, wedging, holding something in place with a knee — that's worth understanding before you ask anything else.

Problem-solving in action.The locally made support under a pipe. The tape on a handle. The handwritten note on a control panel. Someone encountered a problem here, addressed it, and left a trace. The adaptation has usually been there long enough that nobody notices it anymore. Your job is to notice it, and to be curious about what problem it was solving.

Absence. The empty holder. The label that's faded past reading. The space that should be clear but isn't. Absence is harder to see than presence, which is probably why it goes unreported. When something that should be there isn't, it's worth sitting with that long enough to understand whether it matters.

Flow. Work is always moving, even when it looks still. Materials, information, decisions, and problems are arriving, being worked on, and passed on. Some of that flow is smooth. Some of it is interrupted, delayed, or quietly building pressure. Where is the work coming from? Where is it going next? Where is work active, and where is it waiting? Where does it slow down or get stuck? Where flow is smooth, work feels easy. Where flow is disrupted, people adapt — and that adaptation is usually worth understanding.

These aren't problems to fix on the spot. They're clues, the raw material for better questions, grounded in what's actually happening rather than what you assumed before you arrived.

The 5 minute arrival scan is part of a conversation playbook I'm working on. More on that in future issues.

On the Pre-accident Investigation podcast

A few weeks ago I had a conversation with Todd Conklin on the Pre-Accident Investigation Podcast — episode 595, Beyond Checklists: How Conversations Transform Safety Culture. Todd is one of the most generous interviewers I've encountered. He asks things that make you think rather than just explain, and the conversation went to some places I hadn't quite articulated before.

If you have 30 minutes to listen, you can find it here.

A question for you

I'm going to try something with this newsletter. If you have a question about having safety conversations, something you're finding difficult, a situation you're not sure how to approach, a pattern you keep running into, or even a great experience, send it to me. Reply directly to this email, or use the contact form on the website

I'll do my best to respond to the message, and where a question seems like it might resonate with others, I'll address it in a future issue of this newsletter. Promise to keep your name out of it entirely.

The book started from conversations. It seems right that the newsletter should too.

Daniel