A practical reading shelf for product managers and leaders. Choose the problem you are working on, find a useful perspective and try one idea with your team.
An editorial selection, not a ranking. These books offer complementary perspectives rather than universal rules. Descriptions, reader-fit suggestions and exercises are original summaries; they do not imply endorsement by the authors.
Find a book for your situation
Foundation means an accessible starting point; Practitioner means applying the ideas in product work; Leader means a focus on team or organisational responsibility. These are editorial reader-fit labels, not quality scores.
30 of 30 books
InspiredMarty Cagan
Product foundations · Foundation
Inspired
How to Create Tech Products Customers Love
Marty Cagan
2nd edition
Cagan describes how technology product teams combine customer understanding, design and engineering to discover valuable solutions. A useful starting point for understanding the responsibilities behind the PM title.
Best for
New PMs and teams building a shared product vocabulary
When to read
When you need a clearer picture of what good product work involves.
Try this
Choose one proposed feature and write down its value, usability, feasibility and business-viability risks before discussing delivery.
Context: Written around technology product teams; adapt responsibilities to your organisation’s constraints.
Perri examines why busy teams can keep shipping without improving customer or business results. Connects product strategy, team structures and everyday decisions to meaningful outcomes.
Best for
PMs stuck in feature factories and leaders changing incentives
When to read
When delivery is on track but nobody can explain the value created.
Try this
Rewrite one roadmap item as a customer problem, a measurable outcome and the evidence you need before committing to a solution.
How to Innovate with Minimum Viable Products and Rapid Customer Feedback
Dan Olsen
A structured route from a target customer and unmet need to a value proposition, prototype and feedback. Particularly useful for turning broad product-market-fit advice into a working sequence.
Best for
Early-stage PMs and founders testing a product concept
When to read
When you have an idea but need a disciplined way to develop it.
Try this
Map your target customer, underserved need and proposed value on one page; mark the weakest assumption for your next prototype test.
How Today’s Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses
Eric Ries
Ries frames innovation as a learning process under uncertainty. Introduces a vocabulary for testing assumptions, judging progress and deciding when to change direction rather than defend an initial plan.
Best for
Founders, innovation teams and PMs exploring uncertain markets
When to read
Before investing heavily in a proposition with little behavioural evidence.
Try this
Write one falsifiable product assumption and the smallest safe experiment that could change your decision about it.
Context: A minimum viable product is a learning vehicle; it does not excuse unsafe or unusable releases.
A broad career reference covering the skills, behaviours and growing scope of product roles. Useful for converting vague development feedback into specific practice and evidence of progress.
Best for
PMs planning their next step and managers coaching them
When to read
When your growth plan needs more detail than “be more strategic”.
Try this
Pick one skill gap, agree on a real project where you can practise it, and define the evidence your manager will review.
Context: Career ladders vary by company; use the skill discussions to inform your own expectations, not as a universal promotion rubric.
Torres offers a repeatable discovery practice for a product manager, designer and engineer working together. Connects desired outcomes to customer opportunities, competing solutions and tests of risky assumptions.
Best for
Product trios building a sustainable discovery habit
When to read
When discovery happens only at project kick-off or before a big launch.
Try this
Create a small opportunity solution tree for one outcome and choose an assumption to test with your product trio this week.
A focused guide to customer conversations that produce useful evidence rather than polite encouragement. Helps product people notice leading questions, vague praise and unsupported promises.
Best for
Anyone preparing their first interviews or improving existing ones
When to read
Before your next customer conversation, especially if you are pitching too early.
Try this
Replace a hypothetical question with a request to describe the last time the person encountered the problem and what they did.
Patton uses the user’s journey to give individual stories context. A practical bridge between understanding a problem, discussing scope and choosing a coherent first release.
Best for
Cross-functional teams whose backlogs have lost the bigger picture
When to read
When a list of tickets hides the experience you are trying to improve.
Try this
Map one user journey with your team, then draw a release slice that supports a complete, useful outcome from start to finish.
Rumelt distinguishes a strategy that addresses a real obstacle from an ambition dressed up as a plan. Sharpens the thinking behind choices, priorities and coordinated action.
Best for
PMs and leaders writing strategy or challenging a vague one
When to read
When your strategy could describe almost any company or product.
Try this
Draft a one-page diagnosis of the main obstacle, a guiding policy and a short set of actions that reinforce each other.
Lafley and Martin present strategy as connected choices about customers, advantage, capabilities and management systems. Useful for exposing where a product plan lacks a credible way to compete.
Best for
Product leaders aligning a portfolio or a major market bet
When to read
When your team has many initiatives but no clear set of trade-offs.
Try this
For one product, connect your chosen customer and market to a specific advantage and the capabilities needed to sustain it.
Context: The examples draw heavily on established businesses; treat the choices as hypotheses when applying them to uncertain markets.
How to Nail Product Positioning so Customers Get It, Buy It, Love It
April Dunford
Updated and expanded edition
Dunford explains how a product’s context changes the value buyers see. A hands-on approach to positioning that connects alternatives, distinctive strengths and the customers who care most.
Best for
B2B PMs, founders and product marketers sharpening positioning
When to read
When customers misunderstand the product or compare it with the wrong alternatives.
Try this
List what customers would use without your product, then identify the differentiator that matters most to your best-fit segment.
How Smart Companies Design the Product Around the Price
Madhavan Ramanujam, Georg Tacke
Ramanujam and Tacke argue that pricing and willingness to pay belong early in product development. Offers a commercial lens on segmentation, packaging and which features deserve investment.
Best for
PMs shaping packaging, pricing or a new paid proposition
When to read
Before the feature set is fixed and pricing becomes an afterthought.
Try this
Write a research plan to compare what two customer segments value, how they buy and what evidence would support different packages.
Context: Stated willingness to pay is one signal; test it against buying behaviour and your market context.
Bush explores how the product experience can help customers discover value and become paying users. A useful lens on self-service growth, onboarding and whether a product-led approach fits your business.
Best for
Growth PMs and founders assessing self-service acquisition
When to read
When sign-ups are healthy but users struggle to reach a valuable result.
Try this
Trace the shortest path from sign-up to a meaningful customer result and identify one avoidable step to test removing.
Context: A product-led approach is a business-model choice; it can coexist with sales and will not fit every customer or buying process.
Cagan and Jones focus on the leadership conditions behind strong product teams: coaching, context, staffing and meaningful ownership. Helps leaders examine what genuine empowerment requires of them.
Best for
Product leaders managing PMs and cross-functional teams
When to read
When teams are called empowered but still wait for solutions and permission.
Try this
Replace one feature assignment with a clear problem, desired outcome and decision boundaries, then coach the team through its approach.
Marty Cagan, Lea Hickman, Christian Idiodi, Chris Jones, Jon Moore
The SVPG authors describe changing an established organisation towards their product operating model. The focus moves beyond an individual PM to executive behaviour, team capabilities and organisational change.
Best for
Leaders responsible for a product transformation
When to read
After understanding product-team principles, when the existing organisation makes them hard to apply.
Try this
Choose one pilot team and document the leadership support, customer access and decision rights it needs before changing its process.
Context: Presents SVPG’s approach and case studies; use them to reason about your constraints rather than promise a guaranteed transformation.
Doerr makes the case for objectives and key results through organisational stories. Useful for improving the link between an ambitious direction, observable progress and regular conversations about priorities.
Best for
Teams introducing OKRs or making existing goals more useful
When to read
When goals are vague, disconnected or indistinguishable from a task list.
Try this
Rewrite one key result so it measures a change in customer or business behaviour, with a baseline and a review date.
Context: OKRs are a coordination tool, not proof of a sound strategy. Avoid turning every metric into an individual performance target.
Grove examines the manager’s work through team output, leverage and operating routines. A practical reference for designing one-to-ones, decisions and feedback instead of relying on constant intervention.
Best for
New and experienced managers improving their management system
When to read
When your calendar is full but your team still depends on you for everything.
Try this
Review last week’s calendar and identify one recurring activity to redesign so it improves the team’s decisions without your constant involvement.
Context: Written from an earlier industrial and technology context; adapt the practices to contemporary, inclusive teams.
Scott’s framework pairs personal care with clear challenge. Useful for replacing avoided conversations and vague praise with feedback that gives someone a fair chance to improve.
Best for
Managers and peers who need more useful feedback conversations
When to read
When you are withholding specific feedback to keep a conversation comfortable.
Try this
Ask a colleague for one specific thing you could improve, listen without rebuttal and agree on a visible change you will try.
Context: Directness requires care, trust and attention to power and cultural context; it is not permission to be harsh.
Zhuo gives an approachable account of growing into management, including trust, feedback, hiring and meetings. Especially helpful for the shift from doing excellent individual work to enabling a team.
Best for
First-time managers and PMs considering people leadership
When to read
When you have new reports and are unsure what good management looks like.
Try this
Use your next one-to-one to ask where your report needs clearer context or support, then agree on one concrete improvement.
Marquet’s submarine command story explores moving decision-making closer to the people doing the work. A memorable case for pairing greater responsibility with competence and clear intent.
Best for
Leaders trying to reduce approval bottlenecks
When to read
When capable people still ask you to make decisions they understand better.
Try this
For one low-risk decision, ask the owner to explain their intended action, reasoning and guardrails before you offer your own answer.
Context: A leadership case study, not a literal operating model for every workplace. Preserve necessary safety and compliance controls.
Norman explains why products confuse people through concepts such as signifiers, feedback and mental models. Builds the vocabulary to discuss usability problems without blaming the user.
Best for
PMs and designers developing stronger interaction-design judgement
When to read
When a feature technically works but customers cannot understand or control it.
Try this
Inspect one critical interaction: what suggests the next action, what feedback confirms it and how can the user recover from a mistake?
Krug makes usability practical through clear navigation, understandable pages and observing real people. An accessible entry point for anyone who helps shape a digital experience.
Best for
PMs, designers and writers improving web or mobile usability
When to read
Before a redesign, or when familiar screens feel obvious only to the team.
Try this
Observe someone attempting a core task without coaching, then fix the most consequential point where they hesitate or misunderstand.
Gothelf and Seiden connect design work with explicit assumptions, small experiments and cross-functional learning. Helps teams replace document hand-offs with shared decisions about what to test next.
Best for
PMs and designers working with agile delivery teams
When to read
When design is a separate phase and feedback arrives after expensive commitments.
Try this
Turn one design proposal into a hypothesis linking a user, an expected behaviour and an outcome, then choose the cheapest useful test.
Stop Running in Circles and Ship Work that Matters
Ryan Singer
Singer documents Basecamp’s approach to shaping work before committing a team to it. Offers a distinctive way to discuss appetite, boundaries, unresolved risks and flexible scope.
Best for
Product and engineering teams struggling with unbounded projects
When to read
When projects expand because the problem, limits and risks were never made clear.
Try this
Write a short pitch for one problem with a time appetite, a rough solution, known risks and explicit exclusions.
Context: Developed in Basecamp’s context. Try a bounded experiment rather than assuming its cadence or full process fits your organisation.
Meadows introduces feedback, delays, stocks and flows as tools for understanding recurring problems. Valuable for product decisions whose consequences extend beyond one team or one metric.
Best for
PMs and leaders dealing with persistent, interconnected problems
When to read
When a local improvement creates a new problem somewhere else.
Try this
Draw a feedback loop behind one recurring product problem and identify a delay that could make an apparently sensible intervention backfire.
Context: Edited by Diana Wright. Product examples in this reading guide are applications of systems thinking, not claims about the book’s industry focus.
Presents research on software delivery performance and the technical and organisational capabilities associated with it. Helps product leaders discuss reliable delivery as a system rather than demand more individual output.
Best for
Product and engineering leaders improving delivery together
When to read
When speed and reliability are treated as opposing goals.
Try this
Map a recent change from idea to production with engineering and identify one wait or rework loop you can improve together.
Context: The book presents its original research context. Use contemporary DORA guidance for current metric definitions and avoid ranking individuals with team-level measures.
Organizing Business and Technology Teams for Fast Flow
Matthew Skelton, Manuel Pais
2nd edition (2025)
Skelton and Pais offer a language for team boundaries, cognitive load and interactions. Useful for understanding why dependencies and unclear responsibilities slow the flow of customer value.
Best for
Leaders designing team boundaries and platform relationships
When to read
When delivery delays come from coordination rather than a lack of effort.
Try this
Map one team’s dependencies and agree on the intended interaction with each partner: close collaboration, a service or temporary facilitation.
Context: Treat team design as an evolving response to work and cognitive load, not a permanent org-chart template.
Croll and Yoskovitz connect useful metrics to a business model and its stage of development. A strong prompt to choose a decision-driving measure instead of collecting an impressive dashboard.
Best for
PMs and founders choosing meaningful measures of progress
When to read
When your team tracks many numbers but cannot say what would change its plan.
Try this
Choose one metric for your current product question and write the threshold that would trigger a different decision.
Context: A focus metric still needs guardrails for customer harm, quality and longer-term health.
A rigorous guide to designing, running and interpreting online experiments. Gives PMs and analysts a shared foundation for recognising misleading results and building confidence in product decisions.
Best for
Experimentation PMs, analysts and teams running A/B tests
When to read
Before scaling an experimentation programme or trusting a surprising uplift.
Try this
Review your next experiment’s primary metric, guardrails and data-quality checks with an analyst before exposing users to it.
Context: The later sections are technical. Start with the introductory material and partner with a statistician for consequential test designs.
Mollick explores working and learning alongside generative AI while retaining human judgement. A useful starting point for product people testing where AI helps, where it fails and how work might change.
Best for
PMs and leaders developing practical AI fluency
When to read
When you want a thoughtful approach to AI experimentation beyond collecting prompts.
Try this
Compare a low-risk task with and without an approved AI tool; assess quality, errors and effort before changing the workflow.
Context: Model capabilities and tools change quickly. Protect confidential data, verify outputs and pair the book with current technical and policy guidance.