Constructive Feedback Examples (and How to Keep Them Specific)

Good constructive feedback follows one pattern: Situation to Behavior to Impact to next step. Name when it happened, describe the behavior (not the person), state the impact it had, and agree on what to do next. "You're disorganized" is a judgment; "In Tuesday's review the deck wasn't ready, so we lost 15 minutes. Let's lock the draft a day ahead" is feedback someone can act on. Copyable examples by scenario, both constructive and positive, are below. The reason feedback drifts into vague character judgments is simple: you're recalling an impression instead of referencing a specific moment you logged.

The SBI pattern, in one block

Every example on this page is built from the same four lines. Copy the skeleton, then fill each line with something observable. If you can't name the situation and the behavior, you don't have feedback yet, you have a feeling, and that's the signal to go capture the next moment instead of guessing.

SITUATION: when/where it happened
BEHAVIOR:  what they specifically did (observable)
IMPACT:    the effect it had
NEXT STEP: what to do differently / keep doing

Constructive feedback examples (by scenario)

These are written the way you'd actually say them out loud. Each one names a moment, sticks to behavior, makes the impact concrete, and ends with a single next step the person can take. Copy the block, swap in your real dates and details, and you have a script that won't slide into "you need to be more organized."

Missed or slipped deadline

"The API doc slipped past Friday, and it wasn't flagged until Monday, so the frontend team sat blocked over the weekend. Going forward, flag a slip the day you see it. Can we set a Wednesday checkpoint?"

Dominating meetings

"In the last two planning calls you answered before others could, and a couple of the quieter folks stopped contributing. Try asking 'what does everyone else think?' before you share your take."

Quality slipping

"The last two PRs had test gaps we caught in review, which added a review cycle each. Let's add a self-review checklist before you request review, so the second pass is the polish, not the catch."

Vague or status-only updates

"Your last few standup updates were 'still working on it,' so I couldn't tell what was actually blocked. Next time, name the specific thing you're stuck on and what you need. I'd rather unblock you on Tuesday than find out Friday."

Over-committing

"You said yes to three new asks this sprint on top of the migration, and two of them slipped. It's not effort, it's load. Let's protect the migration and push the smaller asks to next sprint."

Defensive in code or design review

"In Thursday's review, the first response to each comment was a reason it was fine, and a couple of people stopped leaving notes. Try reading the whole thread before replying, and treat the comments as questions first. The feedback got quieter, and that's the part I want back."

Notice what's missing from all six: the words "always," "never," "lazy," "careless," and "attitude." Constructive feedback describes a specific, observable thing on a specific day. The moment you reach for a character word, you've left the evidence behind.

MISSED DEADLINE
"The API doc slipped past Friday, and it wasn't flagged until
Monday, so the frontend team sat blocked over the weekend. Going
forward, flag a slip the day you see it. Can we set a Wednesday
checkpoint?"

DOMINATING MEETINGS
"In the last two planning calls you answered before others could,
and a couple of the quieter folks stopped contributing. Try asking
'what does everyone else think?' before you share your take."

QUALITY SLIPPING
"The last two PRs had test gaps we caught in review, which added a
review cycle each. Let's add a self-review checklist before you
request review."

VAGUE UPDATES
"Your last few standup updates were 'still working on it,' so I
couldn't tell what was blocked. Next time, name the specific thing
you're stuck on and what you need."

OVER-COMMITTING
"You said yes to three new asks this sprint on top of the migration,
and two of them slipped. Let's protect the migration and push the
smaller asks to next sprint."

DEFENSIVE IN REVIEW
"In Thursday's review, the first response to each comment was a
reason it was fine, and a couple of people stopped leaving notes.
Try reading the whole thread before replying."

Positive feedback examples (these matter just as much)

The same rule applies to praise: specific beats glowing. "Great job" tells someone you noticed; "your incident write-up Thursday was the clearest I've seen" tells them what to do more of. Positive feedback you can repeat is positive feedback that actually shapes behavior.

