Product Manager Track
For PMs on the team. Read Core first.
How to Think
A PM ships and delivers impact. Push through to completion. Have clarity on what and when.
When the work is "almost done," jump on a call with engineering and test together. Don't test alone, file tickets, wait for fixes, retest, and drag the loop out for a week while everyone waits. That's more work, less output, slower outcomes. The worst of all worlds. It feels like hard work when it shouldn't be.
The PM job is removing friction between "almost done" and "actually done." If you can't answer in 30 seconds — what problem are we solving, who has it, when is it done — that's the work.
What to Read
Onboarding
Craft
Growth
Going Deeper
- Ben Horowitz — Good Product Manager / Bad Product Manager — the canonical
- Marty Cagan — SVPG articles — start with "Product vs. Feature Teams"
- Lenny Rachitsky — Lenny's Newsletter — best ongoing PM writing
- Shreyas Doshi — Medium archive — taste, judgment, prioritization
- Sequoia — Writing a Business Plan — clear narrative thinking
- YC — Startup School Library — Altman/Cagan/Seibel on customer dev, MVP, growth
Coming soon: Discovery & Validation. Writing PRDs. Prioritization. Roadmapping. Metrics & Instrumentation. Stakeholder Management. Working with Design & Eng.
Related: Product Engineer, Product Designer