There is no better source to learn about the art of product management than from the best practionioners themselves.
Thankfully, many leading PMs have published blog posts on all aspects of the job. As former PMs ourselves, we've put our prioritzation skills to use and curated a "must-read" list of posts from PM leaders on important topics like the role of PMs, collaboration, execution, analytics and strategy.
Our picks of the 10 best posts on product management. Ever.
Remains one of the most succinct, insightful posts on the varied, crazy and challenging role of product management.
Worth reading because many hiring PMs have some version of the criteria Ken laid out here in their mind when doing interviews.
A funny, memorable post that illustrates how should work with engineers by calling out the 10 things you definitely should not do.
No non-sense, informative post on how to work with designers from a VP of Design at Facebook who used to work as a PM and an engineer.
A detailed look at how the Intercom team went about re-designing their Messaenger home screen with tactical details on goals, mocks and outcomes.
An in-depth overview of how one poor product assumption decision derailed an entire product launch. While painful to read, it's a great post that shows the importance of getting the details right.
A thorough and analytically sound post on one of the most important aspects of modern day product management: running and analyzing experiments.
By far the best post on the critical topic of LTV, including an overview of the correct way to calculate it and all the pitfalls you need to watch out for.
Great example of clarity of thought in product strategy and execution at a high level. All of them are worth reading, but a solid, recent one is the 2016 annual results letter.
The seminal blog post on product market fit and why it's the "the only thing that matters" when launching a new company (or a new product).
Many leading consumer technology companies, e.g., Google, Facebook, Amazon, Netflix, etc., have built up an incredibly strong position for themselves and Ben's post lays out convincing argument for the systematic and predictable ways this happens.The origins of Product Hunt (Ryan Hoover, ProductHunt)
This is about as good as it gets for a tactical memoir of how a modern tech product was born. Covers everything from the email-first experiment to web app v1, including snippets of email conversations, early mocks and tweets.Climbing the wrong hill (Chris Dixon, Andreesen Horowitz)
Great, general career advice from a former PM and founder. For anyone embarking on a PM career, it's worth reading to this make sure you're thinking about your job finding algorithm in the best possible way.Maker's schedule, manager's schedule (Paul Graham, YC)
In a company, PMs are managers, not makers. While they do manage the product, they do not write the code, design the mocks, write the marketing copy, etc. As a result, the type of schedule they keep and the type of schedule their teammates keep will necessarily vary dramatically. This post explains why.Get one thing right (Andy Dunn, Bonobos)
PMs are often tempted to build robust, fully-featured products that can solve every problem under the sun. The challenge is that doing everything well out of the gate is a recipe for failure. Andy Dunn, the founder of Bonobos, explains why getting one thing right is the critical first step.The DNA of product management (Hunter Walk, Google, Homebrew VC)
Product management is a job of "many hats." Hunter Walk, an early Second Life, Google and YouTube PM, details what those "hats" a PM must wear are and why they matter so much.Advice from 17 product managers (First Round Review)
A nice collection of tactical advice from seventeen different product managers covering everything from driving decisions with data to the best way to communicate with stakeholders.The next feature fallacy (Andrew Chen, Uber, Andreesen Horowitz)
The TLDR: It's often tempting for PMs to think the next feature they launch will magically fix the product. The reality, almost always, is that it won't.Writing is thinking (Steven Sinofsky, Microsoft, Andreesen Horowitz)
One of the core tools of the PM role is writing specs (or PRDs - project requirement documents) that define what a feature is, who it's for, and how it should be built. Given that, writing well is a key skill for PMs.
Real interview questions. Sample answers from PM leaders at Google, Amazon and Facebook. Plus study sheets on key concepts.