Teams often begin with “which features should we add?” Strong mobile products begin elsewhere: what specific problem is a person trying to solve, how often does it occur, and what happens if it remains unsolved?
The problem must be observable
“Users need a more convenient app” is too general. A better description is a situation: someone spends 20 minutes re-entering data, cannot check an order status, or loses context after an interruption. That can be tested through interviews, analytics, and prototype research.
How to separate symptoms from causes
- Ask what users do without your product.
- Find the exact point of delay or error.
- Compare what people say with what they do.
- Check whether the problem is important enough to change a habit.
The Headspace case shows that a problem can be broader than a single feature. The team wanted to expand into wellness, but first had to rebuild architecture and product quality. The problem was not a missing screen; it was the inability to support a new promise reliably.
After defining the problem, write a short hypothesis: “For [audience] in [context], we will reduce [barrier] so people can achieve [outcome].” Test it with a minimum experiment and define what success looks like.
A clear problem disciplines decisions, helps remove unnecessary features, and makes marketing more concrete. It is the foundation of UX and product strategy.
