Why nobody tells you what they actually mean

Someone tells you your presentation was “interesting.” A colleague says a project “went fine.” Your manager mentions the client feedback was “mostly positive.” Every one of these sentences is doing the same thing: carrying real information wrapped in enough padding that you can’t quite act on it.

This isn’t dishonesty. Most people softening feedback aren’t trying to mislead anyone. They’re managing the discomfort of saying something that might land badly, and the easiest way to do that is to sand the edges off until the message barely resembles what they actually think. The problem is what gets lost in the sanding. “Interesting” could mean genuinely interesting, or it could mean confusing, too long, or a polite way of saying nothing landed. You have no way to tell which, so you either ask a follow-up question that puts the other person on the spot, or you guess, and often guess wrong.

The cost of this compounds quietly. A designer hears “let’s revisit this” three times before realising the direction was wrong from the start. A report gets called “solid” right up until it’s quietly rewritten by someone else. Nobody lied. Everybody was just protecting the moment at the expense of the outcome, and the person who needed the real information paid for it later, usually with more work than a direct conversation would have cost.

Three signs feedback has been softened past usefulness

The first is a vague positive with no specific reference point. “Great work” tells you nothing about which part was great or why. Useful feedback names the thing: the opening was clear, the data slide was hard to follow, the tone in paragraph two felt off. If you can’t tell what specifically prompted the comment, it’s been smoothed down to almost nothing.

The second is a conditional buried in passive language. “It could maybe use a bit more clarity in places” is doing a lot of work to avoid saying “I didn’t understand the middle section.” The passive voice and the hedging words (maybe, a bit, in places) are usually there to soften a much more direct point underneath.

The third is timing that doesn’t match the stakes. If something is genuinely fine, feedback usually comes quickly and briefly. If someone takes a long pause, rereads what they wrote, or schedules a call for something that could have been a two-line message, the delay itself is often the real signal. People are more careful with their words when the actual content is harder to say.

What to do about it

Asking “no, but what did you really think” rarely works. It puts the other person on the spot and most will just repeat a slightly firmer version of the same vague comment. A better approach is to ask for something specific instead of something general: not “what did you think” but “what would you change about the opening” or “which part took the longest to get through.” Specific questions are much harder to answer with a soft non-answer, because they require pointing at an actual thing.

If you’re the one giving feedback and notice yourself reaching for a vague positive, it’s worth pausing on what you’d actually change if it were your work. That’s usually the real feedback, and it’s almost always more useful to the other person than a comfortable generality, even when it takes a moment longer to say clearly.

This is the exact gap we’re building Plainspeak to close: taking a real situation, working out what you’re actually trying to say, and helping you say it in a way that’s honest without being harsh. It’s still early, but if the problem above sounds familiar, it’s worth keeping an eye on.