What gets measured, gets managed
The easier a thing is to count, the more likely it is to run the whole show. In product, that is how the conversion dashboard quietly becomes the whole universe.
Measurement is not neutral about what it rewards. It favors whatever sits closest to hand, and in product the things closest to hand are the tangible ones. Conversion, retention, time on task, revenue per user. Countable this sprint, so managed this sprint.
The intangibles wait outside in the cold.
Whether the product met the need someone arrived with. Whether it felt trustworthy. Whether the promise it makes on the first screen is still true by the last. None of these resolve to a clean number, and each asks something of you before you can read it at all: a clear vision of the product and a genuine understanding of the person using it. Harder than opening a dashboard. So it waits, and waiting turns into never, and the countable half wins the budget argument every quarter until nobody is left maintaining the other half.
And then eventually a substitution happens that no one consciously decides: the business metric stops standing in for the experience and becomes the experience. Performance becomes the whole universe: what the numbers show is treated as the only reality, what they cannot show is treated as absent. A team can hit every target on the board and still ship something nobody wanted, because the board was never able to see the want in the first place.
It’s not new, and it’s not unsolved
Service designers named the problem decades ago. SERVQUAL, built in the late 1980s, reads quality as the gap between what a customer expected and what they perceived, across five dimensions. SERVPERF followed a few years later, arguing you could drop the expectation side and score perceived performance on its own. Both are rigorous, and both have held up for forty years.
Both are also pretty hard to live with. They were designed for service encounters and periodic surveys: a long questionnaire after the fact, dimensions to reconcile by hand, a research project every time you want an answer. Few product teams will run that every sprint, so they run nothing, and drift back to the dashboard already open in the next tab. The old models were right about the problem. They were built for a slower world than the one a product team ships in.
What a modern product team needs is something lighter, quick enough to live inside a normal cycle, plain enough that brand, product and research can read it without a manual, and still honest about the intangible.
Three truths, three gaps, and a pizza place
To get a clear picture, we just have to look at three simple truths side by side: Need → narrative → reality.
First, the need, which is what matters most to the person, in their terms, never the action you wish they would take. The narrative is what you lead them to expect, and it runs far wider than marketing: a screen that lays everything out and lets you compare is already promising you are in control here, without a word written. The reality is then what the person concludes is true after using the thing. Not whether the feature worked, but whether they came away confident, or lost, or quietly sold to.
The gaps between them are where your diagnosis lives. Between need and narrative you find relevance, whether the story speaks to something the person values. Between narrative and reality sits credibility, whether the experience backs up what you claimed. And between need and reality you have fulfillment, whether the product resolves what the person came for, regardless of what you said about it.
Close all three and something materializes in the middle that none of them produces alone: brand integrity. It is the compound of a promise made well and kept, and like anything compound it builds on itself, a little more each time a person wants something, believes you will provide it, and finds that you did.
Treat the intangible like the tangible
The model only works if you refuse the asymmetry that started all this. The need, the narrative and the felt reality get measured with the same care and the same weight you give conversion and revenue. Not because they are softer, but because they are the part that decides whether the hard numbers still hold next year.
Reality can be read. It has to be read per person and per context, because the same delivery lands differently depending on who meets it. Show every option and a confident user reads control, a newcomer reads overload, someone in a hurry reads I cannot tell what matters. One average score flattens those three into a number true of nobody. Score them apart, against what each person needed, and the intangible stops being a feeling and turns into evidence you can act on.
Eight states, and where to point next
Each truth is either strong or weak. That gives you eight combinations, and every one points somewhere different.
Three strong is coherent value, the state you protect. Strong need and narrative over a weak reality is a broken promise, the most dangerous condition on the list and the one no dashboard catches: the promise still lands on the surface while the delivery fails underneath, teaching every believer not to trust you next time. Strong need and reality with no narrative is a silent strength, real value handed over without credit. And so on around the grid. Mend the delivery, tell the story, drop the claim, go find the need. You stop guessing what is wrong and start knowing where to aim.
None of this measures less. It counts the thing the convenient number was always standing in for. Put the need back beside the narrative and the reality, give the intangible its full weight, and the dashboard returns to what it was meant to be: a proxy, not the point.
Your intangibles were never really unmeasurable. They’re just unmeasured. That is a decision, made fresh every time an organization reaches for the nearest number because it is … near.
Hi, I’m Oscar - Founding designer at momondo, I’ve won a Material Design Award for Innovation, and I help design leaders succeed.