But the Customer Asked For It.
Six words that kill more customer experiences than bad execution ever could.
I’ve sat in too many strategy meetings where this phrase ends the debate.
Someone suggests a change that doesn’t fit the vision.
The room goes quiet.
Then someone says it: “But the customer asked for it.”
Discussion over. Decision made.
Except that no decision was actually made.
Here’s what that sentence really means:
• We’re afraid to say no
• We don’t trust our own judgment
• We’d rather blame the customer later than own a choice now
The best CX leaders I know do something different.
They listen to customer requests, then ask:
“What problem are they really trying to solve?”
Because customers are brilliant at knowing their problems. They’re terrible at designing solutions.
When a customer asks for a specific change, they’re handing you a symptom.
Your job is to diagnose the disease.
Sometimes the answer is implementing what they asked for. Often, it’s implementing something completely different. Occasionally, it’s changing nothing at all.
All three require the same thing: the courage to choose.
“The customer asked for it” isn’t a strategy.
It’s abdication.
Real leadership is saying “I heard you, and here’s what we’re doing instead,” then explaining why.
That’s the hard part.
That’s also the only part that matters.
A fast gut-check when the room freezes
The moment someone says, “But the customer asked for it,” the meeting usually stalls.
Not because the idea isn’t good. Because no one wants to be the person who looks like they’re ignoring the customer.
You need a way to unstick the room without escalating it.
Use this quick diagnostic. Ask it out loud.
Who asked for this: A named customer. A clear segment. A real pattern. Not “we’ve been hearing.”
What were they trying to get done in that moment: Speed. Certainty. Control. Avoiding a mistake. Finishing something before a deadline.
What breaks if we do exactly what they asked: Cost. Consistency. Trust. The experience for the next thousand customers.
If the room can’t answer all three, you’re not making a customer-led decision.
You’re dodging responsibility.
I’ve watched these questions shift conversations instantly. People stop hiding behind the phrase and start talking about tradeoffs. That’s where real decisions live.
The script leaders actually need
Most leaders don’t lack conviction. They lack words.
They worry that pushing back will sound dismissive. Or arrogant. Or out of touch.
So they stay quiet.
Here’s a script you can use without sounding defensive or academic. Say it as-is.
“I hear the request. I don’t think doing exactly that solves the underlying problem. Here’s what I think they’re really struggling with, and here’s the option I’m proposing instead.”
That sentence does three things at once.
It acknowledges the customer.
It shows you’ve thought past the surface.
It makes the choice yours.
No apology. No hedging. Just ownership.
Teams don’t need leaders who echo feedback. They need leaders who interpret it.
A 15-minute exercise for teams drowning in edge cases
If your backlog is full of “special cases,” this is for you.
