Must reads
- Good Product Manager/Bad Product Manager by Ben Horowitz of a16z, and his ‘14 book The Hard Thing about Hard Things
- The Innovator’s Dilemma and The Innovator’s Solution by Clayton Christensen (books, but worth it)
- How to get startup (and feature) ideas, Do things that don’t scale, and Maker’s Schedule, Manager’s Schedule by Paul Graham of YC
- Leading Cross Functional Teams, How to hire a product manager, and How to work with software engineers by Ken Norton, Google PM
- Software Inventory by Joel Spolsky, StackOverflow/FogCreek CEO
- Get one thing right by Andy Dunn, Bonobos CEO
Books
- The Everything Store: Jeff Bezos and the Age of Amazon
- In The Plex: How Google Thinks, Works, and Shapes our Lives
- The Design of Everyday Things
- Managing Humans, by a former eng manager at Apple on the soft skills you need to manage and lead a software development team
- The Lean Startup, by Eric Reis
- Cracking the PM interview, a great overview of what the PM role is, how it looks at different companies, and how to ace interviews
- Naked Statistics, an accessible primer to stats so you can understand and analyze experiment results
- On Writing, by Stephen King (of horror book fame)
A good product manager is the CEO of the product. A good product manager takes full responsibility and measures themselves in terms of the success of the product. The are responsible for right product/right time and all that entails. Bad product managers have lots of excuses.
Good product managers crisply define the target, the “what” (as opposed to the how) and manage the delivery of the “what.” Bad product managers feel best about themselves when they figure out “how”.
Good product managers don’t take all the product team minutes, they don’t project manage the various functions, they are not gophers for engineering.
Good product managers take written positions on important issues (competitive silver bullets, tough architectural choices, tough product decisions, markets to attack). Bad product managers put out fires all day.
Good product managers decompose problems. Bad product managers combine all problems into one.
Good product managers focus the team on revenue and customers. Bad
product managers focus teams on how many features Microsoft is building.
Good product managers send their status reports in on time every week, because they are disciplined. Bad product managers forget to send in their status reports on time, because they don’t value discipline.
Defining an amorphous role
- We Are Product Managers by Satya Patel, ex VP Product at Twitter
- Top 10 Product Leadership Lessons and Be a great product leader by Adam Nash, COO @ WealthFront / Ex-VP of PM at LinkedIn
- A product manager’s job by Josh Elman, Twitter/FB/LinkedIn PM
- The DNA of product management by Hunter Walk, ex YouTube PM
- What Makes a Good PM, by Ed Ho, Ex staff engineer At Google
- What distinguishes the top 1% of PMs by Ian McAllister, GM at Amazon
- Traits great Internet product leaders share
- Why companies should have Product Editors
Working with teams
- How to work with designers and engineers by Julie Zhuo, Product design director @ Facebook
- The Art of Decision Making as a Product Manager by Sachin Rekhi
- How to present designs (and anything you need feedback on) by Julie Zhuo
- 5 hard questions to ask yourself during a conflict by Julie Zhuo
Planning and prioritizing
- The best ways to prioritize a product and feature list by Ian McAllister
- Guide to product planning: three feature buckets by Adam Nash
- “Shipping beats perfection” and “It’s OK to be embarrassed about what your product doesn’t have” by Ben Kamens (Khan Academy VP Eng)
- The Tax of New by Julie Zhuo
- Product strategy means saying no
- The one cost engineers and product managers don’t consider by Kris Gale, VP of Eng at Yammer
- Understanding how The Innovator’s Dilemma affects you
Writing great (specs)
- Working Backwards by Wrener Vogels, CTO of Amazon
- Writing, briefly by Paul Graham
- The Specification is Dead; Long Live the Specification
- Bad managers talk, good managers write on how talking doesn’t scale.
Dealing with data
- The Agony and Ecstasy of Building with Data by Julie Zhuo
- Design for continuous experimentation by Dan McKinley, Principal Engineer at Etsy (another related Etsy data science slidedeck)
- The only metric that matters by Josh Elman
- How do users really hold mobile devices
Email me when Noah Weiss publishes or recommends stories