The first thing they teach you in EMT class isn't how to stop bleeding. It isn't CPR. They teach a question you ask, sometimes to yourself, sometimes out loud. Every call, before you touch anyone.
Is the scene safe?
Before you reach the patient, you stop and read the situation. Is there traffic still moving? Downed wires? A dog, a fire, a second patient nobody mentioned? The instinct — the human instinct, the good instinct — is to run to the person on the ground. The training exists to override it. A responder who rushes in and becomes the second patient hasn't helped anyone. All they've done is doubled the problem and removed the one person who was supposed to fix it.
You are no good to the patient from inside the wreck.
It took me fifteen years of leading teams to understand that this is a management principle, and I learned it backwards — by violating it, over and over, before I ever heard the words said aloud.
You come in to lead a new team and a launch is failing. A key person just quit. A VP who had set the direction suddenly isn't so sure. The instinct is to run in. To absorb the problem, match its urgency, start moving fast because moving fast feels like leadership. And like the rookie sprinting toward the patient, you don't notice that you've made yourself part of the emergency instead of the person managing it.
In the field there's a discipline for this. Before you touch the patient, you read the scene. Over the years, that read became five questions I now run before I start anything new. I call it the BRIEF.
Background — what happened before you got here.
Relationships — who your people actually are, not their titles.
Interests — what they want, not what they say they want.
Exposures — the hazards you'll walk past if you move too fast.
Foundation — what has to be true before any change holds.
Each one of these is important to Scene Safety, but today I want to focus on just one.
Background.
What happened before you got here?
Every team you inherit has a history, and almost none of it is visible on your first day. The people who carry it won't volunteer it. So you go looking. What were the earlier attempts to fix this, and why didn't they land? What did the last leader do that the team is quietly relieved is over — and what do they miss more than they'll admit? What got promised that isn't written down anywhere?
This is the part new leaders skip, because it feels slow and the urge is to start driving change on day one. But the background is not gossip. It is scene data. You cannot safely approach what you don't understand, and you cannot understand a team without understanding what it has already survived.
I learned this by getting it wrong. Early in a new design leadership role, I found a standing meeting that always ran long and a documentation ritual that looked like duplicated work. Classic overhead. So I eliminated it.
What I hadn't looked for was why it existed. That meeting was the only recurring reason two halves of the team, with no shared manager, were ever in the same room. The documentation ritual was also how a quiet senior contributor made her work visible at review time. I'd cleared a visible inefficiency and created two invisible problems. I found out about the second one when someone mentioned, offhand, that quiet IC had been updating her résumé since spring.
I had run straight for the car.
Walking onto a scene without reading it first is how a responder becomes the second patient. Walking into a new team the same way is how a leader spends their first ninety days solving the wrong problem at full speed.
Scene safe. Then in.
David
P.S. What's your version of reading the scene before you act — the question you ask first, or wish you had? Hit reply. I read every one.