Frameworks and reasoning tools for product managers who make hard decisions.
A practical framework for product managers who need to make high-stakes decisions with incomplete information. Move beyond analysis paralysis with structured reasoning under uncertainty.
PM and PO are fundamentally different roles with different scope and accountability. Conflating them leads to underspec'd hiring and teams that don't know who is responsible for strategy.
A product manager's guide to strategic disagreement. Learn the pre-negotiation analysis, language patterns, and influence techniques that protect both your product and your relationships.
Competing priorities are a governance problem: leadership hasn't established which decisions are binding and which are negotiable. The fix is a priority framework that makes trade-offs explicit.
Product teams collapse discovery and delivery into a single process. Separating them is a governance issue: you need a decision gate that forces clarity about what you're solving before you commit to delivery.
OKRs fail because teams optimize for the score instead of the outcome. The core skill is writing OKRs that align incentives and remain true when the business changes.
A modern framework for assessing product-market fit beyond Sean Ellis's 40% rule. Systematic validation for product managers who need to make build-or-pivot decisions with confidence.
Technical debt is a strategic liability, not an engineering problem. PMs must quantify its cost and enforce debt repayment as a governance mechanism.
Most sprint reviews are show-and-tell. An effective one surfaces what you learned, what assumptions held, and what changes next. Structure it for learning, not demos.
Managing up is not politics. It's a mechanism for clarifying expectations and building trust. Do it by presenting data, naming assumptions, and proposing logic.
PMF is not a feeling. It's when your product satisfies a need in a way your market is willing to pay for. Measure it with retention, NPS, and churn trajectory—not vanity metrics.
RICE, ICE, and MoSCoW are cargo-cult frameworks. They fail because they compress non-commensurable variables into a number. Use ranking by consequence instead.
A product roadmap is a mechanism for allocating authority and attention, not a timeline. Build one by clarifying strategic bets, sequencing dependencies, and publishing the theory of change.
Use the problem-solution-reaction sequence to extract actionable evidence instead of collecting validation or complaints.
Use three decision gates—unit economics, evidence quality, and calendar risk—to eliminate the guesswork from pivot decisions.
The structured process for validating or disproving what customers actually need before you build.
Use a conviction ladder to separate opinions from evidence, then surface the real constraint—capital, risk tolerance, or timeline—driving disagreement.
The structured approach to entering a new PM role: diagnostic phase, stakeholder mapping, and decision rights clarification.
The structure for writing strategy that drives prioritization, aligns teams, and survives contact with reality.
Track three tiers of metrics—unit economics, engagement velocity, and health signals—to avoid metric theater and catch problems early.
A systematic framework for deciding whether to build, buy, or integrate third-party solutions based on strategic advantage and cost.
Use three decision lenses—leverage, evidence, and capacity constraints—to prioritize ruthlessly instead of debating opinions endlessly.
The framework for declining feature requests while maintaining credibility and aligning stakeholders on your actual priorities.