Ethics & Economics
Cost of poor quality: make the harm a number
Opinion loses to revenue targets. CX earns its seat in strategy when it can price the harm and name the mechanism causing it.
Poor quality and deceptive design are business decisions with a price, and that price can be calculated. Teams that quantify experience failures in their own data, and name the design mechanism responsible, turn CX from advocacy into analysis. Leadership responds to quantified risk, not sentiment.
Most customer experience arguments fail because they arrive as feelings, and feelings lose to revenue targets. The cost of poor quality discipline fixes that. It teaches teams to quantify the harm a bad experience causes, name the mechanism causing it, and propose the governance change that stops it, so a CX case walks into the room as analysis rather than advocacy. Instead of 'customers hate our checkout,' the argument becomes a priced statement: this specific flow loses this much revenue per quarter through abandonment, repeat contacts, and churn, and here is the design decision responsible.
Why it matters to the business
The macro numbers say the stakes are enormous. Qualtrics XM Institute put $3.7 trillion of global sales at risk from bad experiences, and CISQ priced the US cost of poor software quality at $2.41 trillion in 2022. PwC found 32% of customers will leave a brand they love after one bad experience, while great experience commands up to a 16% price premium. Poor quality destroys revenue at both ends.
Deceptive design now carries its own price line: the FTC settled with Epic Games for $520 million and with Amazon for $2.5 billion, which turns dark-pattern audits from an ethics exercise into risk accounting. Leadership responds to quantified risk. The job is to bring it.
How to use it
- Join experience failures to money in your own data: abandonment, refunds, repeat contacts, and churn by journey.
- Split cost of poor quality into prevention cost and failure cost, and report both to executives quarterly.
- Price each questionable design pattern: near-term conversion lift versus churn, support load, and regulatory exposure.
- Translate every CX proposal into revenue protected or cost avoided before it reaches a budget meeting.
- Attach one governance recommendation to each finding: a gate, a named owner, or a veto.
Where teams get it wrong
Two failure modes mirror each other. The first is presenting sentiment where finance expects arithmetic; a passionate anecdote loses to a spreadsheet every time. The second is inventing precision: numbers that cannot be traced to your own systems or to named research collapse under the first hard question and take the team's credibility down with them. Quantify only what you can defend.
Ask your team
- What does one point of churn cost us in revenue, and who owns reducing it?
- Which of our known experience failures have a price tag attached, and which are still described as feelings?
- When did a CX finding last change a budget line?
When you can price the harm and name the mechanism, you move from advocacy to analysis.
Apply this
Reading about cost of poor quality: make the harm a number is one thing. Seeing where it applies in your journey is the useful part.