Soft Feedback Is Kind to You and Expensive to Them

An engineer walks you through the design for a new billing service. Ten minutes in, you can see the problem. The retry logic sits in the wrong layer, and when the payment provider times out, the customer will get charged twice. Fixing it means rebuilding the middle of the design.

You say, “This is a really solid start. I’d think a little more about the failure cases. Let’s keep going.” They leave the room feeling good about the work. You leave feeling generous, which is what soft feedback feels like from the giving end.

Three weeks later they present the finished design to a wider group, and someone who has never tried to be kind to them asks what happens when the provider times out. The room goes quiet. The engineer spends the next week rebuilding what they spent the previous three weeks building, and a long time after that wondering why you did not say anything.

You did say something. You said it softly enough that it did not land, and the softness was for you.

Soft feedback is any message where the verdict is present in your head and absent from the sentence. It feels like kindness in the room because the room is where you are. The other person pays for it later, in weeks of work on the wrong thing, in a public correction they could have had in private, and in the slow discovery that your praise cannot be trusted. That bill goes to them, and you never see it.

The assumption: softening the message is the kind thing to do

Most managers I know believe hard news needs a cushion. The instinct is fear of one uncomfortable minute, and the explanation about protecting people gets written afterward. Nobody wants to be the manager who crushes people, so the verdict gets tucked between two compliments, “this will not work” becomes “I have a few thoughts,” and the actual problem gets demoted to a suggestion at the bottom of an email.

The instinct is aimed at the wrong person’s pain. When you soften a message, the discomfort you remove is your own. Saying “this design will double-charge customers” is unpleasant for the person saying it and useful for the person hearing it. Softening trades their information for your comfort, and it does the trade in a way that looks like generosity from where you sit. There are two things the word kind can mean here. One is the pleasant feeling in the room. The other is wanting the other person’s good enough to spend your own comfort on it. Softening delivers the first and skips the second, because the second costs a minute.

Brené Brown puts it in four words in Dare to Lead: clear is kind, unclear is unkind. I would add the clause she leaves implied. Unclear is unkind to them and pleasant for you, which is why it survives every resolution to stop.

I have written before about how nice leaders ruin people over the span of a career. This is about the same habit measured in weeks, at the scale of a single review, where you can still catch it.

The crack: they kept building the wrong thing

The first sign that your kindness did not land is that nothing changes. You said “think more about the failure cases,” and the next version has the same failure cases. You said “I’d tighten the scope,” and the scope came back the same size with a new coat of paint.

The tempting explanation is that they did not listen. Watch more closely and you will usually find they listened carefully. They heard “solid start” and believed it, because you meant them to. They heard “think a little more about” and filed it as a polish item, because that is what “a little more” means in English. They went and did what you said. What you said was not what you meant. An engineer who hears a vague review can ask whether it was a blocker, and the good ones learn to. That does not move the debt. You had the verdict, they did not, and asking is a workaround for a sentence you owed them.

This is where the cost compounds. Every day between your soft comment and the real correction is a day they spend building on a foundation you already knew was cracked, working hard and in good faith on the thing you told them was solid. When the correction finally arrives, they are handed a bill for a test that was never on the page, and the person who wrote the test is the one who told them they were passing.

What they heard is not what you said

Psychologists have a name for the gap. Thomas Gilovich, Kenneth Savitsky, and Victoria Medvec called it the illusion of transparency: people believe their internal states leak out far more than they do. You know how worried you are about the retry logic, so “think about the failure cases” feels heavy with that worry when it leaves your mouth. To the listener, it is seven neutral words.

The speaker walks out believing the warning was delivered, and the listener walks out believing the work was approved. Both are being honest, and one of them is about to lose three weeks.

A second gap opens later. Belief is what happens while the relationship is new, and discounting is what the team learns once the pattern is clear, and the information fails to arrive either way. People adjust what they hear for who is saying it. If you have a habit of softening, your team has already learned to discount you, and “a few thoughts” from you carries less weight than “a few thoughts” from someone who says what they mean. Your soft feedback lands even softer than you intended, because they have calibrated to you. Then comes the day you mean “this is fine,” and it sounds the same as every other time, and they cannot tell the difference. You have spent your ability to reassure them. The hours are the visible cost, and they can be made up. A team that has no way to know the truth about its own work, because the one person positioned to tell them speaks in one register no matter what they see, has lost something a refund of three weeks would not restore.

The revelation: soft feedback is comfortable for one person

Stop asking whether the feedback was gentle enough, and start asking who the gentleness was for.

aletheia, the Greek word for truth, carries the whole argument. It means un-hiddenness, the state of something pulled out of concealment into the open. It is built from a- (not) and lethe (concealment, forgetting), the same root as the river the dead drank from to forget. Truth, in this picture, is something you do to information: you bring it out. Whatever you do not bring out stays in the fog, and the fog does not clear on its own. Someone eventually walks through it and finds the wall.

Soft feedback keeps the truth in the fog. You know the design double-charges customers, and the engineer does not. Between those two facts sits a decision you made, which was to keep the knowledge on your side of the table, where it costs you nothing and costs them everything.

Seneca opened his letters to Lucilius with a complaint about time. People guard their money and hand out their hours to anyone who asks, he wrote, because time does not look like anything. Nobody sends an invoice for it. When you soften a verdict, you are spending someone else’s hours, and there is no invoice for that either. Three weeks of an engineer’s work disappears, and it never shows up as a cost on your side of the ledger. It shows up as a hard month on theirs.

