Why customer obsession matters for product teams
Customer obsession is best understood as a working philosophy, not a slogan. It means designing, shipping and supporting products from the customer's point of view, then checking whether the value created is greater than the price charged.
Start with value, not internal preference
Value is not an abstract label. It describes how useful something is in helping a person reach a goal. A company creates value when its product helps people do that, and it captures only part of that value through revenue. The healthier position is for the benefit received to clearly exceed the amount paid, so customers can see a reason to stay and recommend the product.
Why the customer decides whether value exists
A product has no value in isolation. It becomes valuable when someone can use it to achieve something. That makes customers the essential constituency: a business may operate without investors or employees for a period, but without customers there is no business. When choices are close, choose the option that serves the customer better.
Four habits that make the value real
Keep speaking with customers and base decisions on what you learn from them. Consider how each change may help or harm them, and validate that judgement. Fix problems that frustrate customers even when the behaviour matches the original design. Ship for adoption and real impact rather than waiting for a flawless solution; a useful, slightly rough release can create more value than a polished feature few people use.
Treat confusion as a product problem
Support teams should separate a difficult interaction from the underlying signal. A customer may misread documentation or miss an obvious step; frustration is understandable, but the useful question is why the product, wording or guidance did not make the right action clear. Customers also communicate through behaviour, including purchases and support requests, so those signals should shape priorities. The familiar iPhone 4 antenna anecdote illustrates the opposite approach: telling users to avoid a problem instead of treating the complaint as a product issue to solve.
Intuition fades, so keep observing
Founders often begin close to their first users, but that closeness fades as the product and audience evolve. The builder may no longer use the product in the same way, or may not represent the target audience at all. Ongoing conversation and direct observation are therefore necessary. Weekly play testing with children, described in the Sago Mini example, shows how repeated first-hand observation can keep assumptions grounded in real behaviour.
Fairness compounds over time
Extracting more from existing customers without creating additional value can weaken trust and future growth. Accepting a short-term cost to be fair may compound over time through retention, goodwill and word of mouth. Apply that test to price increases and to decisions about passing store fees on to subscribers.
| Check | Question to answer | Evidence to collect |
|---|---|---|
| Value | Does the benefit clearly exceed the price? | Customer outcomes and willingness to pay |
| Impact | How might this change help or harm customers? | Before-and-after usage, complaints and support themes |
| Adoption | Will customers actually use this, or is it only polished? | Activation, repeat use and task completion |
| Fairness | Are existing customers treated fairly when prices or fees change? | Retention, churn and customer feedback |
Use as a decision checklist; validate each answer with customer evidence rather than internal opinion.
Frequently asked questions
How should price changes treat existing customers?
When a subscription price rises, existing subscribers can be allowed to stay on their previous price rather than being moved automatically. The same customer-first test applies to passing on store fees: consider whether shifting that cost would damage trust or perceived fairness, even if it improves short-term revenue.