Cracking the PM Career: The Skills, Frameworks, and Practices To Become a Great Product Manager (Cracking the Interview & Career)
Gayle McDowellamazon.com
Cracking the PM Career: The Skills, Frameworks, and Practices To Become a Great Product Manager (Cracking the Interview & Career)
Product Updates. Sometimes people stop using your product because it doesn't have all the functionality they need. Sending monthly update emails (with an unsubscribe option) is a great way to remind people about your product and entice them to try it again.
Every Friday afternoon, the product management team and other interested folks from the design, research and analytics teams sit together for an hour and "tear down" an interesting mobile or web app. By "tear down," we don't mean "criticize", but rather investigate and reverse engineer the thinking and experience under
... See moreBy complexity of need: Start with the users who have the simplest needs, and build your way towards the more complex needs.
By customizability: Start with fixed options that will meet a subset of use cases, and then add customization options.
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.
The definition of a minimum viable product from Eric Ries's book, The Lean Startup, is: that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort.2 MVPs can be early working prototypes of a product, but they don't have to be. You can set up an AdWords campaign or a bu
... See moreFrameworks 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.
This depends on the team, but there are two main approaches—each with their pros and cons: Designers work one sprint ahead of engineering.
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