Recognizing strong work

"Your incident write-up Thursday was the clearest I've seen. It's now the template the team uses for retros."

Recognizing initiative

"You unblocked the design team this sprint without being asked. That initiative is exactly the next-level behavior we talked about, keep doing it."

Recognizing growth

"Three months ago estimates ran long; your last three projects all landed on the date you committed. That's a real change, and I noticed."

Recognizing how someone shows up

"In yesterday's planning you pulled the two quietest people into the conversation. The plan we landed on was better for it. That's leadership, and I want to call it out."

STRONG WORK
"Your incident write-up Thursday was the clearest I've seen. It's
now the template the team uses for retros."

INITIATIVE
"You unblocked the design team this sprint without being asked.
That initiative is exactly the next-level behavior we talked about."

GROWTH OVER TIME
"Three months ago estimates ran long; your last three projects all
landed on the date you committed. That's a real change, and I
noticed."

HOW THEY SHOW UP
"In yesterday's planning you pulled the two quietest people into the
conversation. The plan we landed on was better for it."

Why feedback drifts into vague judgments

Almost nobody sets out to give character feedback. It happens because of how memory works. By the time you sit down to give feedback, the specific Tuesday is gone and what's left is a residue: "kind of unreliable lately." That residue is an impression, not evidence, and it's the raw material of every unfair review.

Here is where the usual ways of giving feedback quietly fail:

• Character, not behavior. "You're careless" can't be acted on and feels like an attack. "The last two PRs had test gaps" can be fixed by Friday.
• No specific moment. Without a date and a situation, the person can argue the premise, and they're often right to. You're describing a feeling.
• The feedback-sandwich mush. Burying the real point between two compliments blurs all three. People hear the bread and miss the filling.
• Only at review time. Saving feedback for a twice-a-year form means every point is months stale, and the person can't course-correct in the meantime.
• No next step. Feedback that ends at "the impact was bad" leaves the person knowing they're in trouble but not what to do about it.

Every one of these has the same root cause: you're working from recall instead of a record. The fix isn't a better script. It's having the specific moment written down so you can read it back.

How a per-person memory keeps feedback specific and fair

Specific feedback needs a specific moment you actually logged. The practical version of that is simple: drop a quick note under the person when you see the behavior, good or bad, the same day. When it's time to give feedback, you're referencing a dated entry, not the last thing you happened to remember. That's what keeps feedback specific and fair, because you're pulling from the whole period instead of the loudest recent moment.

This is what Notivo is for. Write one line and tag the person with @, and it files itself into that person's timeline. Add a #topic and it also lands under that theme across everyone. When the feedback conversation or the review comes, you type the person's name and read the moments back in order, with dates attached. Your notes are private by default, scoped to your account, and stored on secured infrastructure.

• Capture in seconds. One line on the web the moment you notice the behavior, while the situation is still exact.
• Filed by person. @-tag the name and the note joins that person's timeline. No folders, no doc to remember to open.
• Grouped by theme. #-tag the behavior (#delivery, #communication) and you can pull every related moment at once.
• Read it back, dated. Search a name and the specific Tuesdays are right there, so feedback cites a moment instead of a mood.

The honest version: this is platform-level security and private-by-default storage, not end-to-end or zero-knowledge, and we won't pretend otherwise. What it gives you is the thing that makes feedback fair: a record you can read, instead of a memory you have to trust.

Frequently asked questions

Keep going

Feedback, reviews, and the notes behind them are one connected habit. Next reads:

• Performance review template and examples, for turning these moments into a written review.
• Recency bias in performance reviews, on why the whole year should count, not just the last six weeks.
• The 1:1 meeting notes template, where most of these moments get captured in the first place.
• Performance review prep with Notivo, the workflow that turns logged moments into a finished review.
• Notivo for managers, the per-person memory behind fair, specific feedback.