20 practical guides
Product Management Guides
Learn how to frame product choices, investigate customer behavior, define measurable outcomes, coordinate delivery, and review evidence throughout a software product's lifecycle.
Built for product managers and cross-functional software teams that need concrete methods, reusable decision records, and clear evidence standards.
Clear product strategy
Connect a defined customer problem, product advantage, choices, outcomes, and evidence in a strategy that guides everyday decisions.
Outcomes and outputs
Distinguish shipped work from changed behavior, connect both through assumptions, and define measures that show whether value was created.
Opportunity solution tree
Map one outcome to customer opportunities, competing solutions, and assumption tests without turning discovery into a feature wish list.
Customer interviews
Recruit relevant participants, elicit concrete past stories, probe decisions and context, and avoid leading customers toward your preferred idea.
Synthesize interview notes
Convert customer stories into traceable observations, patterns, opportunities, and decisions without flattening contradiction or inventing prevalence.
Product requirements document
Create a concise product requirements document that aligns problem, evidence, scope, behavior, measures, risks, and unresolved decisions.
Stories and acceptance criteria
Describe user value in a concise story, then define observable acceptance criteria for rules, states, failures, and boundaries.
Minimum viable scope
Define the smallest coherent product experience that tests a risky value assumption without dropping trust, safety, or essential workflow steps.
Product discovery sprint
Time-box discovery around a consequential question, matched research methods, rapid synthesis, assumption tests, and an explicit decision.
Product experiments
State a falsifiable hypothesis, choose a credible comparison and measure, protect participants, and define the decision before observing results.
Product success metrics
Select a small metric set that represents customer value, business contribution, causal mechanisms, and important harms.
Outcome-based roadmap
Organize a roadmap around customer and business results, current opportunities, evidence, and adaptable solution bets instead of fixed feature dates.
Manage technical debt
Make technical debt visible through product effects, risk, evidence, and options, then fund reduction alongside feature and reliability work.
Build versus buy
Compare internal development, vendor products, and hybrid options across strategic differentiation, lifecycle cost, control, risk, and exit paths.
Launch readiness review
Evaluate product quality, operations, risk, measurement, communication, rollout, and rollback through accountable evidence before launch.
Product decision memo
Record the decision, context, evidence, alternatives, tradeoffs, dissent, owner, and review trigger in a concise durable memo.
Stakeholder conflicts
Translate requests into underlying needs, evaluate them against shared strategy and evidence, decide transparently, and preserve relationships without false promises.
Product retrospective
Review evidence across discovery, delivery, launch, and outcomes, then choose owned improvements with observable follow-through.
Diagnose adoption decline
Validate the signal, localize the affected cohort and journey, test competing explanations, and choose a response proportional to evidence.
Product interview case
Practice structuring ambiguous product cases through clarification, users, problems, strategy, solutions, metrics, risks, and concise communication.