How to Give Specific Feedback:Name the Moment, Not You
How to give specific feedback: name one moment, say what you saw, say it fast. The test, the swap table and the two-minute prep a busy solo owner can use.
To give specific feedback, name one moment, describe what you saw, and say it while you both still remember it. "Your communication needs work" is a verdict with no evidence. "On Tuesday's call you gave three different answers in five minutes" is something they can use.
How to give specific feedback: pick the moment first
Most feedback fails before you open your mouth. It fails because you walked in with an impression instead of an example.
An impression feels solid. "They're a bit careless." "Client handling isn't great." You've felt it more than once, so it seems true. But try saying it out loud to the person. What do they do with it? Nothing. There's nothing to fix, nothing to argue with, nothing to try on Monday.
So start with the moment. One. Recent. Something you both saw or can both look at.
Say you've brought in a freelancer to answer your customers. You noticed something off. Don't tell them they're "unclear". Go and find the actual email, or the actual call. That is your feedback. The impression was only the smoke.
No moment, no feedback. That sounds strict. It's the kindest rule you can adopt, because it stops you handing someone a vague unease and calling it guidance.
The test: could they disagree with it?
Here's a quick check. Good feedback can be disagreed with. Bad feedback can't.
"You're not detail-oriented" cannot be disagreed with. It's a judgment about who they are. They can only sulk or agree. "The invoice you sent on Thursday had the wrong company name on it" can be disagreed with. They can say it was the template. They can say the client changed it. They can say they fixed it an hour later. Every one of those replies gives you information you didn't have.
That's the point. Specific feedback opens a conversation. General feedback closes one.
The guide behind this post says it in one line: a specific example names a moment, describes what happened, and can be discussed and disagreed with. Hold your own feedback to that. If it can't be disputed, it isn't specific yet.
Free guide · 21 pagesAmbiguity is the cruelty.The Performance Conversation Playbook: how to tell someone the truth about their work.Get the free guide →Three things every piece of feedback needs
Strip it down and there are three parts. Behavioural, specific, timely.
Behavioural. You describe what they did, not what they are. Words like "careless", "lazy", "not a self-starter" are about character. You can't see character. You can see that a deadline passed without a message.
Specific. One moment, one example. Not "often". Not "always". If you catch yourself saying "you always", you've got a pattern, and you haven't named the first instance of it yet. Go back and find the first one.
Timely. Soon. While you both remember. That's the one most people skip, and it's the one that makes the other two easy. The cost of delay is covered properly in why delayed feedback costs more, but the short version is this: the same observation is thirty seconds in week three and a confrontation in month five.
Specific feedback versus vague, side by side
The fastest way to learn this is to see the swap. Here are common vague lines and what they become once you do the work.
| The vague version | What is wrong with it | The specific version |
|---|---|---|
| "Your communication needs work." | A judgment. No evidence, no action. | "In Tuesday's call, when they asked about timelines, you gave three different answers in five minutes. I think they left confused." |
| "You need to be more proactive." | Character, not behaviour. They can't tell what proactive looks like to you. | "The client asked a question on Monday morning and the reply went out on Wednesday. I'd like a holding reply the same day." |
| "Your work is sloppy." | An insult dressed as feedback. | "The report had two figures that didn't match the spreadsheet. Here are both. Can we look at how they got in?" |
| "Great job lately." | Warm and useless. They can't repeat it. | "The way you handled that refund request, apologising first and offering the fix second, is exactly how I'd want it done." |
| "Things have been slipping." | A mood. Nobody can fix a mood. | "The last two deliveries arrived after the date we agreed. Let's talk about what happened on each." |
Look at the last column of this specific feedback table. Each line names a thing. Each one could be answered with "actually, here's what happened". That's what you're after.
Say what you saw, then what it cost
A good shape for the sentence is simple. What I saw. What I took from it. What I'd like instead.
"I saw you gave three timelines in one call. I think the client left unsure which one to plan around. Next time, can we agree one date before the call?"
Notice the middle part. You say what you took from it, and you say it as your read, not as a fact. That matters enough that it gets its own post: observation versus interpretation in feedback. For now, just keep the two apart. What happened is one thing. What you concluded is another.
And always finish with what you'd like instead. Otherwise you've described a problem and handed it over without a direction. They'll fix something. It may not be what you meant.
Free assessmentHow trapped are you, really?Take the Corporate Suffocation Index, the free solopreneur readiness assessment.Take the assessment →Praise has to be specific too
This is where solo operators get lazy. You do the hard feedback carefully and then toss out "good work" when something goes right.
Don't. Positive feedback is not a softener to make the criticism go down easier. It is information of exactly the same kind. People often don't know which part of their work you value most. If you say "great job", they'll guess which part you meant, and they may guess wrong and polish the wrong thing for months.
So apply the same test. Name the moment. Describe what they did. Say why it mattered.
There's a second benefit. When specific recognition is normal, feedback stops meaning "something is wrong". A conversation that only ever means trouble becomes something people dread. Mix in the good and the invitation stops being a threat.
Prepare in two minutes, not two hours
You're running a business on limited hours. You can't afford a rehearsal for every comment. You don't need one.
Before you speak, ask yourself four quick things:
- What exactly did I see? If you can't point at it, wait until you can.
- Is it recent enough that we both remember? If not, say less and ask more.
- Which part is fact and which part is my guess? Keep them apart in your head before you do it aloud.
- What is one thing that is going well, specifically? Not to soften. Because it's true and they should know.
That's the preparation. Two minutes with a notebook, or on a walk.
Then ask before you tell. "How do you think that call went?" Often they'll name the problem themselves, which is easier for them to hear and more likely to stick. And if their answer differs from yours, that gap is the most useful thing in the room. It deserves more of your attention than the original point. Where this sits inside a full conversation is covered in how to have a performance conversation.
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 to do on Monday
Pick one thing you've been meaning to say. Not the biggest. Just one that's been sitting there.
- Find the actual moment. The email, the call, the file.
- Write it as one sentence: what you saw, what you took from it, what you'd like instead.
- Check it against the disagreement test. Could they dispute it with a fact? If not, sharpen it.
- Say it today, or tomorrow at the latest.
Then write two lines down afterwards: what you said, and what was agreed. Not surveillance. Memory. Without it you'll each remember a different conversation, and there'll be nothing to build on when you come back to it. The follow-through is its own skill, and how to follow up on feedback covers it.
If you only change one habit, change this one. Replace every adjective about the person with a sentence about a moment.
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 specific and harsh feedback?
Harsh is about tone and character. Specific is about a moment. You can be very specific and very calm: here is what happened, here is what I took from it. Vague feedback is often the harsher kind, because it leaves the person guessing how bad it is.
How soon after something happens should I say it?
As soon as you both still remember it clearly. Close to the event, it is a small observation about a thing. Months later it becomes a judgment about a pattern, and it carries the weight of everything you did not say in between.
What if I only have a general feeling and no example?
Then you are not ready to give specific feedback. Wait and watch for a concrete instance, or ask a question that helps you find one. A feeling you cannot point at gives them nothing to act on and nothing to answer.
Should I give praise as specifically as criticism?
Yes. Recognition is information, not a cushion. People often do not know which part of their work you value most, and without being told they may improve the wrong thing.
The full method for specific feedback, 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.