For deciding what to build: user interviews, feature requests, roadmaps, prioritising and saying no.
When you ask for help with a product decision, include:
- What the product does and who uses it
- How many customers you have
- The decision you are trying to make
- What customers have asked for, in their words, and how many asked
- What you think, and what makes you unsure
Good threads
- How you collect feedback and what you do with it
- A feature you built that nobody used
- A feature you refused to build, and what happened
- How you run user interviews
- How you choose what to work on next
- Whether to publish a roadmap
Principles worth arguing over
- Customers are good at describing problems and poor at designing solutions.
- One request from a customer who pays a lot is not the same as ten from people on the free plan. Decide which matters more to your business.
- Every feature you add is something you must maintain, document and support for as long as the product lives.
To get feedback on your own product from members, use the Workshop or Beta Testers & Feedback Swaps.