Observation vs Interpretation in Feedback:Label Each
Observation vs interpretation in feedback: one is what happened, the other is your guess. Say which is which and feedback invites an answer, not a fight.
Observation vs interpretation: observation is what happened. Interpretation is what you decided it meant. Give feedback as: here is what I saw, here is what I took from it, is that right? Hand over the interpretation as if it were the observation and feedback turns into an accusation.
Observation vs interpretation in feedback: you are probably wrong
Let's start with the uncomfortable part. Your interpretation is a guess.
A good guess, often. You know your business. You've seen this kind of thing before. But a guess all the same, and you're making it from a narrow view. You're working evenings. You see a fraction of what your contractor does. You weren't in the room for most of it.
So when you say "you clearly don't care about this client", you aren't reporting a fact. You're reporting a conclusion you reached alone, with half the picture, and presenting it as settled.
That's the whole problem. Feedback goes wrong less often because the observation is false and more often because the conclusion is welded onto it so tightly nobody can pull them apart.
Two things that look like one
An observation is something a camera would have caught. A reply went out on Wednesday. A figure didn't match a spreadsheet. Three different dates were given in one call.
An interpretation is the story you built on top. They don't care. They're disorganised. They're hiding something. They've lost interest.
The trick is that the story arrives instantly and feels exactly like seeing. You don't notice the join. By the time you speak, the two have merged into one sentence: "You gave the client three different timelines because you weren't paying attention."
Count the parts in that sentence. One is a fact. The rest is a theory about their mind.
Free guide · 21 pagesAmbiguity is the cruelty.The Performance Conversation Playbook: how to tell someone the truth about their work.Get the free guide →What the same moment looks like three ways
Here is one event, delivered badly, better and best. The event: a client asked about timelines on a call, and the person you work with gave several different answers.
| How you say it | What it sounds like | What the other person hears |
|---|---|---|
| Interpretation as fact | "You weren't prepared for that call." | An accusation. They defend themselves, and the talk is about whether they were prepared, not about the call. |
| Observation only | "On Tuesday's call you gave three different answers about timelines in five minutes." | A fact they can look at. Fair, but it leaves them waiting to hear what you think it means. |
| Observation, interpretation, question | "On Tuesday's call you gave three different answers about timelines. I took it that the plan wasn't clear in your head yet. Is that right?" | An invitation. They can correct your read, and the correction is the useful part. |
The third row is the observation vs interpretation fix the guide recommends: here is what I saw, here is what I took from it, is that right? Notice the question at the end is real. You don't know the answer.
What you were missing
So what do they say when you ask? Often something you didn't have. The guide lists the usual suspects: they'd already been told something different, the deadline had moved, there was context you lacked.
Run those against the timelines call.
- Maybe the client changed the scope halfway through, and each date was right for the version being discussed at the time.
- Maybe you gave them one date last week and a different one on Friday and they were trying to reconcile your own messages.
- Maybe they really weren't prepared. That happens too, and now it comes from them rather than from you.
Two of those three are your fault. You'd never have known if you had led with the accusation. You'd have walked off confident, and wrong, with a person who now thinks you don't read your own emails.
That's the real cost. Not only that it feels harsh. It leaves you confidently wrong in a way that's hard to walk back. Once you've told someone they don't care, "sorry, I got that wrong" never quite lands.
How to separate observation vs interpretation before you speak
You can do this in your head in about a minute. The test is simple: could a stranger watching a recording see what you describe?
- Write the thing you want to say. One sentence, as it first comes out.
- Underline anything a recording couldn't show. "Careless", "didn't care", "wasn't ready", "avoiding", "rushed". All interpretation.
- Move those words into a second sentence. Begin it with "I took that to mean".
- Add the question. "Is that right?" or "What am I missing?"
It feels fussy the first time. By the fifth, you do it without the pen.
And do it for good news too. "You're brilliant with clients" is an interpretation. "The way you opened that call by repeating back what they'd asked for" is an observation. The second one they can repeat on purpose. This is part of the wider habit in how to give specific feedback: the more your sentence points at a thing, the more use it is.
Words that give the game away
Some words are interpretation wearing a disguise. Watch for them in your own mouth.
- Always and never. They claim a pattern you haven't shown. Name the one instance.
- Clearly. Nothing is clear. If it were, you wouldn't need the word.
- Obviously. Same.
- Attitude. You can't see an attitude. You can see someone not replying.
- Seems like you. At least honest. Keep going and ask the question.
None is banned. You're allowed to have a view. You're allowed to say it. The rule is just that you say which part is the view.
Free assessmentHow trapped are you, really?Take the Corporate Suffocation Index, the free solopreneur readiness assessment.Take the assessment →Then use the gap
When their account differs from yours, resist the urge to restate your case louder. That gap is the most important thing in the conversation.
Listen to the substance first. They may have context you lack. They may have been responding to constraints you set. Or the expectation may genuinely never have been communicated, in which case the fault was yours and the fix is cheap: say it now, write it down.
If you still disagree after hearing them, say so plainly, and say what you'd need to see. An acknowledged disagreement is workable. One where you nodded along and privately kept your original verdict is not. They can usually tell. How to keep that disagreement from stalling is in how to follow up on feedback.
There's a related trap worth a mention. Feedback that mixes in your reading of someone's motives is far more likely to be blurred with a conversation about pay or about whether they should stay. Keeping the observation clean helps you keep the conversations separate, which is the subject of feedback, development and pay conversations.
Say it out loud once before you say it for real
Try the three-part sentence on the dog first. Or on the wall. Or in the shower. It sounds odd, and that is the point: the moment you hear "I took that to mean" in your own voice, you notice how often you'd have skipped it.
Pay attention to the question at the end. If you catch yourself asking it in a tone that means "admit it", it isn't a question. It's the accusation again, with a question mark on top. Ask it as though you honestly expect to learn something. Because you should. Most of the time, you will.
And if the answer surprises you, say thank you. That one sentence teaches them that correcting you is safe, which is worth more than the original point.
Free guide · 21 pagesAmbiguity is the cruelty.The Performance Conversation Playbook: how to tell someone the truth about their work.Get the free guide →Why this matters more when you work alone
On a bigger team, somebody else sees the same moment. They'll tell you your read is off. Here, you don't have that. You're the only witness, and you're tired.
That means your interpretation goes unchallenged unless you build the challenge in. The question at the end of the sentence is how you do that. It's a cheap way to borrow a second pair of eyes: theirs.
Hold your view a little more loosely than you would if you had watched all day. You didn't.
Free assessmentHow trapped are you, really?Take the Corporate Suffocation Index, the free solopreneur readiness assessment.Take the assessment →Frequently asked questions
What is the difference between observation and interpretation in feedback?
An observation is what happened, something a recording would show. An interpretation is the meaning you attached to it, such as "they don't care" or "they were unprepared". The first is a fact. The second is a hypothesis, and it is often wrong.
Do I have to leave my opinion out entirely?
No. Say what you took from it. Just label it as your reading and ask whether it is right. Delivering the opinion as though it were the observation is the mistake, not having the opinion.
What if they say my interpretation is wrong?
Listen to the substance before you answer. They may have context you lacked. If you still disagree afterwards, say so plainly and say what you need to see. Pretending to agree is worse than disagreeing openly.
Does this make feedback too soft?
No. You still say the hard thing. You say it in a form they can respond to, so you hear about the explanation you did not have. Soft is being vague. This is being precise.
The full method for observation vs interpretation, with the checklists, is in The Performance Conversation Playbook, a free 21-page playbook.
How trapped are you, really?
Take the Corporate Suffocation Index, the free solopreneur readiness assessment.