Ethics & Economics
Ethics anti-patterns: how harm gets rationalized
Unethical CX arrives as a reasonable argument in a planning meeting. Name the pattern and the justification loses its camouflage.
Most CX ethics failures are not villainy; they are rationalizations that sound sensible in the room. Six patterns recur across industries, from hiding behind legality to using metrics as moral cover. Recognizing them by name, and installing a sanctioned way to object, is the difference between pausing harm and shipping it.
Unethical customer experience rarely announces itself. It arrives as a plausible argument in a planning meeting, and the arguments repeat across industries so reliably they can be cataloged. Six recur: it is legal, so it is fine. Ethics is handled by the brand campaign. The metrics show no damage. Everyone in our market does it. The engagement mechanics work, so keep them. And the people hurt are edge cases. Each sounds reasonable in the room. Each is a rationalization, and naming the pattern is what disarms it: once a team recognizes the move, the justification loses its camouflage and the conversation can proceed honestly.
Why it matters to the business
'Everyone does it' is almost literally true, and it is still no defense. A 2022 EU Commission study found 97% of the most popular sites and apps used by EU consumers deploy at least one dark pattern, and enforcement arrived anyway: the FTC settled with Epic Games for $520 million and with Amazon for $2.5 billion. Ubiquity protected no one.
The metrics shield is equally hollow. Luguri and Strahilevitz found mild manipulative patterns more than doubled sign-ups to a dubious service while triggering no backlash at all. Dashboards stay green while trust erodes, which means 'the numbers look fine' proves nothing except that you are not measuring the harm.
How to use it
- Teach the six patterns by name in a team session, so the vocabulary is shared before it is needed.
- Install a sanctioned red-flag mechanism now. Rationalizations win by default when there is no structured way to object.
- Treat any of the six arguments surfacing in a meeting as a signal to pause the decision, not proceed.
- Add a vulnerable-user check to design reviews: who bears disproportionate cost from this feature?
- Log each time a pattern is invoked and what was decided. That log is your ethics telemetry.
Where teams get it wrong
Teams assume the hard part is detecting bad intent. It almost never is. The people in the room usually sense the problem; what is missing is a sanctioned way to challenge the decision on ethical grounds, so the plausible argument wins by default. The structural fix precedes the ethical moment: build the mechanism before you need it, because you will not build it during.
Ask your team
- Which of our current practices survive mainly because everyone in our market does the same?
- Where do our metrics look healthy while customers are plausibly being harmed?
- If someone objected to a feature on ethical grounds tomorrow, what process would catch and weigh that objection?
Legality is not a defense. Metrics are not a moral shield. Everyone does it is not a reason.
Apply this
Reading about ethics anti-patterns: how harm gets rationalized is one thing. Seeing where it applies in your journey is the useful part.