The Customer Is Always Right: No, They're Fucking Not
Somewhere in the history of business, somebody came up with the phrase the customer is always right.
And for reasons that remain a complete fucking mystery, millions of people have been repeating it ever since.
The customer is always right.
Really?
Always?
Every single fucking time?
Even when they're demonstrably wrong?
Even when they don't understand what they've bought?
Even when they're demanding something that is technically impossible, commercially ridiculous or in direct violation of the laws of physics?
Apparently so.
Because the customer is always right.
What an extraordinary piece of bullshit.
If the customer is always right, why the fuck do we employ experts?
Why have engineers?
Why have consultants?
Why have doctors, architects, mechanics or electricians?
Why not just let the customer wander in, announce whatever nonsense has entered their head that morning and immediately implement it?
"Good morning. I'd like you to install a swimming pool on the roof of my bungalow."
"Certainly, sir."
"And I don't want any additional structural support."
"Of course, sir."
"And I'd like it completed by Thursday for £200."
"Absolutely, sir. The customer is always right."
By Friday, the bungalow is a fucking paddling pool.
But at least the customer felt listened to.
The Customer Who Knows Absolutely Fuck All
I've spent years working in IT, and one thing I've learned is that customers are perfectly capable of being spectacularly wrong.
Not occasionally wrong.
Not slightly mistaken.
I mean we may need to contact NASA to establish how you've managed to arrive at that conclusion wrong.
And that's fine.
Customers aren't expected to understand every technical detail.
That's why they employ people who do.
But there's a difference between not knowing something and confidently insisting that everybody else is wrong.
"Your system isn't working."
"Okay. What's happening?"
"It keeps displaying an error."
"Right. What does the error say?"
"Invalid password."
"Okay. Have you checked your password?"
"Yes. It's definitely correct."
"Are you sure?"
"Absolutely."
"Could you try resetting it?"
"No. The problem is with your system."
Of course it fucking is.
The system is deliberately rejecting your password because it doesn't like your personality.
Perhaps the server has developed a grudge.
Perhaps the database has decided to ruin your Tuesday.
Or perhaps, and I appreciate this is a wildly controversial suggestion, YOU'VE ENTERED THE WRONG FUCKING PASSWORD.
But no.
The customer is always right.
So we raise an incident, assign an engineer, schedule a call, investigate the authentication logs and spend three hours establishing that the customer has been typing Password123 instead of Password123!
"Ah, yes. That seems to have fixed it."
Wonderful.
That'll be £600 in wasted engineering time, please.
"Can you provide a root cause analysis?"
Yes.
ROOT CAUSE: YOU'RE A FUCKING IDIOT.
The Customer Who Wants Something Impossible
Then there's the customer who has absolutely no understanding of what's technically possible but possesses an astonishing level of confidence in their ability to demand it.
"We'd like the system to do this."
"Okay. Unfortunately, the platform doesn't support that functionality."
"But we need it."
"I understand. However, there are technical limitations."
"Can you not just make it work?"
Oh, of course.
Why didn't I think of that?
I'll just open the secret settings menu and select Ignore All Technical Limitations.
Perhaps there's a button labelled Make Impossible Shit Happen.
I've been working with software for years and somehow completely overlooked it.
"Surely there must be a workaround?"
Possibly.
But a workaround isn't a fucking magic wand.
Sometimes the answer is no.
Not because we're being difficult.
Not because we lack ambition.
Not because we're insufficiently committed to customer excellence.
But because what you're asking for is either impossible, unsafe, prohibitively expensive or completely fucking stupid.
And none of those things becomes less true because you've said "business critical" seventeen times.
Can You Just Do It Quickly?
Ah, the word just.
Possibly the most dangerous four-letter word in corporate IT.
"Can you just add a field?"
"Can you just change the workflow?"
"Can you just integrate it with another system?"
"Can you just migrate the data?"
"Can you just make the application work completely differently?"
Just.
As though adding the word just magically reduces the complexity of the task.
Imagine walking into a hospital.
"Doctor, could you just perform a heart transplant?"
"Well, that's a major surgical procedure."
"Yes, but I only need a small one."
A small heart transplant?
What the fuck does that even mean?
"Could you just remove the old heart and pop another one in? Shouldn't take more than twenty minutes."
No.
And neither will your fucking software integration.
The customer doesn't need to understand every technical detail.
But they do need to accept that the people who actually understand the work might have a slightly better idea of how long it takes.
The Salesperson Who Promises Absolutely Anything
Now, here's where things get particularly ugly.
Because sometimes the customer isn't the biggest problem.
Sometimes it's the salesperson.
A customer asks for something completely unreasonable.
The technical team explains that it isn't feasible within the proposed budget or timeline.
And the salesperson, whose entire personality appears to consist of commission payments and expensive fucking shoes, announces:
"Absolutely! We can deliver that!"
Can we?
That's interesting.
Because five minutes ago, the engineers said we couldn't.
But apparently, Gary from Sales has discovered a previously unknown branch of computer science.
"Don't worry, we'll work out the details later."
Will we, Gary?
Or will I work out the details later while you disappear into the sunset clutching your commission?
Gary has never written a line of code.
Gary couldn't distinguish a database from a fucking dishwasher.
But Gary has just promised the customer a fully integrated enterprise solution in three weeks.
"Let's not get bogged down in technicalities."
Technicalities?
Gary, the technicalities are the fucking product.
That's like selling somebody a house and telling the builders not to get bogged down in bricks.
And when the inevitable disaster arrives, Gary is nowhere to be seen.
He's in Dubai.
At a sales conference.
Posting photographs on LinkedIn about the importance of customer relationships.
Meanwhile, the delivery team is attempting to construct a functioning system from seventeen contradictory requirements, a budget of £4.50 and a project plan written by somebody who appears to have suffered a serious head injury.
But don't worry.
Gary's exceeded his quarterly target.
The Customer Who Changes Their Mind Every Five Minutes
Another delightful species.
The customer who doesn't know what they want but is absolutely certain that whatever you've built isn't it.
"We'd like a blue button."
Fine.
You build a blue button.
"Actually, could it be green?"
Fine.
You make it green.
"On reflection, we think orange might be better."
Okay.
Orange it is.
"Could we perhaps explore something a little more innovative?"
What, a fucking rainbow?
"Maybe the button shouldn't be a button."
Right.
What should it be?
"We're not sure. We'd like you to come back with some options."
Of course you would.
And then, after three workshops, four design reviews, seventeen emails and a presentation containing the phrase user-centric transformation journey, the customer announces:
"Actually, we preferred the original blue button."
YOU ABSOLUTE FUCKING WALNUT.
And naturally, all this additional work is expected to be included in the original price.
Because the customer is always right.
No, the customer is indecisive.
There's a difference.
The Account Manager With No Spine
And then there's the account manager.
A person whose job, in theory, involves maintaining a productive relationship between the customer and the company.
In practice, some appear to believe their primary responsibility is agreeing with absolutely everything the customer says, regardless of how unreasonable it might be.
"The customer is unhappy."
"Why?"
"Because the project is late."
"Well, they've changed the requirements eleven times."
"Yes, but we need to maintain the relationship."
"Okay. Have we explained that the changes affect the timeline?"
"We don't want to appear confrontational."
Confrontational?
By explaining reality?
We're not threatening to invade their fucking country.
We're telling them that changing the scope of a project changes the amount of work required.
"Perhaps we could absorb the additional effort as a gesture of goodwill."
A gesture of goodwill?
With whose fucking time?
Yours?
Are you going to come and build the software?
Are you going to stay late testing it?
Are you going to spend your weekend fixing the defects?
No.
You're going to sit in another meeting, smile sympathetically and promise the customer that the delivery team will "go above and beyond".
Wonderful.
Another corporate hero spending somebody else's fucking time.
The Customer Who Wants a Discount Because They're Important
"Do you know how much business we give your company?"
Yes.
We have an entire finance department dedicated to knowing exactly that.
"Well, we expect a certain level of flexibility."
Flexibility.
Another magnificent word.
Usually meaning we'd like additional services without paying for them.
"We're a very important customer."
Congratulations.
Would you like a certificate?
Perhaps a little badge?
Or a photograph of Kevin shaking your hand?
Being an important customer doesn't mean the laws of economics stop applying.
If you order ten pizzas, you don't automatically get to demand another seventeen for free because you've been a loyal customer.
"Actually, we're a strategic pizza partner."
Are you?
Well, in that case, perhaps you'd like to strategically fuck off.
The Customer Escalation
Of course, when the customer doesn't get what they want, there's always the escalation.
"I'd like to speak to your manager."
Naturally.
Because if you don't like the answer from somebody who understands the problem, perhaps somebody who understands considerably less will give you a different one.
Martin joins the call.
Martin is a middle manager.
He has the personality of a fucking brick, the emotional intelligence of a parking meter and the managerial instincts of a confused garden vegetable.
But Martin has authority.
Which, in corporate life, is frequently mistaken for competence.
"Right, let's see if we can find a solution."
We already have a solution, Martin.
We explained it.
The customer didn't like it.
"Well, perhaps we need to think outside the box."
Oh, for fuck's sake.
The box isn't the problem.
The customer wants something that can't be done.
"Let's not focus on what we can't do."
Why not?
That's quite an important part of engineering.
If a bridge can't support a hundred tonnes, perhaps we should focus on that before driving a hundred-tonne lorry across it.
But Martin wants to demonstrate leadership.
So he announces:
"I'm sure we can find a way."
Excellent.
How?
"Well, I'll leave the technical details with you."
Of course you fucking will.
You've just promised the impossible and handed it back to the person who told you it was impossible.
What a magnificent display of management.
Perhaps we should give Martin a fucking award.
The Customer Who Doesn't Read Anything
One of the most astonishing things about customers is their ability to ignore every piece of information provided to them and then complain that nobody told them.
You send an email.
They don't read it.
You send a document.
They don't open it.
You explain the process in a meeting.
They're not listening.
You send a follow-up summary.
They ignore that too.
Three weeks later:
"Why weren't we informed about this?"
WE FUCKING TOLD YOU.
It's in the email.
It's in the document.
It's in the meeting notes.
It's in the project plan.
It's probably written on the inside of Martin's fucking skull.
But apparently, because the customer couldn't be bothered to read any of it, the company has failed to communicate effectively.
"We need to improve our stakeholder engagement."
No.
We need the stakeholder to learn how to fucking read.
The Customer Who Thinks Everything Is Urgent
Everything is urgent.
Every request is critical.
Every issue is business-impacting.
Every minor inconvenience is apparently threatening the continued existence of Western civilisation.
"The button is slightly misaligned."
"Okay. We'll schedule a fix."
"This is business critical."
Is it?
Really?
Because from where I'm sitting, the button is approximately three pixels to the left.
The system works.
The users can complete their tasks.
Nobody is losing money.
Nothing is on fire.
But apparently, this is a P1 incident.
"Can we get someone looking at it immediately?"
Yes.
We'll wake up the entire engineering team.
We'll establish a crisis management room.
We'll notify senior leadership.
Perhaps the Prime Minister should be informed.
BREAKING NEWS: BUTTON THREE PIXELS OUT OF POSITION. NATION ON BRINK OF COLLAPSE.
And then, when a genuine critical incident occurs, the same customer is astonished that the team is already overwhelmed.
Well, yes.
We've spent the last six hours treating a cosmetic defect like the fucking Chernobyl disaster.
The Customer Satisfaction Survey
And after all this, the company sends the customer a satisfaction survey.
"How would you rate the service you received?"
The customer gives a six.
A six.
Because the engineer wouldn't implement their impossible request, the project manager wouldn't agree to an unreasonable deadline and somebody had the audacity to explain that additional work costs additional money.
Management immediately launches an investigation.
"Why did we only receive a six?"
Because the customer is a fucking nightmare.
"Could we have handled the situation differently?"
Yes.
We could have lied.
We could have promised something impossible.
We could have worked for free.
We could have sacrificed our evenings, weekends and remaining dignity to make somebody happy who was never going to be happy in the first place.
Would that improve the score?
Possibly.
Would it improve the business?
Absolutely fucking not.
But the account manager looks concerned.
"We really need to improve customer sentiment."
Perhaps we could send them a fruit basket.
Or a personalised apology.
Or Gary from Sales could fly over and perform a fucking interpretive dance.
Sometimes the Customer Is Right
Now, here's the important bit.
Sometimes customers are absolutely right.
Sometimes the product is defective.
Sometimes the service is poor.
Sometimes the company makes mistakes.
Sometimes the customer has a legitimate complaint and deserves a proper apology, a clear explanation and a sensible resolution.
That's not controversial.
That's called doing business properly.
But treating every customer demand as automatically reasonable isn't customer service.
It's corporate cowardice.
And it's particularly cowardly when the people agreeing to those demands aren't the ones who have to deliver them.
A good customer relationship involves honesty, competence, clear expectations and the occasional ability to say no.
Not every customer is pleasant.
Not every request is sensible.
Not every complaint is justified.
And not every unreasonable demand should be rewarded simply because somebody threatens to escalate it.
Sometimes the customer is wrong.
Sometimes the customer is very wrong.
And sometimes the customer is so spectacularly fucking wrong that their misunderstanding should be preserved in a museum for future generations to study.
The Customer Is Always Right. Until They're Not.
So the next time somebody tells me that the customer is always right, I'd like them to explain something.
If the customer is always right, why are we paying specialists to advise them?
Why do we bother with technical expertise?
Why do we have contracts, requirements, budgets and project plans?
Why not simply hand the customer a blank cheque and ask them to write down whatever they'd like?
Because that's effectively what happens when companies confuse customer service with unconditional surrender.
The customer deserves respect.
The customer deserves honesty.
The customer deserves competent service.
But the customer does not deserve to be treated as an infallible fucking deity whose every passing thought must be converted into a business requirement.
And if Gary from Sales, Martin from Management or some spineless account director wants to promise the customer absolutely anything, perhaps they should be required to deliver it themselves.
I'd genuinely pay money to watch that.
Gary sitting at a laptop trying to build an integration he sold for £250,000.
Martin desperately Googling how to configure a workflow.
The account manager attempting to explain why the customer's demand violates seventeen technical constraints.
And Kevin standing behind them saying:
"Great collaboration, guys. Really demonstrating our customer-first values."
Meanwhile, the customer joins the call.
"Hi, everyone. Just one small change."
Gary looks terrified.
Martin starts sweating.
The account manager stops smiling.
"Could we bring the deadline forward by three weeks, halve the budget and add another integration?"
Silence.
"Also, we'd like the entire thing redesigned."
More silence.
"And obviously, we'd expect that to be included in the original price."
Finally, Martin speaks.
"Well, the customer is always right."
THEN YOU FUCKING BUILD IT, MARTIN.