An observation is something you can directly see or verify. An inference is a conclusion you draw from what you observed. "She hasn't spoken in twenty-five minutes" is an observation. "She's checked out" is an inference.
Every science class teaches this. Good leadership models already name it too. Argyris's ladder of inference is one. The hard part is practicing it in a live room, under pressure. And the gap between the two is where most leadership mistakes begin.
Why the difference matters at work
Inference isn't the problem. You have to draw conclusions to lead. The problem is drawing them so fast that you can't tell them apart from what you saw. The first one feels like information. It's a conclusion.
Medicine has a precise way to talk about this. A sign is objective: blood pressure, a rash, a fever. Two doctors in the same room will see the same sign. A symptom is what the patient experiences, and you can only learn about it by asking or inferring.
Leadership works the same way. The sign is yours to observe. What's driving it belongs to the other person.
One sign, four causes
Take silence. Someone stops contributing in a meeting. That's the sign. Now, what does it mean?
- Deference. They've learned over months of meetings that speaking up doesn't change the outcome, so they've stopped spending the energy.
- Fear. Something happened that made the room feel unsafe, maybe a comment that landed wrong and was never addressed.
- Exhaustion. They're carrying something outside the room and have nothing left to give today.
- Strategic withdrawal. They've concluded they can't win this one and are deliberately conserving energy.
Four causes, one sign. And the response that helps one makes another worse. Push someone who is afraid and they get smaller. Give more space to someone who has already withdrawn and they drift further. Try to motivate someone running on empty and you speed up the burnout.
You'll feel confident whichever one you pick. That's the trap. A wrong read rarely feels wrong. It feels like experience.
How leaders blur the line
There's a name for the moment the thinking stops: premature closure, accepting a diagnosis before it's been verified. Pat Croskerry, an emergency physician who has spent decades studying diagnostic error, has written about it extensively as one of the most common causes of misdiagnosis in medicine. Not because doctors are careless, but because pattern recognition is fast, and fast feels like knowing.
Leaders do the same thing. You walk into a room carrying your history, your discomfort with conflict and your need to look like you know what's going on. Then you start finding evidence for the read you walked in with.
It's not observation. It's confirmation.
How to separate them
Start on paper. After your next three meetings, write one sentence that describes only what you saw. Then check it.
| Inference | Observation |
|---|---|
| The team is stuck. | We've circled the same decision three times this month without landing. |
| He's trying to control the meeting. | He answered every question before anyone else spoke. |
| The team has lost motivation. | Nobody asked a question in the last two planning meetings. |
| She's resistant to the change. | She asked three questions about the timeline and none about the goal. |
Watch for the words that sneak inference back in: seemed, appeared, felt, clearly. "He seemed frustrated" is still an inference. "He pushed back twice and then stopped talking" is an observation.
Then do what a good doctor does. Before you act, list more than one possible cause. Ask what you'd expect to see if each one were true. Then ask the question that almost always gets skipped: Am I actually seeing it, or just finding what I went looking for?
The payoff
Separating observation from inference sounds slow. In practice it gets fast, a few seconds once it's a habit. And it changes what you can do. You can't intervene on a feeling or give feedback on a vibe. You can name a behavior: "For the last three sessions, every time we move toward a decision, the energy drops and the room waits." That gives you, and the team, somewhere to look.
This is the first step of Diagnostic Leadership, the discipline of reading what's actually happening before deciding what to do. The first question is the one this article is about: What do I see?