Why Users Credit Themselves And Not Your Product
The deepest value a product gives is the value nobody thanks it for
Pleasure leaves a receipt, and the receipt is denominated in exactly the units our dashboards already speak.
Two people open the same app on the same grey morning and have opposite experiences, and neither of them is wrong. One closes it feeling like the day now has somewhere to go. The other closes it feeling slightly worse and slightly more committed than before. The product did not change between the two sessions. Nothing in the interface knew which person it was talking to, or cared.
A designer can hold the whole product in view. Every state, every transition, every empty screen with its small reassuring sentence written and rewritten until it sounded calm. What the designer cannot hold in view is the reason the person showed up. That reason turns out to do most of the work, and it arrives already formed, before the first tap, from somewhere the design file does not reach.
The Same Screen, Two People
Ask two people why they use the same social feed and you can get answers that do not sound like they describe the same thing. One says it is how they stay close to family on the other side of an ocean, the only reliable window into a niece growing up in a country they rarely visit. The other says it is a time-sink they resent, something they reach for without deciding to, something they would be relieved to lose. The pixels are identical. The fifteen minutes are identical. The experience is not even adjacent.
What separates them is not the what. It is the why, and the why runs along a longer line than most product thinking allows for. At one end sits the person who genuinely cannot say why they keep returning. Further along, the person who would feel a low guilt if they stopped, the way you feel about a habit you have half-disowned. Further still, the person for whom the thing has quietly become part of how they see themselves, congruent with what they already value. Same feed. Every position on that line occupied at once by different hands holding different phones.
We tend to design as if the line did not exist. We design for a user, singular, with a goal, singular, and we measure whether the goal was met. The line is the part the funnel cannot see.
Pleasure Leaves A Receipt, Meaning Does Not
Here is the part that should unsettle anyone who has spent a quarter polishing an onboarding flow. When an experience is mostly about momentary pleasure, people credit the technology. The game was fun. The video was good. The thing did something to them and they know it was the thing. When an experience is mostly about becoming a little more capable, people credit themselves. They learned the language. They got the complicated device working that they were sure would defeat them. They figured it out. The tool that made the figuring-out possible drops out of the story entirely.
Someone who finally sets up a device they expected to lose a weekend to does not walk away grateful to the setup flow. They walk away thinking, quietly, that they can do more than they assumed they could. The flow we argued about in three reviews becomes the thing they did not notice. That is not a failure of the flow. It is the flow working exactly as intended, which is to say invisibly.
The better that path is, the less of it survives in memory.
I have started to think this is the same shape as a good teacher. A student who was taught well remembers learning to think. They rarely remember the lesson plan, the sequencing, the deliberate decision to withhold one idea until the week the class was ready for it. The plan worked precisely to the degree that it disappeared into the student’s sense of their own growth. Nobody thanks the scaffolding. The scaffolding was load-bearing anyway.
The Metric We Can Count Is The One That Fades
The cruel arithmetic is that the experience which credits the technology is also the one we can measure. Sessions, dwell, return rate, the satisfying upward line. Pleasure leaves a receipt, and the receipt is denominated in exactly the units our dashboards already speak. Meaning leaves no receipt. It shows up, if it shows up at all, as a person who still quietly cares about something a year later, which no event in the analytics pipeline was built to fire.
And the experiences that credit the technology turn out to be the ones people themselves expect to abandon. Pressed on whether a thing will matter to them in a year, people are honest in a way that should give product teams pause. The fun was real and it had no bearing on anything. It filled a stretch of dead time. It will be replaced by something else simple, soon, and they will not mourn it. The metric our instruments are best at catching is the one the user has already told us will not last.
This is the point where the argument wants to tip into something tidy, and it should not. A product made entirely of meaning, with no pleasure anywhere in it, is a product nobody opens on a tired evening when the day has already taken everything. Pleasure is not the opposite of meaning and it is not the enemy of it. It is closer to hygiene. It removes friction and bad feeling, it makes the thing bearable to return to, and on its own it is almost never the reason anyone’s life is different. A product needs it the way a room needs the lights on. Nobody writes home about the lighting.
So the honest position is uncomfortable. The part we can count is necessary and shallow. The part that decides whether the time mattered is the part that, by its nature, does not announce itself to us, and often does not announce itself to the user until much later.
The User Who Has Started To Wonder
There is a measurable difference, it turns out, between the person who never once asks why they keep using something and the person who has begun to ask. Both are still here. Both still open the app. In every chart we keep, they are the same line. But the second person has let the question into the room, and the question behaves like a leading indicator that no leading indicator was designed to detect.
That person reports more of the not-knowing-why and less of the it-fits-who-I-am. They have not left. They are, in the language of the dashboard, retained. Retention, in this case, is measuring the moment before a decision rather than the absence of one. Which is harder to act on than churn, because churn at least has the decency to show up as a number going down.
What the questioning looks like from inside the data is nothing. The taps land in the same place. The session lengths sit in the same band. A person can use something daily for a year while slowly building the private case against it, and the only place that case exists is in a sentence they have not said out loud yet. By the time the sentence is said it has usually already been decided. The stretch between the first quiet why and the last session is the most important part of the relationship and the one with no instrument pointed at it.
I notice this matters most for the products that look healthiest. A thing with enormous engagement and a population quietly composed of people who have started to wonder is not a thing in trouble yet. It is a thing in the specific kind of trouble that arrives looking exactly like success, right up until it does not.
The Part We Cannot Draw
The product is the part we can draw. The screens, the words, the timing of the small animation that nobody will consciously register but everybody would feel the absence of. We can spend a career getting that part right and we should, because the alternative is worse and more common.
What we cannot draw is the reason the person reached for it, and that reason decides nearly everything that follows. The same artifact becomes momentary relief, a faint guilt, or a piece of how someone understands themselves, and it does this without consulting us, using materials we did not ship. The deepest thing a product can give a person is something they will, correctly, attribute to themselves. They got better. They stayed close to someone far away. They became, in some small and durable way, more like the person they meant to be. The tool that made the room for that will not be in the sentence they use to describe it.
That is not a problem to be solved. It is closer to the actual shape of the work, seen without the flattering lighting we usually keep on it.
The most successful thing a product ever does might be to become forgettable in the right way. Not unused. Not unloved. Just absent from the story the person tells about the part that mattered, the way a good teacher is absent from the thought the student is now, finally, able to have on their own.
Terms / explained
Described terms.
- Hedonic experience
- An experience centred on momentary pleasure derived directly from a technology, such as fun, enjoyment, relaxation, or escape. Typically attributed by the user to the technology itself.
- Eudaimonic experience
- An experience centred on meaning, personal growth, and progress toward valued goals. Typically attributed by the user to their own effort rather than to the technology that enabled it.
- Attribution
- The judgement a person makes about what caused a positive experience. Pleasure is more often attributed to the technology, growth more often to the self.
- Motivational regulation
- The reason behind an action, ranging from not knowing why one acts, through acting to avoid guilt, to acting because it aligns with one's own values. The same action can sit at any point on this range for different people.
- Intrinsic motivation
- Engaging in an activity for its own sake because it is interesting or enjoyable, rather than for an external reward or to avoid a negative consequence.
FAQ / questions
Frequently asked.
What is the difference between hedonic and eudaimonic user experience?
A hedonic experience is about momentary pleasure derived directly from a technology, such as fun, relaxation, or escape. A eudaimonic experience is about meaning, growth, and progress toward something a person genuinely values, such as learning a skill or staying close to someone far away. The distinction matters because the two are experienced, remembered, and attributed differently. Pleasure is credited to the product, meaning is credited to the self.
Why do users credit themselves instead of the product?
When an experience involves becoming more capable, people remember the growth as their own accomplishment, not as something the tool gave them. Someone who sets up a difficult device walks away thinking they are more capable than they assumed, not grateful to the setup flow. The better the supporting design is, the more invisible it becomes, because it succeeds by disappearing into the user's sense of their own progress. This is structurally similar to good teaching, where students remember learning to think but rarely remember the lesson plan.
Why does meaning not show up in product analytics?
Analytics are built to count sessions, time, and return rate, which are the signature of momentary pleasure rather than lasting meaning. Pleasure produces measurable, repeatable behaviour that existing dashboards already capture. Meaning shows up, if at all, as a person who still quietly cares a year later, which no event in the pipeline was designed to fire. The result is that teams optimise the part users themselves expect to abandon and miss the part that decides whether the time mattered.
Ask / a model
Request an AI summary.
Hand this take to your model of choice for a summary, a deeper read, or a critique. Each link pre-fills a prompt that points the model at this page.
Read / further
Related reading.
- Pink, D. H. (2009). Drive. Riverhead Books.
- Csikszentmihalyi, M. (1990). Flow. Harper & Row.
- Norman, D. (2013). The Design of Everyday Things. Basic Books.