I learned the delight trap on my first product. In 1994, Joel Maske and I watched a single stock quote take far too long to load on a gray screen. Our first users were students and curious early adopters, and every new person who signed up felt like a small miracle. Today the idea that you can see the price of anything, anywhere, instantly, is so ordinary it is invisible. The miracle became the floor.
Delight has an equation. I write it on the whiteboard in every lecture. Customer delight equals delivered service minus expected service. Expected service is built from many things: what the customer needs, what they want, what you promised, what you delivered last time and what your competitors deliver. Delight lives in the gap between what they expected and what they got.
Delight = delivered service minus expected service.
Every time you delight a customer, you raise what they expect next time. Yesterday’s delight becomes today’s baseline.
The vast majority of companies never become great, precisely because the vast majority become quite good.
Competitors raise the floor too.
At Lycos, the last input set the pace. In the portal race, whatever one portal launched, the others had to match within weeks. Every surprise one of us shipped became something every portal was expected to have.
Where I got it wrong.
I also learned that delight is measured against what the customer needs, not against the feature list. Lycos Clubs had every option a power user could want. It did not get much traction. Yahoo Clubs came six months later, did less and took off like wildfire. We had delivered more. We had not delivered what mattered. The question is never what features you can deliver. It is what fundamental value the customer needs, and how simply you can deliver it.
The only way out is forward.
This is why so many good companies stall. Jim Collins opened Good to Great with a line I quote often: good is the enemy of great. Most good companies stay good. They delighted their customers once and then mistook the new baseline for success.
Quality researchers mapped the same decay. In 1984 Noriaki Kano separated must-have features from attractive ones, the surprises that delight. Over time, he found, what delights becomes what customers simply expect.
I feel the trap from the customer’s side now. When this wave of AI arrived, I was a skeptic. What struck me was not how good it was at the start. It was how fast it improved. That pace resets what every user expects. There is no way out of the trap except to keep moving. You have to understand your customer well enough to see what they will want before they can say it.
Run the delight equation.
- Build the expectationFor one customer, write the five inputs: what they need, what they want, what you promised, what you delivered last time and what your competitors deliver.
- Score the gapDelivered minus expected. Above zero is delight. Zero is satisfaction. Below zero is a problem to fix first.
- Write down the new floorWhatever delighted them last time is now the baseline. Treat it as the floor, not the win.
- Find next year’s surpriseName one thing this customer will want before they can say it. Start on it now.
Quick answers.
What is the delight trap?
Rob Frasca’s term for a pattern most companies miss: every time you delight a customer, you raise what they expect next time. Yesterday’s delight becomes today’s baseline, so the only way out is to keep moving.
How do you measure customer delight?
Rob Frasca uses an equation: customer delight equals delivered service minus expected service, where expected service is built from needs, wants, promises, the last delivery and what competitors deliver.
Sources.
- Rob Frasca, The Creator’s Journey (forthcoming), Chapter XI, Building What Lasts.
- Jim Collins, Good to Great: Why Some Companies Make the Leap and Others Don’t (HarperBusiness, 2001). Chapter 1 excerpt as published by BookBrowse. Source
- Noriaki Kano, Nobuhiko Seraku, Fumio Takahashi and Shin-ichi Tsuji, “Attractive Quality and Must-Be Quality,” Journal of the Japanese Society for Quality Control, 1984. Source