Tag: Product Management

Achieving outsized returns on new product investments by concentrating bets and measuring outcomes instead of features.

Kent Beck's model for understanding how products move through Explore, Expand, and Extract phases, each requiring different strategies, risk tolerances, and investment approaches.

A collaborative technique for surfacing and prioritizing the riskiest assumptions behind a product idea using a 2x2 grid of importance vs. evidence.

The Desirability/Viability/Feasibility model for balancing business, user, and technical impacts.

Teresa Torres' framework for building a sustained discovery practice through weekly customer touchpoints, opportunity solution trees, and assumption testing.

The smallest group that holds every perspective required to make good product decisions without waiting on anyone outside the room.

Structured conversations with users and customers designed to uncover problems, motivations, and context rather than validate your existing ideas.

The practice of regularly using what you build so you experience it the way your customers do; commonly called dogfooding.

Running parallel discovery and delivery tracks so that learning and building happen continuously.

A structured conversation technique for decomposing user story steps into concrete examples, rules, and open questions.

Shifting from project-driven delivery to a product-oriented model grounded in outcomes over outputs.

Marty Cagan's foundational text on how strong product organizations actually work, including the product trio, continuous discovery, and the difference between product and feature teams.

Leading indicators tell you if you're on track; lagging indicators tell you when you arrived.

Practices for keeping a backlog short, groomed, and honest about what will actually get built.

The smallest product increment that delivers real user value and generates learning about whether your hypothesis is correct.

A structured rubric for scoring priorities across Necessity, Outcome Clarity, Impact, Confidence, and Effort.

A four-part template for defining an outcome with its impact, metrics, and scope.

A Now/Next/Later roadmap format organized around outcomes, impacts, metrics, and scope rather than feature timelines.

A hands-on workshop that teaches product teams to build roadmaps centered on outcomes and impact rather than feature lists.

Joshua Seiden and Jeff Gothelf's case for measuring success through behavioral outcomes rather than features shipped.

Focus on measurable changes in behavior rather than features shipped.

The failure mode where teams confuse staying busy and shipping features with creating value.

Treating an internal platform with product management discipline — roadmaps, adoption metrics, and user research with consuming teams.

A lightweight approach to building useful user personas from a few real conversations.

An immersive workshop that helps teams build a repeatable product discovery system, shifting focus from outputs to outcomes and impacts through hands-on practice with discovery techniques.

Structured tests designed to validate assumptions and hypotheses about a product idea before committing to full implementation.

The behavioral shifts that separate product-thinking teams from feature factories, spanning stakeholder interactions, planning, research, prioritization, and team structure.

Five pillars of product thinking that distinguish product-led teams from feature factories.

Mik Kersten's framework for connecting software delivery flow to business outcomes using the Flow Framework.

Outcome-based roadmaps and the roadmapping process as a continuous practice.

A reverse-engineering technique that traces features back through outcomes to business impact by asking "So what?!" at each level.

Giff Constable's practical guide to conducting effective customer interviews for product discovery and entrepreneurship.

Three strategies for more productive engineering collaboration when tackling technical debt.

A field guide for reducing the risk of product ideas through structured experimentation.

Donald Reinertsen's comprehensive treatment of flow-based product development economics.

User, Customer, and Technical outcomes — three flavors of measurable change that must stay in balance.

A visual technique for tracing paths through a story map to plan MVPs, prioritize delivery, and coordinate discovery, design, and engineering work.

The differences between project-based and product-based engineering and why it matters.

Why bad requirements are a symptom, not the root problem, and what to fix instead.