Quick test. Have you said any of these in the last month?
- “No rush on this” (when there was, in fact, a rush).
- “This is great, just a few small tweaks” (when it needed significant rework).
- “Maybe we could think about possibly trying…” (when you’d already decided).
- “Don’t worry about it” (when you were, in fact, worried about it).
If you’re nodding along, I want to gently challenge something you probably believe about yourself – that this is you being a kind, supportive manager.
It isn’t. It’s you being unclear. And there’s a real cost to it that lands on the very people you think you’re protecting and trying to lead.
The honest truth is that your team would rather have clarity than comfort. Every time you soften a deadline, hedge a piece of feedback, or wrap a “no” in three layers of “maybe”, you’re not sparing their feelings. You’re transferring the burden of working out what you actually meant onto them.
I learned this one the hard way.
Let’s dig into why we do this, what unclear-dressed-as-kind actually looks like day to day, and how to be genuinely direct without turning into what you don’t want.
Why we confuse vagueness with kindness
Let’s be honest about what’s actually happening when we soften things, because it’s not really about the other person.
When you hedge feedback, you’re managing your discomfort, not theirs.
The awkwardness that you’re avoiding is your own. Delivering a clear “this isn’t good enough yet” or “I need this by Thursday, no flex” creates a moment of tension and most of us will do almost anything to avoid that moment – including sacrificing the clarity our team needs to do their jobs.
Psychologists sometimes call this the “mum effect” – people systematically avoid delivering unwelcome news and when they can’t avoid it, they distort it into something much softer. As managers we do it constantly and we tell ourselves a flattering story about it. We’re being “empathetic”. We’re “protecting morale”. We “don’t want to demotivate them”.
I used to do this a lot and call it “protecting my team”.
But look at it from your team member’s side. They can’t act on your intentions. They can only act on your words. If your words say “this is broadly fine” and your intentions say “this needs a rethink”, they will carry on doing the thing you didn’t want and then be blindsided when the truth eventually surfaces in a quarterly review or a missed promotion.
There’s a second layer to this too and it’s the one that stings a bit. Vagueness is also a way of keeping your options open. If you never clearly said the deadline was Thursday, you can’t be the bad boss when you’re frustrated on Friday. If you never clearly said the work wasn’t good enough, you never have to own the difficult conversation. Unclear managers get to feel kind and stay blameless.
And your best people notice. High performers, in particular, are pattern-matchers. When they realise your words don’t reliably map to your meaning, they stop trusting your words and start burning energy trying to work out what you really mean instead of doing the work.
What the kindness trap looks like day to day
Like most management problems, this one hides in small, well-intentioned moments. Here’s what to watch for in yourself.
The soft deadline
“Whenever you get a chance” or “no massive rush” – for something you actually need by Friday. You think you’re giving them breathing room. What you’re actually doing is running a test they don’t know they’re taking. When Friday comes and it’s not done, you’re quietly annoyed, they’re confused and the relationship takes a small hit as well.
The compliment sandwich with no filling
Feedback so wrapped in reassurance that the actual message never lands. You walk away having “given the feedback”. They walk away having heard “everything’s basically fine”. Three months later, you’re frustrated that “nothing’s changed” about a problem you never clearly named.
The phantom decision
You’ve already decided, but you present it as an open question because it feels more collaborative. “What do you think about maybe moving in this direction?” Your team debates it in good faith, someone argues against it and then the thing happens anyway.
The invisible standard
“I’ll know it when I see it.” You have a clear picture in your head of what good looks like, but describing it feels too prescriptive, so you let them guess. Then you give feedback on the gap between their guess and your unspoken picture – and call it a development opportunity.
Four ways to be clear without being cold
The fear underneath all of this is that directness equals harshness. It doesn’t. Clarity and kindness aren’t opposites – done properly, clarity is kindness. Here’s how you can do it.
1. Say the real deadline, then the real reason
Replace “no rush” with the truth plus context: “I need this by Thursday morning because I’m presenting it to the client Thursday afternoon. If that’s going to be tight, tell me today and we’ll work something out.”
Notice what this does. It’s completely clear, but it’s also more genuinely kind than “no rush” – because it gives them the information to succeed and an explicit escape route if they’re overloaded. Vague deadlines don’t protect people from pressure. They just make the pressure arrive as a surprise.
2. Separate the person from the work
Most feedback-hedging comes from worrying they’ll hear “your work isn’t good enough” as “you’re not good enough”. So don’t leave that to chance – say the distinction explicitly.
“You’re doing well here and this isn’t a concern about you. This specific piece isn’t where it needs to be yet, and here’s exactly what’s missing.”
Then give the specifics. One clear sentence of reassurance buys you the right to be completely direct about the work. That’s a much better trade than ten sentences of hedging that bury the message entirely.
3. If you’ve decided, say you’ve decided
Stop dressing decisions up as discussions. Be honest about which mode you’re in: “This one’s decided and I want to explain the thinking” versus “This is genuinely open and I want your input before I make the call.”
Your team can handle not being consulted on everything. What they can’t handle is not knowing which conversations are real. (This also does wonders for your meetings, but that’s a whole other topic on its own.)
4. Describe what good looks like before they start
If you have a picture in your head, get it out of your head. Before someone starts a significant piece of work, give them two or three concrete examples: “Good looks like X. The most common way this goes wrong is Y. If you’re unsure about Z, that’s the bit to check with me on.”
By the way, this isn’t micromanagement – far from it. This is setting expectations and providing clarity on what a good outcome looks like – not the exact steps of how to get there.
One way to get started with this is to block 20 minutes and do an honesty audit on yourself. Look back through your last few days of Slack messages, emails and one-to-one notes and find the places where what you wrote and what you meant don’t match. The “no rush” that had a rush. The “small tweaks” that weren’t small. The “great work” you didn’t fully mean.
Pick the one with the biggest gap and go close it. Not with an apology – just with the clear version: “I want to revisit something. When I said X, what I actually meant was Y and I should have said that at the time.”
It’ll feel uncomfortable for about ninety seconds. And then you’ll notice something: they’re not hurt. They’re relieved. Because now they finally know where they stand. They have clarity.
Being unclear isn’t kind. It moves the pain to later and makes it bigger. The kindest thing you can give your team is a manager whose words they can trust.
