Be a heat shield, says Rich Mironov.
In Summary: VPs of Product Management establish the broad context that allows great products and services to be built. They must create an environment where their teams can be successful. This means a lot of organisational design, behaviour modification and a relentless focus on the most important projects.
Packed with one-liners, prepared responses and insightful anecdotes, this is a masterclass in internal stakeholder management.
List joy from Indicative's Matt Levin.
In Summary: This epic list started life as an internal company spreadsheet and evolved into a giant record of PM tools and techniques that was well worth sharing.
From product ideation to analyzing user engagement post-launch, it's been ordered according to key steps of the product management process and stuffed full of useful data about when to use each one (and how).
Up and to the right, says Iulia Porneala.
In Summary: How can Product Managers deconstruct growth? The answer, says Iulia, is physics. Or the theoretical simulations used in physics to prove real world concepts.
By analysing your product's funnel (initial visit, signup, in trial engagement and payment) and applying theoretical models such as The Rule of 72 it's possible to determine the % by which you must increase each metric in order to increase revenue.
PM is more than just 'Getting things done', says Daniel Demetri.
In Summary: Daniel takes issue with the conventional description of Product Managers as the 'glue' between differing domains of expertise. Just as there are different types of glue, he says, different PMs inevitably bring a technical, UX or business focus as a result of their background.
As your product strategy changes over time, so should what Product Managers do, and where to find them.
This week's MVP Deep Dive #1 comes from Jim Brikman of Atomic Squirrel.
In Summary: Most people don't understand the point of an MVP. An MVP is not a product with half the features removed, or a way to ship earlier. In fact, the MVP doesn’t have to be a product at all. And it’s not something you build only once, and then consider the job done.
In a trial-and-error world, the one who finds errors the fastest wins. Some call this philosophy “fail fast", some call it Lean, some Agile. Whatever you call it, the point is to find out which of your assumptions are wrong by getting feedback on your product from real users as quickly as possible.
MVP Deep Dive #2 is from Crisp's Henrik Kniberg.
In Summary: Henrik Kniberg is best known for writing about 'How Spotify build Products' in 2013 as well as videos about their engineering culture.
In this (admittedly long) piece, he picks apart common misunderstandings about MVPs. Henrik suggest we replace the term 'MVP' with Earliest Testable Product (the first release that customers can actually do something with) or Earliest Lovable Product (the first release that customers will love, tell their friends about, and be willing to pay for.)