Product People Deciding What to Build Next
- Customer
- A product manager at a 20–500 person company
- Context
- Accountable for an outcome while managing nobody who builds it
The Jobs of someone choosing between several correct things — where the cost of a wrong choice only appears after it is built.
5 Jobs
- 01When the data shows users dropping off, I want to know where they are stuck and why, so I fix the real thing instead of guessing and redesigning a screen.5 Pains · 5 Desired Outcomes · 5 Existing Solutions
- 02When every department has its own request, I want to refuse what is not worth building, so the roadmap does not become the loudest person's wish list.5 Pains · 5 Desired Outcomes · 5 Existing Solutions
- 03When a feature ships, I want to know whether it made a difference, so the next decision is better rather than simply moving on.5 Pains · 5 Desired Outcomes · 5 Existing Solutions
- 04When I need engineering to prioritise something, I want them to believe it is worth doing, so I am not spending authority on something I am also only guessing at.5 Pains · 5 Desired Outcomes · 5 Existing Solutions
- 05When the product serves several kinds of customer, I want to know which to build for, so I do not build something adequate for everyone and good for nobody.5 Pains · 5 Desired Outcomes · 5 Existing Solutions