Distinguish observable data from interpretation
Separate what a camera would record from what you made of it.
Why it works
The first and most foundational error on the ladder is treating interpretations as if they were observations. "She was dismissive" is an interpretation; "she did not respond to the last two emails and cut the meeting short by fifteen minutes" is data. Interpretations can be wrong; data can be checked. Confusing them makes disagreements about interpretations feel like disagreements about facts, which are much harder to resolve.
How to do it
- When you describe a situation, ask: what would a video camera have captured here?
- Write the observable events separately from your interpretation of them.
- Test whether two observers with different priors would see the same "data" or different ones.
- When in conflict with someone, find the lowest rung you both agree on before discussing interpretation.
Evidence
The distinction between description and evaluation is fundamental in behavioral feedback research and in nonviolent communication frameworks. Reducing evaluative language in conflict situations is associated with reduced defensiveness, consistent with research on the impact of labeled vs. described behavior. (mechanistic)
Perfect separation of observation and interpretation is impossible — all perception is theory-laden at some level. The practice aims for better separation, not pure objectivity.
Sources
- Rosenberg (2003), Nonviolent Communication — observation vs evaluation as a foundational step
Common mistake
Believing that because something feels obviously observable, it is — "she was hostile" feels as concrete as "she raised her voice," but the former is a judgment.
Practice this with IX Coach
7 days free, then $40/month (~$1.30/day).
More practices for The Ladder of Inference
- Notice which data you selected — and which you ignored
Your conclusions are built on a sample of the available data — ask what the sample excluded.
- Surface and examine the assumptions you are making
Name the assumptions filling the gap between the data you selected and the interpretation you reached.
- Test conclusions before acting on them
Treat your conclusion as a hypothesis and find one piece of evidence that would confirm or disconfirm it.
- Walk down the ladder together in disagreements
In conflict, stop arguing about conclusions and descend together to the data level.
- Slow the reflexive loop
Your current beliefs shape which data you select, reinforcing themselves — interrupt this loop deliberately.
Related concepts
- Thinking, Fast and Slow, Made Usable
Two systems, the biases they create, and when to slow down
- Hanlon's Razor: Never Attribute to Malice What Stupidity Can Explain
The charitable-attribution heuristic and why it usually serves you better
- The Map Is Not the Territory
Mental models are tools, not truths — how to use them without being captured by them
- Cognitive Reframing, Made Practical
How reappraisal changes emotion, the common distortions, and how to do it without toxic positivity