Most definitions of quality start with absence. No defects. No regressions. No failures in production. These are useful floors — but they're floors, not ceilings. A product can be technically flawless and still feel wrong to everyone who touches it.
After years in quality engineering, I've landed on a different starting point. One word. One question that cuts through every checklist, test plan, and acceptance criterion I've ever written:
Would they be delighted by this?
Not satisfied. Not unblocked. Delighted.
The frame matters because it's both more demanding and more human than the standard definitions. Delighting someone requires understanding what they actually care about — not just what they asked for. And crucially, it forces you to name who you're asking about. Because quality doesn't have one audience. It has many.
Delight is a stakeholder question
I first wrote this as a LinkedIn post years ago, and it's the framing I keep coming back to. Here's how I think about it:
How do you define quality?
Delight.
Not the Turkish Delight I grew up on, but the Delight each person feels.
- Consumer delighted to use the product — it's intuitive, frictionless, maybe even surprising in the right ways
- Ops delighted to support this service in PROD — observable, reliable, not a source of 2am pages
- Developer delighted to write that code — the architecture makes sense, the tooling cooperates, the intent is clear
- Product Designer delighted to see a solution-based approach to complex problems — their intent survived the build
- PM delighted to have crafted the best possible solution, in spite of many constraints
- Dev Manager delighted to lead this team and support this product — something they'd be proud to show anyone
- Tester delighted — let's just say that delighting your Tester is the holy grail
- SEO Manager delighted to measure positive engagement — the signals are real and growing
- Analytics delighted to collect and predict trends — the data is clean, trustworthy, and tells a story
- Customer Support delighted to support this consumer — fewer tickets, better answers, less frustration on both sides
- Intern delighted to experience a taste of the future — what great looks like when it's done right
Come to think of it, the only person that should not be delighted is the competition.
Originally published on LinkedIn
Notice that none of these definitions of delight are the same. The consumer's delight is about experience. The developer's is about craft. Ops is about stability. Analytics is about trust in the data. The Intern's is about inspiration.
That's the point. Quality isn't a single thing — it's a system property, felt differently by everyone who touches your product. The question "would they be delighted?" only works if you're willing to slow down and ask it about each of them.
How to use this framing
I use this as a gut-check during reviews, not a checklist. When I'm evaluating whether something is ready to ship, I run through the list mentally: who are the people this touches, and is there anything here that would actively un-delight them?
Some questions are obvious — does the consumer experience work, is it accessible, does it do what it says? Others are less visible but equally real. Will Ops be paged at 3am for this? Will the developer who inherits this code understand what they're looking at? Will the data Analytics depends on be trustworthy six months from now?
The tester question is always last, and always the hardest. A delighted tester means the thing you built was so well-considered that finding problems in it required real creativity. That's a high bar. It's the right bar.
If you can walk through every person who will touch your product — everyone from the person who wrote the first line of code to the person who fields the first support ticket — and honestly answer "yes, they'd be delighted by this," you've asked a better quality question than most test plans provide.
And that last line about the competition? It's not a joke. Quality done well is a moat. The goal isn't parity. It's to build something so right for everyone involved that replicating it is genuinely hard.
That starts with delight — for all of them.
This piece was researched and shaped in genuine partnership with Claude, Anthropic’s AI. Tania names this collaboration intentionally — because meaningful AI partnership is worth acknowledging, not hiding.