Plutarch, writing about how to tell a flatterer from a friend, put the damage in the same place. The harm the flatterer does is that the friend finds out too late to fix anything.

So the revelation is arithmetic. Softening saves you one uncomfortable minute. It costs them the days between that minute and the moment the truth arrives from somewhere less kind. Multiply that across every review and every draft you called a great start, and you get a team that is chronically late and cannot work out why, reporting to a manager everybody likes.

The application: say the verdict first

Once you see who pays, the fix is mechanical.

1. Lead with the verdict. The first sentence carries the conclusion: “This design will double-charge customers when the provider times out, and the retry logic has to move.” Then the reason, then what to do next. Compliments, if they are true, come after, where they cannot be mistaken for the message.

2. Run the surprise test. Before you close a review, ask yourself one question. If this person gets a hard no from someone else in three weeks, will they be surprised? If the answer is yes, you have not told them. Whatever you said did not count.

3. Name the size. “Small” and “big” are the two most useful words in feedback and the two most often left out. “This is a big one, it changes the middle of the design” gives them a budget. “This is small, ten minutes” gives them a different one. Leave the size out and they will guess small, because you sounded calm.

4. Write it down the same day. The illusion of transparency lives in spoken feedback. A written sentence with the verdict in it survives the walk back to the desk, and it is the sentence that will be repeated when you are not in the room.

5. Check what they heard. “Tell me what you’re going to change” costs thirty seconds and catches the gap while it is still free.

You control whether the verdict, the reason, and the size were in the sentence. You do not control how it feels to hear it, and how it feels was never the test of whether you did your job. A face that falls means the sentence arrived. The other way to fail the person is contempt, and a verdict delivered with scorn or a sigh teaches them about you instead of about the work. The target is the plain verdict with the reason attached, without a cushion and without an edge.

I learned the shape of this from working with agents all day. When Claude hands me a design and the retry logic is in the wrong layer, I do not type “solid start, think about the failure cases.” I type: the retry logic is in the wrong layer, move it to the payment client, here is why. The fix comes back in a minute. Vague feedback to a model wastes my own afternoon, so I stopped giving it within a week of starting. It took me far longer to notice I was still giving it to people, and that with people, the afternoon I was wasting belonged to someone else. The model made the cost visible by billing me directly, and people are polite enough to eat it.

The test: who paid for your last soft review?

• Think of the last time you softened a verdict. How many days passed before the person learned what you meant, and who told them?
• When did someone last leave your review believing the work was approved while you believed it was not?
• Which draft on your team right now is being built on a “great start” you did not mean?
• If your team heard you say “this is fine” tomorrow, would they believe it?
• Whose time did your last cushion save, and whose did it cost?

The challenge for this week: for your next five reviews, write the verdict sentence before you walk in, say it first, and end with “tell me what you’re going to change.” Count how many times what they say back matches what you meant. Every miss you catch in that thirty seconds is work they would otherwise have done on the wrong thing.

Final Thoughts

The comfortable version of feedback is comfortable for one person in the room, and that person already knows the answer. The rest of the room is about to pay for the fog with their time.

A manager who says the hard sentence first, with the reason and the size attached, spends one bad minute and saves the other person weeks. That is the whole trade. It looks harsh from inside the minute and, from three weeks out, like the kindest thing anyone did for them all quarter.

If you want to work with people who say the verdict first and give you the reason, MasteryLab is built for that.

FAQ

Why is vague feedback harmful?

Vague feedback fails because the listener decodes it as approval. When a reviewer says “solid start, think a little more about the failure cases,” the speaker believes a warning was delivered and the listener believes the work was accepted with a polish note. The listener then spends days or weeks building on a foundation the reviewer already knew was wrong, and finds out later, usually from someone less kind and in a bigger room. The harm is measured in the listener’s time, plus the loss of trust when they realize the reviewer knew all along.

Is soft feedback kind or unkind?

Soft feedback is comfortable for the person giving it and expensive for the person receiving it. Softening removes the speaker’s discomfort in the moment, which is why it feels like kindness from the speaker’s chair. The listener loses the information they needed, keeps working on the wrong thing, and pays for the softness later. Kindness in feedback means giving the other person the truth while it is still cheap for them to act on, even though the minute of saying it is unpleasant for you.

How do you give hard feedback without being cruel?

Lead with the verdict in one plain sentence, then the reason, then what to do next. Name the size of the problem so the person knows whether they are looking at ten minutes or a rebuild. Write the verdict down the same day, because spoken feedback is where the gap between what you meant and what they heard lives. Finish by asking them to tell you what they plan to change, which catches the misunderstanding while it is still free. Cruelty comes from contempt and tone, and a clear statement about the work with the reason attached is a form of respect.

What does aletheia mean, and what does it have to do with feedback?

aletheia is the ancient Greek word for truth, built from a- (not) and lethe (concealment or forgetting). It means un-hiddenness, the state of something being pulled out of concealment into the open. In feedback, aletheia is the act of bringing what you know about someone’s work out where they can use it. Soft feedback keeps that knowledge concealed on the speaker’s side of the table, where it costs the speaker nothing and costs the listener the time between the soft comment and the day the truth arrives from somewhere else.