Why Giving Feedback (With No Ask) Confuses Everyone!
Let me ask you something. When was the last time someone said something like this to you: “The presentation was good – but slide 4 felt a bit rushed?”
And then just… stopped.
No request. No demand. No, “so please redo it.” Just the observation, hanging in the air.
What did you do?
If you’re like most people, you probably scrambled for words.
You said something like “Oh, I’ll fix that!” or “Sorry about that – want me to redo it?” or you went quiet and felt vaguely guilty for the rest of the day.
Here’s the thing.
The person giving you that feedback didn’t ask for any of those responses.
They were just… talking.
And that, right there, is one of the most underrated confusions in human communication.
The Vada That Started This
My wife and I recently took a short break at a lovely resort (some of you read about that!). At breakfast, the F&B manager – a genuinely warm chap – came over and asked if everything was all right.
I said, “The vada this morning wasn’t quite as crispy as yesterday’s.”
Suddenly there was a scramble – almost like a rugby scrummage!
He immediately called the chef over. The chef offered to make me a fresh one on the spot.
I said, “No, no – it’s fine. I just wanted to mention it.”
Both of them looked genuinely puzzled.
You could almost see the thought bubble: How can something be wrong – but you don’t want it fixed?
I found it fascinating.
Because I wasn’t complaining. I was simply offering information – because they’d asked and because I thought it might help.
But their system had no category for that.
And I mean that quite literally.
The Script That Got Broken
Here’s something most guests never think about. Hospitality staff are trained to follow a structured service recovery process.
One popular framework used widely in the industry is called LEARN – Listen, Empathise, Apologise, Resolve, Notify.
It’s a well-designed sequence: Something goes wrong, the guest raises it, staff listen and empathise, apologise sincerely, resolve the issue (replacement, refund, upgrade), and then notify the team so it doesn’t happen again.
Clean. Logical. Effective.
Except I had skipped straight past “Resolve.”
I didn’t want a resolution. I had no complaint. I was offering pure information – and in doing so, I had quietly dismantled the entire sequence.
The manager and the chef were standing there with a perfectly loaded script and nowhere to go with it. That’s why they looked confused.
It wasn’t rudeness. It wasn’t incompetence. It was a script designed for complaints – encountering something that wasn’t one.
Feedback vs. Complaint – They’re Not the Same Thing
Here’s the distinction that most of us blur without realising it.
- Feedback is informational – You’re sharing what you noticed. There’s no ask attached. You’re not looking for resolution – you’re contributing to improvement. The information is the gift.
- A complaint is transactional – Something went wrong, and you want something done about it – a replacement, a refund, an apology, or a correction. The complaint comes with an implicit or explicit demand. It’s a request dressed as an observation.
The confusion arises because most human systems – service teams, managers, partners, and parents – are only trained to handle complaints.
Feedback with no demand attached genuinely doesn’t compute – it breaks the script.
And this isn’t just a hospitality problem.
It Happens Everywhere…
Think about a classroom:
A student stays back after a lecture and tells the professor, “The way you explained that concept today was the clearest I’ve ever heard it.”
No ask. Just feedback.
Most professors either deflect immediately (“Oh, I’m sure you would have figured it out anyway”) or over-explain their teaching methodology in response.
Because receiving a purely positive observation – with no question, no complaint, and no request attached – is surprisingly awkward for most people.
Now flip it. A student says, “I found the second half of the lecture a little hard to follow.”
Same situation. No ask. Just an observation. The professor’s immediate instinct? Apologise, justify, or offer to re-explain it right there in the corridor.
Because the brain reads “something was wrong” as “something must be done.”
The workplace is no different:
An employee tells their manager, “I think our client reports could be a bit clearer – clients often seem confused by them.”
No ask for a promotion. No request to lead a project. Just an observation.
Most managers either over-react (“Right, let’s overhaul the entire reporting format!”) or under-react (“Hmm, yes, thanks“) – because feedback without a demand creates a kind of decision paralysis.
You’ve been given something. You feel obligated to do something with it.
But there’s no obvious next step.
What the Research Says
Economist Albert Hirschman laid this out beautifully in his 1970 book Exit, Voice, and Loyalty (Harvard University Press).
His argument: when people are unhappy with something – a product, a workplace, a relationship – they have three choices.
- They can Exit – leave, resign, stop buying, or walk away.
- They can use Voice – speak up, say something, and try to change it.
- Or they can choose Loyalty – stay silent and hope for the better.
Most organisations are built to handle Exit – it’s measurable, visible, and hard to ignore.
Voice, on the other hand, is uncomfortable, ambiguous, and requires you to do something with it that isn’t obvious.
Later researchers built on this with the concept of Voice Behaviour – specifically promotive voice: speaking up not to demand, but to improve.
Sharing information because you care enough to, not because you need something back. It’s actually the most constructive form of human communication.
And it’s the rarest.
Because giving it well is hard – and receiving it gracefully is even harder.
Why We Struggle to Receive It
Here’s the behavioural science bit. When someone tells us something is wrong – even without an ask – our brains immediately trigger a reciprocity response.
We feel obligated to act because we’ve been given something (information). Receiving without acting creates cognitive discomfort.
Add to that the fact that most of us are conditioned, from childhood, to see feedback as a precursor to criticism.
So we go into defensive mode before we’ve even processed what was said.
The result? We either over-correct (“I’ll fix everything immediately!”) or we deflect (“Oh, it wasn’t that bad, was it?”).
Neither of which is what the feedback-giver wanted or needed.
What To Do Instead
Whether you’re on the giving end or the receiving end, two simple shifts make all the difference.
- When you’re giving feedback with no ask – say so explicitly. “I’m not looking for any action here – I just wanted to share this.” Those two sentences remove an enormous amount of confusion and discomfort for the other person. You disengage the reciprocity trigger before it fires.
- When you’re receiving feedback with no obvious ask, resist the urge to scramble. Simply say, “Thank you – I’ll note that.” That’s it. You don’t owe a fix. You owe acknowledgement.
A calm “thank you, noted” is one of the most underused phrases in leadership, service, and relationships.
And if you’re running a service team? It might be worth building a fourth option into your LEARN training – one that simply says: Sometimes, the guest just wants to be heard.
No resolution required.
Well, now you know it too!
(Over to You… I’m genuinely curious about this one – do you find it easy to give feedback with no complaint attached? Or does it always come with an implicit ask? And on the flip side, when someone gives you pure feedback with no demand, no ask – what do you actually do with it? Share your story in the comments. I’d love to hear whether the “vada confusion” is just me – or whether it’s all of us!!)
Select References/Sources:
- Albert O. Hirschman, Exit, Voice, and Loyalty (Harvard University Press, 1970).
- Voice Behaviour research: Liang, Farh & Farh, Academy of Management Journal (2012).
- Elizabeth Morrison, NYU Stern – organisational voice behaviour research.
- LEARN service recovery framework – widely attributed to hospitality industry training, origins in customer service literature from the 1990s.
