Mirorly

Constructive criticism examples, rewritten to land

Most feedback examples are canned lines nobody would say — and the generic kind often backfires. Real manager moments: the verdict, and the rewrite that lands.

By the Mirorly editors7 min read
On this page
  1. The move every rewrite makes
  2. The work itself
  3. Communication
  4. Reliability and ownership
  5. Collaboration and attitude
  6. What all of these share
  7. The mirror: when did someone last give you one?
  8. Common questions
  9. The one-line summary

Search "constructive criticism examples" and you get lists of fifty canned lines — "I appreciate your effort, but…" — that nobody would actually say out loud and that land as hollow when they do. Worse, a lot of the generic advice hands you exactly the kind of feedback that backfires. The classic meta-analysis by Kluger and DeNisi found that feedback improves performance on average — but in more than a third of cases it actually made performance worse, and the dividing line was where the feedback pointed: at the task and the behavior, it helped; at the person, it hurt.

So this isn't a list of phrases to memorize. It's a set of real manager moments, each shown twice — the version that points at the person (the verdict) and the version that points at the behavior and the next attempt (the rewrite). Once you see the move a few times, you can run it on any moment you face, because it's always the same move.

The move every rewrite makes

Before the examples, the pattern underneath all of them. Every rewrite below does these three things, in this order:

  1. Name the behavior and the moment, not the trait

    "You're careless" is an unfalsifiable verdict. "The last two PRs missed edge-case tests" is a fact the person can recognize and act on.
  2. State the concrete impact

    What it actually cost — so it reads as information, not nitpicking. Skip this and it sounds like you're just finding fault.
  3. Point at the next attempt

    Hand over something to do differently next time, not a judgment on the attempt that's already over. A verdict invites defense; a fix invites action.

If a rewrite ever feels flat, it's usually because one of the three is missing. Now the moments.

The work itself

When the work keeps needing rework.

The verdict

"You're careless — I keep having to send things back."

The rewrite

"The last two PRs each came back for missing edge-case tests. Going forward, can we make 'edge cases checked' the final step before you mark it ready? I'd rather it take twenty more minutes than bounce."

When something falls below the bar.

The verdict

"This isn't good enough — I know you can do better."

The rewrite

"The deck buried the recommendation on slide 14, and the exec team decides in the first two minutes. Next time, open with the ask and the number, then the supporting detail behind it."

Communication

When their direction isn't landing.

The verdict

"You need to communicate better."

The rewrite

"Twice this month the team built against the wrong priority after your kickoff. Try ending each one with a single line: 'the one thing that has to be true by Friday is X.'"

When someone dominates the room.

The verdict

"You talk too much and people tune out."

The rewrite

"In Tuesday's planning the two newer folks didn't get a word in before we ran out of time. Want to try going round-robin on the big calls, so we hear them first?"

Reliability and ownership

When deadlines keep slipping.

The verdict

"You're unreliable — things keep slipping."

The rewrite

"The last two sprints slipped, and I didn't hear about it until the day of. I can work with a slip; I can't work with a surprise. Flag it the moment it starts to wobble, even half-formed."

When someone over-promises upward.

The verdict

"Stop saying yes to everything."

The rewrite

"You committed us to the Q3 date in the review before we'd scoped it, and the team absorbed the overtime. Next time, buy a day — 'let me confirm the timeline and come back tomorrow' — before you lock it in."

Collaboration and attitude

When someone gets defensive about feedback.

The verdict

"You get defensive every time anyone gives you feedback."

The rewrite

"In the retro, when Sam raised the handoff issue, the conversation moved to why it wasn't your fault before we'd looked at the fix. Try holding the 'what would make this better next time' question open for a beat before you respond."

When a manager you manage won't let go.

The verdict

"You micromanage your team."

The rewrite

"A couple of your reports mentioned they run most decisions past you before moving — which usually means they don't feel real ownership. Pick one call this week you'd normally make, and hand it over fully: the outcome and the authority to decide how."

When someone shoots down every idea.

The verdict

"You're too negative — you shoot everything down."

The rewrite

"In the last two brainstorms, the first thing said to each new idea was why it wouldn't work, and people stopped floating them. Try holding the objection for one round — let ideas get fully on the table before we pressure-test them."

Notice these last two are about a pattern, not a single slip. When something has happened three times across different contexts, name it as a pattern and say so — "I've seen this in a few places now" — so the person hears a trend worth changing, not a one-off they can wave away. A single instance is an incident; the same thing in three rooms is the thing to actually work on.

What all of these share

Read the rewrites back to back and the same three moves show up every time: a specific behavior in a specific moment, its concrete impact, and a fix pointed at the next attempt. None of them says a word about the person's character — and that's not politeness, it's what makes them work. People defend against "you're X" because it's an identity claim they have to dispute; they can engage with "in Tuesday's meeting, this happened" because it's a fact about a moment, not a verdict about who they are. The wording isn't the whole job — a flawless rewrite still lands badly coming from someone the person doesn't trust to be on their side — but it's the half you can control on the way into the conversation, and getting it right keeps the harder half from being wasted.

It's also why no wrapper rescues a bad note. The feedback sandwich tries to soften the verdict; the fix isn't a softer verdict, it's no verdict. And which relationship the feedback travels through changes the shaping — down to a report runs on restraint, sideways to a peer runs on a shared goal — but the core move, behavior over character, forward over verdict, holds across all of them. The rest of the pillar goes deeper on each case.

The mirror: when did someone last give you one?

You've just read a page of examples of how to give other people constructive criticism. Here's the uncomfortable question: when did anyone last give you a straight one? The better you get at giving feedback, the more your team experiences you as the person who evaluates — which is exactly the dynamic that makes them hold back what they see in you.

That's the gap Mirorly is built to close. It's the 360 feedback round you run on yourself first — you answer a set of behavioral questions about how you actually work, send the same ones to the people around you, and read your self-view side by side with theirs. Same discipline as the rewrites above — anchored to behavior, not character — turned back on you. The core leadership behaviors template is where most managers start.

Common questions

The one-line summary

Useful constructive criticism isn't a canned phrase — it's a real moment where you swap the verdict about the person for the specific behavior, its concrete impact, and a fix pointed at the next attempt. Run that move on the moments you actually face, and skip the wrappers: research shows the feedback that points at the person, not the task, is the kind that makes things worse.