We have reviewed hundreds of product decisions over the years. The pattern is consistent: the best ones were made by people thinking about the user. The worst ones were made by people thinking about the technology, the roadmap, or the competitor.

User Obsession Is Not Customer Service

Being user-obsessed does not mean doing whatever users ask. Users ask for faster horses. They describe symptoms, not solutions. User obsession means deeply understanding the underlying problem — the job they are trying to get done, the friction that frustrates them, the outcome they actually want — and then building the best solution, even if it is nothing like what they described.

How to Build User Obsession Into Your Team

It starts with access. Engineers, designers, and PMs should all have direct access to user feedback, support tickets, and session recordings. Not filtered summaries — raw signal. When an engineer reads a support ticket where someone spent two hours confused by a feature they built, it changes how they approach the next feature.

The most powerful UX improvement process is removing the distance between the person who experiences the problem and the person who solves it.

Metrics That Reinforce the Wrong Behavior

Many teams inadvertently measure the wrong things. Features shipped, lines of code written, story points completed — these measure activity, not user value. The metrics that actually matter: retention, time-to-value, support ticket volume, and NPS. Orient your team around these and watch the product conversations change.