How to Give Constructive Feedback (Without Softening It Into Mush)
Constructive feedback means telling someone the truth about their work in a way they can actually use, not softening it until the point disappears or avoiding it until it becomes a bigger problem. Most owners fail at this in one of two directions: they bury the real message under compliments so nothing changes, or they avoid the conversation entirely out of fear the person will quit or push back. The fix is being fully honest about what needs to change and fully open to how the other person receives it, at the same time, and saying it in specific, private, timely terms instead of vague ones.
Why most feedback doesn't actually change anything
Picture the standard version. You open with something nice. You slide in the real issue, wrapped in enough cushioning that it barely registers. You close with more nice. The person walks out feeling fine and does the exact same thing next week, because the actual message never landed. That's not kindness. It's a message sent in a language nobody can decode.
Ken Bogard, who wrote a whole book on this, puts it bluntly: "My gosh, grown human professional adults struggle to do this thing that is called open and honest. And I'm like, we got to change the course of where we're going." He's not talking about rare, difficult people. He's talking about the default setting most of us run on.
Feedback fails for one of two reasons. Either it's too soft to be useful, or it never gets said at all.
Avoiding the conversation is its own kind of dishonesty
Scott Hollrah, founder and CEO of Venn Technology, let a hard conversation with a team member drag on for years. When he finally had a first version of it, the meeting seemed to go fine, then the person dropped a piece of news at the very end that wrecked him for a month. Weeks later, still avoiding the follow-up conversation he knew he owed, he woke up early one morning with a thought he couldn't shake: "Scott, you are avoiding this situation because you're afraid that this person might leave. You need to act and damn the consequences." He finally had the real conversation. The person did leave, but having it brought him more peace than avoiding it ever had.
Here's what avoidance actually costs. The problem doesn't pause while you work up the nerve. It compounds. The gap between what you're thinking and what you're saying grows, the resentment grows with it, and by the time you finally say something, it comes out bigger and sharper than it needed to be, because you've been carrying it alone for a month.
Kelly Knight, president of EOS Worldwide, carries a line from her mentor Gino Wickman that cuts through the whole excuse: "Kelly, you owe people clarity, not what they want to hear." Withholding the truth to keep someone comfortable isn't generosity. It's a debt you're not paying.
Honest and open, at the same time
Bogard's framework has two parts, and the whole thing breaks if you only do one. Be 100% honest: say what you actually think, not a softened version aimed at avoiding discomfort. Be 100% open: listen without already building your rebuttal, actually willing to hear how it lands.
Most people default to one side. The conflict-avoider is open but not honest, they'll hear you out all day and never tell you what's really wrong. The bulldozer is honest but not open, they'll tell you exactly what's wrong and then argue with anything you say back. Neither one is actually communicating. Bogard's point is that the raw material for doing both at once is already in you: "The ingredients already exist. It's already in you. Every human being has some level of honesty and some level of openness. What's happening is we're actually dirtying up the ingredients we already have." Ego, fear, and the habit of managing how you're perceived are what get in the way, not a missing skill.
Disagreement isn't the problem. Treating it like one is.
A lot of avoided feedback starts with a mistaken belief: that disagreement itself is dangerous, a sign the relationship is cracking. Bogard reframes that directly: "Disagreement is okay. It's as prevalent as oxygen and we need to be way more accepting of it." If two people never disagree, one of them has stopped saying what they actually think.
Once you stop treating disagreement as a threat, you can also stop the reflex of labeling someone the second the conversation gets uncomfortable, the difficult one, the sensitive one, the problem. Ben has pointed to the economist Amartya Sen's line on this: when we label things, we lose the ability to have a conversation. A label ends the exchange before it starts. Specific, honest feedback about a specific situation keeps it open.
Borrow the authority so it isn't just you against them
One of Ben's more practical tools for the moment a hard conversation starts to feel personal: borrow someone else's authority instead of putting the whole weight on your own opinion. Point to a shared reference, a book you both read, a standard you both already agreed to, a mentor's name. His example: "Now you don't have to say 'I think this,' you can go 'remember that book we read together?' You just borrowed someone else's influence to have a hard conversation. And guess what? You're not the villain."
You're not hiding behind someone else's opinion here. You're separating the standard from your personal judgment of the person, which keeps the conversation focused on the gap between the work and the standard instead of turning into you versus them.
- 1Private and soonPublic reads as punishment. Waiting a month strips out what would have made it useful.
- 2Name the specific thing"You've been off lately" gives nothing to act on. A specific incident does.
- 3Say what you wantNot just what went wrong. A request beats a verdict.
- 4Then go fully openStop talking. Let them respond before you defend or explain further.
How to actually structure it
Say it in private, and say it soon. Public correction reads as punishment, not feedback, and it teaches everyone watching to hide their own mistakes better next time. Waiting a month to bring up something from week one strips out most of what would have made it useful.
Name the specific thing, not the pattern you've built up in your head. "You've been off lately" gives someone nothing to act on. "The last two client proposals went out without the pricing table" gives them something they can actually fix by Friday.
Say what you want, not just what went wrong. Bogard's honesty half of the equation includes naming what you actually want, not only what disappointed you. "I need the proposal reviewed before it goes out" is a request. "You keep missing things" is just a verdict.
Then go fully open. Once you've said the honest part, stop talking. Let them respond without cutting them off or already defending your position. You may be missing context. The point of the conversation isn't to win it.
What this actually protects
Lisa Cini ties the whole habit back to what it's really for: "Success is being able to have, more often than not, the hard conversations that help somebody, instead of the 'great job, honey, here's a trophy, you did fantastic.'" A team that only ever hears vague praise never actually gets better, and neither does the business underneath them.
The founders who avoid this the longest usually aren't avoiding conflict. They're avoiding the version of themselves who has to sit with someone's disappointment for a minute. That's uncomfortable. It's also a lot cheaper than carrying an unspoken problem for six more months, or losing someone who needed a clear ask and never got one.
How to start this week
- Write down the one conversation you've been avoiding. Not the vague version, the specific incident behind it.
- Turn the complaint into a request. Replace "they keep dropping the ball" with the exact thing you need instead.
- Book it in private, this week, not the next time it comes up naturally.
- Say the honest part first, in one or two sentences. Resist padding it.
- Then stop talking. Let them respond before you explain further or soften it.
- If it starts to feel personal, anchor it to a shared standard instead of your opinion of them.
What to actually do
Soft feedback and no feedback fail the same way
If the real message never lands, the delivery method doesn't matter. Nothing changes either way.
Avoidance is a debt, not a kindness
You owe people clarity, not what they want to hear. Withholding the truth to keep someone comfortable just delays the cost.
Honest and open have to happen together
Honest without open is bulldozing. Open without honest is people-pleasing. Neither one is actually communicating.
Disagreement isn't a threat
Treating disagreement as dangerous is what makes people stop telling you the truth in the first place.
Borrow a shared standard when it starts to feel personal
Anchor the conversation to an agreed-on reference point instead of your opinion of the person. It separates the work from the relationship.
Specific and private beats vague and public
Name the exact incident, ask for the exact thing you want, and have the conversation in private, soon.
From the podcast
Common questions
How do I give constructive feedback without it turning into a fight?
Why do I keep avoiding a hard conversation with an employee?
How do I tell someone their work isn't good enough?
What's the difference between honest feedback and being harsh?
How do I have a difficult conversation with an employee I like?
Should I give feedback in private or in front of the team?
Still rehearsing a conversation you haven't had yet?
This is the work Ben does with founder-operators every week: naming the conversation you're avoiding, and why, then working through how to actually say it. If there's someone on your team who needs to hear something from you, let's talk.
Work with Ben