By customer type or use case: List which requirements you need for each, then look for a list that's short and mostly a subset of things you need for your higher priority use case.

Break work into incremental launches and validate early

Our goal is for this book to help more people become great product managers.

To probe deeper, try the following questions: Can you walk me through how you would use the feature you're requesting? What happens before you use it? What happens after? Is that task part of a larger goal? What are some of the challenges you run into with that task? Have you tried anything to help with this problem before? What stopped it from wor

Show How People Are Using It: Sometimes teams lose track of how people are actually using the product, and what is most important to people. Include metrics that help illuminate how people are actually using the product, such as the relative usage of various features.

To write a user story or use case in the JTBD framework, you can use this template: When I , I want to , so I can .

Your company should have a dashboard that can show you the metrics over time. If it doesn't, please work with your team to create one! It's awfully hard to optimize metrics if you can't easily understand what they are.

In Scrum, teams work in sprints of one to four weeks. At the start of each sprint, the team does sprint planning where they pull work from the product backlog into the sprint backlog and estimate how much work can be done in the next sprint. During the sprint, team members pick work off the backlog and meet daily for a fifteen minute standup meetin

By cost: Look at the list of cost estimates and drill into anything that's particularly expensive.