Q14 / PRODUCT
Problem 11
What features should I build?
Stop building features. Start solving problems.
Your product isn't a list of features. It's a map of problems. See where you win, where you lose - and what you'll never build.
- Time: 20 MIN
- Who: SOLO OR WITH TEAM
- Stage: STAGES 1-2
- Access: FREE
Coming soon. Map my product — interactive tool not yet available.
The short answer
How do I decide what to build next? Map the problems your customers have, not the features they ask for. Colour each one: green (best in class), orange (competitive), red (weak - losing deals). Mark what you haven't built by priority, and cross out what you'll never build. Every request goes in a box - and requests in a crossed-out box get a confident no.
How it works
- List the main problems your customers need solved, and split them into smaller ones.
- Colour-code how strong you are on each, compared to the competition.
- Drop every feature request into a box and score it.
Worked example
A big customer asks for sorting on a widget - weeks of rework. Asked why, they say they need to see today's top survey for their boss. A new "Top surveys today" widget takes half a day. Solve the problem, not the request.
FAQ
Who owns the ProductOS?
At Stages 1-2, one of the founders. Review it as a team, especially the crossed-out boxes.
What if a request doesn't fit any box?
Add a new box and colour it.
Is this a roadmap?
It's what your roadmap should come from.
From the book
Problem 11 - What features should I build?
Use this next
Coming soon. Map my product — interactive tool not yet available.