Common tasks during the design phase include: Writing a spec Deciding what functionality is in or out Negotiating dependencies with other teams Whiteboarding with designers and engineers Giving feedback on design Running usability studies

This is a process called product discovery—when you figure out what problem you should go after.

Connecting work back to the goals is one of the most important things that a PM does.

The core product team at most modern tech companies is called the triad: Engineer (or Tech Lead), Designer, and Product Manager. Engineers are responsible for the technical solution. They'll plan the data structures and algorithms that will make things fast, scalable, and maintainable. They'll write the code and tests. Designers are responsible for

One thing you should not do is cut out polish.

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

Frameworks and rationale: Instead of simply telling people what to do, explain to them the reasoning behind the change so they can figure it out for themselves next time.

A huge part of your early credibility will come from your direct knowledge of the customer.

Notifications. The best kind of notifications let people know that something they were waiting for is available. Perhaps they were waiting for a coworker to complete a task or for their food to be delivered to their door. In these cases, people would be frustrated if you didn't notify them. People might also opt-in to reminders to use your product