By length of engagement: Start by building things people need in the first week, and then build things that are needed later on if the usage is high enough.

The define phase is when you narrow down the problem space to a specific, feasible slice, and frame it so it's ready for the team. You might have a hypothesis for a solution at this point, but it's just an illustration, not something you're committed to. During this phase, you'll be shaping the outcomes you're going after, and outlining the big

Here are some different approaches for splitting a product into multiple releases: By risk tolerance and friendliness: Start by releasing to users who can tolerate the most bugs, missing functionality, and UI hurdles so you can start getting feedback before all the polish is added.

Common tasks during the debrief phase include: Running a retrospective on what went well and what didn't Analyzing launch metrics Reading customer feedback on the launch Prioritizing "fast follow" work based on customer feedback Evaluating the launch success Sharing launch results with the company Planning for the next iteration

In this book, we've grouped the skills it takes to be a great product leader into five categories: Product skills help you design a high-quality product that delights customers and solves their needs. Execution skills enable you to run and deliver your projects quickly, smoothly, and effectively. Strategic skills improve your ability to set

Show the Success Metrics: Include graphs that show the most important success metrics for your product.

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

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

Look for the Precursors: What drives the success metrics?