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

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

Reduce Noise: Consider slicing or filtering metrics in ways that reduce variance and noise. For example, you might look at the number of users who comment, rather than the raw number of comments.

user researchers

The culmination of the define phase is often some kind of review where the team gets the go-ahead for the work and people are assigned to the team.

As you talk to people, focus on the insights—both expected and unexpected—so you can form a mental model of your users. Try to predict what people will say, and keep track of where your intuition is right and wrong.

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 pic

It's disappointing to finish your research only to find out that you asked the wrong questions. The trick to asking the right questions is to know in advance how you'll use the answers.

Gamification. Techniques like "streaks" for using the product multiple days in a row can encourage people to start a habit, although they can also backfire when people accidentally break a streak.