Why the Best Products Begin With Better Questions
Most failed products answered a question nobody was asking. The discipline that prevents this is unglamorous: asking better questions before building anything.
The early days of a product are full of answers: features, designs, pricing ideas, technology choices. What they usually lack is a precise question. And because answers feel like progress, teams skip the question and start building.
The cost of the wrong question
“How do we build a better scheduling app?” is a question. So is “Why do small clinics still lose appointments when scheduling apps already exist?” The first leads to features. The second leads to understanding — and possibly to discovering that the real problem is reminders, trust or staff workload, not scheduling at all.
Questions that sharpen a product idea
- Who, specifically, has this problem — and what do they do about it today? Existing workarounds are the best evidence that a problem is real.
- What happens if they do nothing? If the answer is “not much,” demand will be weak however good the product is.
- What would they have to stop doing to use this? Every new product replaces a habit. Name it.
- What would prove this idea wrong? Decide in advance, so you can recognize it when it happens.
A good question is a constraint. It tells you what not to build.
Borrowing from the factory floor
Manufacturing has long used the practice of asking “why” repeatedly — often associated with Toyota’s production system — to get past symptoms to causes. Product teams can do the same with user requests. A request for a feature is a symptom. The reason behind the request is the problem worth solving.
Why it matters
Better questions are cheap. Building the wrong thing is expensive. The teams that ship products people keep using tend to be the ones that stayed curious a little longer before they committed.
