25 must-read educational articles for product managers
Tempo Team
Key Takeaways
The reading list covers market insight, shipping tradeoffs, team dynamics, and leadership – a spread that more accurately reflects the PM job than prioritization-heavy curricula.
Several entries are written for adjacent roles, and each one includes material a product manager can use the same week.
The product management articles worth saving are the ones that helped during a specific hard call and stayed useful long after that moment passed. This list collects 25 of them, grouped by the part of the PM job each one actually improves.
Some entries sit outside the product canon on purpose. The PM role borrows heavily from engineering and design writing, and the best pieces in those neighborhoods are often sharper than the writing aimed directly at product managers.
1. The only thing that matters
Author: Marc Andreessen
What's most critical to the success of a startup? Tricky question. Lots of wrong answers. In part 4 of a 9-part series on startups, Marc Andreessen (co-founder of Andreessen Horowitz) identifies three factors – team, product, and market – and argues that market knowledge, or "user empathy," is the most likely determining factor. A compelling, direct answer relevant for PMs at any size company.
2. 12 Things About Product-Market Fit
Author: Tren Griffin
Most PMs struggle to pin down product-market fit because it looks different for every product. Tren Griffin, who works at Microsoft, sums it up more clearly than most. My favorite definition from this article: "The term product/market fit describes 'the moment when a startup finally finds a widespread set of customers that resonate with its product.'" Keep this top of mind when starting any new product journey.
3. Relentlessly Resourceful
Author: Paul Graham
Originally written for founders, by a founder. But the trait Graham describes – relentless resourcefulness – is exactly what I look for when hiring a PM. Almost no amount of experience, theory, or charisma replaces the ability to handle any problem with determination and grit.
4. The One Cost Engineers and Product Managers Don't Consider
Author: Kris Gale
The answer: the cost of maintaining new code. The more complex you make your product, the higher the cost of changing it later. I still share this post with new PMs regularly. I care far more about a feature's maintenance cost over time than its short-term ship date.
5. The Time Value of Shipping
Author: Brandon Chu
Knowing when to pull the trigger on a product release is a necessary and tricky skill for PMs. Shopify's VP of Product Brandon Chu built a framework to simplify that decision. Tactical and useful.
6. Maker's Schedule, Manager's Schedule
Author: Paul Graham
This post genuinely changed how I interact with team members day-to-day. Designers and developers dive deep into one problem at a time – interrupting them breaks their flow. Managers context-switch by nature. Knowing the difference makes you a better collaborator. I also credit this article with pushing me to protect my own maker time. No meetings in the morning unless absolutely necessary.
7. Deadlines
Author: Brandon Chu
A healthy reality check about deadlines and balance. The part that stuck with me: Deadlines are about changing behavior, not hitting dates. It's no coincidence that sales teams are busiest at quarter end. Keep this insight in your pocket when you're mapping project timelines as a PM.
8. Spotify's engineering culture (part 1)
Author: Henrik Kniberg
Fine, this one's a video. But Spotify's squad and tribe setup has fascinated me since agile became standard practice for product orgs. The video explains the motivation behind the culture and offers lessons PMs can apply to their own teams.
9. How to Work with Engineers
Author: Julie Zhou
Aimed at designers, but since Julie Zhou is a former PM and later VP of Product Design at Meta, I'm including it. As much time as a designer spends with engineers, a PM spends at least as much – and this cheat sheet applies to both roles.
10. How to Work with Designers
Author: Julie Zhou
You spend as much time working with your design team as you do with engineering, so it helps to understand how to manage that relationship well. Another useful cheat sheet from Julie Zhou, this time aimed specifically at PMs and designers.
11. How would you design an interface for a 1,000-floor elevator?
Author: Tarun Chakravorty
A think-outside-the-box exercise that tests your UX thinking. All PMs should be grounded in essential design principles – this post puts on the product design hat and gets you thinking like a designer.
12. Ruthless Prioritization
Author: Brandon Chu
Another from Brandon Chu, this time on a different prioritization challenge: between projects and within a project. Over-bloating – prioritizing too many things – is a mark of a junior PM. A seasoned PM knows how to get to an MVP (or MSP – minimum sellable product). This article helps junior PMs level up and gives senior PMs a framework to evaluate more junior teammates.
13. Understanding How the Innovator's Dilemma Affects You
Author: Mark Suster
"Innovator's dilemma" gets thrown around in the product space without much rigor. Two-time entrepreneur and VC Mark Suster breaks it down and explains what it means for your company – whether you're a startup trying to disrupt a market or an incumbent defending your position.
14. Dear PMs, It's Time to Rethink Agile in Enterprise Startups
Author: First Round Review
There's a common misconception that agile and planning are incompatible. This interview with Ogi Kavazovic, CMO and SVP Product Strategy at Flatiron Health, gives a tactical perspective on balancing them – and pushes back directly on that false choice.
15. The Agony and Ecstasy of Building with Data
Author: Julie Zhou
Julie's take on the perils of data and A/B testing is sharp and specific. It covers common traps PMs fall into with data tests. The pitfall I reference most: making decisions based on short-term data. This article has kept me from making that mistake more than once.
16. The Best Advice We Heard at First Round's CTO Unconference
Author: First Round Review
As a PM surrounded by technical people, reading insights from tech leaders on hiring, metrics, and diversity gives you useful context. Multiple perspectives from people who actually work in technical environments. Not theorize about them.
17. Do Things That Don't Scale
Author: Paul Graham
"Build it and they will come" is usually wrong. Startups succeed when founders take deliberate action – specifically, some actions that can't scale. These principles apply equally to product management, not just early-stage companies.
18. What We Look for in Founders
Author: Paul Graham
Written with executives in mind. The five traits Paul Graham lists for founders are traits I look for in any hire – especially PMs.
19. What sets the Top 1% of product managers apart from the Top 10%?
Author: Multiple
A Quora thread that compiles answers from various product leaders. The response from Ian McAllister (then Director at Airbnb) stands out for naming specific, observable traits that separate excellent PMs from good ones.
20. Bad managers talk, good managers write
Writing is an underrated PM skill. This post makes the case for written communication over verbal communication in management contexts. If you've ever doubted whether those technical docs matter, this will settle it.
21. Navigating Mid-Success
Author: Sam Altman
Product management is managing many expectations at once. Sam Altman (now CEO of OpenAI, formerly President of Y Combinator) wrote a direct reminder that PMs must have conversations with executives about what success actually means and whether everyone's expectations are aligned. Read this before you accept a PM role.
22. Simon Sinek: Why Leaders Eat Last
Author: Simon Sinek
I broke the rules again – it's a video. What starts as a standard leadership talk turns into a genuinely interesting discussion about the hidden expectations of leaders. As a PM, you'll be looked to as a leader. This video covers the essential leadership qualities behind earning trust from the people you work with.
23. Using the Kano model to prioritize product development
Author: Martin Eriksson
Delighting your users shouldn't be optional – it should be designed in. Martin Eriksson (founder of ProductTank, co-founder of Mind the Product) sums up the Kano model's central lessons clearly and concisely. Regardless of which prioritization technique your team uses, this post makes the case for why Kano deserves a place in your toolkit.
24. Create effective customer feedback loops for product teams
Author: Tarif Rahman
Customer feedback drives product teams toward better products – and getting that feedback to and from the product team is a system that needs deliberate design. This covers how Roadmunk's customer success team kept the feedback loop running so the product team got the most out of user input.
25. 20 Years Ago, Steve Jobs Demonstrated the Perfect Way to Respond to an Insult
Author: Justin Bariso
If you haven't seen the interaction between Steve Jobs and an inquisitive (and insulting) audience member, this post breaks down the biggest lessons from it. What could have been a bad moment turned into a clear lesson in patience and humility. Read this before the next time you get pushed back on something you've built.
Sign up for a demo
Request Demo
