Reverse Quality

When teams built on the assumption that more features means more satisfaction, there was no language for the month where everything requested got shipped and the ratings went down anyway. From the building side the backlog was clear, which felt like good work, while the people using the product liked it less.

Pagedeck ran into exactly that. A month after turning on notifications for every open and every edit on a document, the number of accounts that switched notifications off entirely had tripled. It had been a heavily requested feature and it worked correctly, and the result was still that.

The name came with the Kano model, which sorts features into must-be, performance and attractive quality to see how each one moves satisfaction. Its five types leave a slot for this case, so a feature pointing the wrong direction isn't mistaken for one built badly.

Put how much you deliver on one axis and satisfaction on the other. Every other type climbs to the right or stays flat — one-dimensional quality, where satisfaction rises in proportion to how well you do it, climbs most plainly. Reverse quality is the one line that falls, which means building it better costs you more. Send those notifications faster and more accurately and the people who don't want them get faster, more accurate interruptions.

The cause is usually one of two things.

1. It takes control away from the person. Auto-tidying built with good intentions rearranges the order somebody set by hand. Even when the result is neater, what sticks is that their arrangement changed without them.
2. The user base splits. The same feature is an attractive quality — the kind people are delighted to find — for one group and reverse quality for another. A team in the document daily welcomes full notifications; somebody who opens it once a month reads them as spam.

The reading comes from the two Kano survey questions: how would you feel if it were there, and how would you feel if it weren't. An answer of dislike it when present and like it when absent is reverse quality. If 42 out of 100 respondents answer that way, the instruction isn't to skip building it — it's to ship it switched off. So the treatment is one of three: default it to off, move it into settings as a choice, or drop it from the candidate list.

"This one came back as reverse quality. If we build it, the default has to be off."

Enough respondents disliked having it that shipping it enabled would cost more than it earns.

"Responses split down the middle between attractive and reverse. We need to segment and look again."

Two groups are mixed together and can't be summarized as one number.

"Plenty of people asked for it, but notification opt-outs jumped the day we turned it on. It was reverse quality."

A retrospective: request volume didn't predict satisfaction here.

At Pagedeck, when Mia brings a candidate list, whatever sits in this slot comes off first. Coming off isn't being thrown away — those items get rewritten as optional settings that ship switched off.