Constructive criticism examples that actually work all share the same backbone, and it has less to do with tone than you'd think. What they share is a structure the other person can walk away and actually do something with. The clearest version is an 8-step framework from the Straight-Line method originated by American author and business coach Dusan Djukich. This framework for constructive criticism turns feedback from a vague complaint into a sequence you can follow, whether you're correcting a teammate or telling your boss something they don't want to hear. Here's the framework, with each step turned into an example you can copy.
-
Get clear on the outcome you want
Before you say a word, decide the specific change you're after, a concrete behavior going forward rather than a feeling you want them to feel. If you can't name what you'd want different next week, you're not ready for the conversation yet.
Example: the aim of this talk is a firm handoff time you can both count on, not an apology for the last one.
-
Deal in facts, not verdicts
This is where most criticism dies. "The report was three days late" is a fact. "It seems like you don't care about making deadlines" is a verdict wearing a fact's clothes. Lead with the second kind and the other person is defending their character before you've finished the sentence.
Example: say "the last two reports came in after the deadline," not "you've got a real problem with deadlines."
-
Name what's actually working
Acknowledge and strengthen workable behaviors. State what's genuinely good, plainly and specifically. This isn't a compliment stapled on to cushion the blow. It's an honest accounting and it only counts if it's true.
Example: "your analysis in this was the sharpest on the team, same as it usually is."
-
Name what isn't working, the same way
Acknowledge and deal with unworkable behaviors. Same directness, same plain voice, for the part that's a problem. No hedging, no softening it until it disappears.
Example: "the late handoff keeps stacking up on whoever's next in line and slowing the whole thing down."
-
Check they actually heard you
A nod is not agreement. Test for understanding. Ask them to tell you back what they took from it, so you find out whether it got through or bounced off.
Example: "walk me through how you're reading this," instead of "does that make sense?"
-
Close any gap
Clarify when necessary. If what they reflect back doesn't match what you meant, clear it up now, before you move on. A misunderstanding you paper over here becomes the reason nothing changes later.
Example: "that's close. The quality was never the question. The timing is what we need to fix."
-
Get a real agreement
Sounds like a small step, but nonetheless important. It is the visible, in-the-room action: did you get a specific yes to a specific next step, out loud? Not "sounds good". If nobody agreed to anything concrete, nothing actually got put in place. Big chance that in a few weeks you’ll have to give the feedback again.
Example: "so we're agreed, the next report is in my inbox by Thursday noon. Yes?"
-
Watch for commitment over compliance
This is the sharpest one. "I'll try to be better" is compliance. It costs nothing and changes nothing. Commitment has a specific behavior and a specific time attached, and you can tell which one you got by whether you'd actually be able to notice next week if it happened.
Example: "I'll send the draft by Thursday morning and flag it before end of Tuesday if I'm going to miss" is a commitment. "I'll do my best" is not.
What's a good example of giving constructive feedback?
“Before this, I got clear on what I actually want out of it: a handoff time we can both rely on. [outcome] So here’s where we are. The last report was due Tuesday and came in Thursday, and that’s the third time this quarter. [facts, not a verdict] Your analysis was the sharpest on the team once we had it, same as always. [what’s working] But the late handoff keeps stacking up on whoever’s next in line and slowing the whole thing down. [what isn’t] Walk me through how you’re seeing it. [checking they heard it] … Right, so the quality was never the question, the timing is what we fix. [closing the gap] Here’s what I’m asking, then. Next report in my inbox by Thursday noon. Are we agreed on that? [real agreement] And what do you need from me to make that realistic, so this is a plan and not just a yes to get out of the room?” [commitment over compliance]
Read it back and you’ll notice it never once diagnoses the person. Every line is either a fact, a specific ask, or a check that the two of you are actually on the same page. That’s the difference between feedback that changes something and feedback that just gets endured.
How do you give feedback to your boss?
The same eight steps apply, with one extra move first: get your account straight before you speak. Feedback to a boss gets waved off when it shows up as a feeling, like “I’m frustrated with how decisions get made.” It works when it’s one specific event, its real effect downstream, and a plain reason you’re bringing it up now.
Pin down one actual moment, when and where it happened. Not a pattern you’ve built up over months, one instance you can point to. Then what that moment actually caused downstream, the concrete effect, not what you assume it says about your boss. Then why you’re flagging it, without the theater.
Here’s what that sounds like:
“In the last two planning meetings, the scope changed after we’d already started building. [one event] The team’s started padding every estimate because nobody trusts the scope will hold, which is slowing delivery down. [the downstream effect, in facts] I wanted to raise it now, while it’s still cheap to fix, rather than after it costs us a deadline.” [why now]
That replaces “I’m frustrated with how decisions get made,” which invites a defense, with something a reasonable person can act on.
One more thing, since this is the conversation people avoid most. The reluctance itself is usually worth reading. When you catch yourself not raising something with your boss, it’s often less about whether the point is valid and more about a status gap you haven’t said out loud. Worth noticing before you talk yourself out of a fair point. Holding your ground with someone who outranks you is its own skill, covered in the article how to stand up for yourself without losing your cool, and it starts with having the account straight.
What if they get defensive?
Assume some people will hear even a clean, factual account as an attack, and plan for it instead of getting thrown off. A defensive reaction doesn’t mean you delivered it wrong. It means the structure matters more, not less. Stay on the facts, hold the specific ask, and don’t trade your account for their comfort.
Not everyone takes feedback the way it was meant, no matter how carefully you built it. Bosses included. They get defensive as easily as anyone. When it happens, the move is to set your own reaction aside for a second, stay on the facts, and keep the specific change on the table. “I hear that this is frustrating. The report was still three days late, and I still need it on time. What do you need to make that happen?” You’re not winning an argument. You’re refusing to let the agreement get renegotiated into nothing.
Part of this you can’t control. You can control whether what you handed them was a clean, factual account or a loaded verdict. Do that part right and a defensive reaction is theirs to manage, not proof you got it wrong.
Clear and harsh aren’t the same thing. Clarity hands the other person something to change. Harshness just hands them something to defend against. If you want the stance a person operates from when they give feedback this cleanly, that’s what Straight-Line Leadership by Dusan Djukich is actually about.
