Product Leader Thinking Frameworks
Product discovery, design, and team-leadership frameworks from the practitioners who built the discipline — captured as .md skill files.
Product management as a discipline barely existed in its current form before the 1990s, and the people who shaped it did so largely by writing down what they were already doing. Marty Cagan spent years inside Netscape, eBay, and HP before distilling the distinction between a product team that discovers what to build and one that simply executes a roadmap handed down from sales. Teresa Torres formalised continuous discovery — the habit of talking to customers weekly not as a research project but as an ongoing practice — after watching teams treat it as an optional phase. Don Norman's work at Apple and his foundational design books established the vocabulary of affordances and feedback that every product designer now uses without necessarily attributing it. Tony Fadell built the iPod and Nest and wrote explicitly about the mission-before-product principle that separates durable product organisations from feature factories. Melissa Perri diagnosed the build trap — the condition in which teams measure output rather than outcome and confuse shipping with solving. Kathy Sierra's Badass Users framework is the most cogent account of why optimising for user skill rather than user satisfaction produces better long-term retention. Use this collection when structuring a discovery process, preparing to hire or evaluate a PM, or diagnosing why a product that works technically is failing commercially.
How product leaders think
- Discovery over delivery — the PM's job is to discover what is worth building, not to manage the delivery of a pre-decided list; empowered teams own the problem, not the roadmap
- Continuous discovery — replace discrete research sprints with a weekly habit of customer interviews; the goal is constant opportunity awareness, not a periodic report that goes into a shared drive
- Affordances and feedback — every product element either signals what it does or tells you what happened when you used it; invisible affordances and silent feedback produce user error that gets blamed on users
- Escaping the build trap — measuring output (features shipped) rather than outcomes (problems solved) is the organisational condition that produces roadmaps nobody believes in
- Badass users — design for the user's skill growth rather than their immediate ease; users who become genuinely capable with a tool advocate for it; users who are merely satisfied switch at the first alternative
Frameworks in this category
Don Norman
Affordances & Human-Centred Design
Tony Fadell
Build, Opinion-Driven Product & The Mission
Julie Zhuo
Managing Design & The Making of a Manager
Marty Cagan
Empowered Teams & Product Discovery
Ken Kocienda
Creative Selection & Demo Culture
Teresa Torres
Continuous Discovery Habits
April Dunford
Positioning & Obviously Awesome
Melissa Perri
Escaping the Build Trap
Kathy Sierra
Badass Users & Skill Building
When to use these frameworks
- Structuring a product discovery process so that the team is continuously learning rather than building on unvalidated assumptions
- Diagnosing why a product with strong engineering is failing to retain users, grow, or receive internal prioritisation
- Evaluating or writing a product strategy that needs to hold up to scrutiny from engineering, design, and senior leadership simultaneously
- Preparing for a product review, roadmap presentation, or a senior product hiring decision
- Working out whether a product organisation is structured around output or outcomes — and identifying specifically what to change
Start here
Don Norman
Affordances & Human-Centred Design
Adjacent thinking
Frequently asked questions
Which product framework is best for someone new to product management?
Start with Cagan's empowered teams model and Torres's continuous discovery. Cagan gives you the structural distinction — teams that discover versus teams that execute — that underlies most of what goes wrong in product organisations. Torres gives you the weekly practice that makes discovery real rather than aspirational. Read Don Norman's The Design of Everyday Things alongside them for the design vocabulary; it remains the clearest account of why products feel broken even when they technically work.
Can this replace product management training or a senior PM mentor?
No. Product management is a judgement-intensive discipline learned through the specific experience of shipping products under real constraints, watching what fails, and working under senior practitioners who can diagnose what you can't yet see in your own decisions. These frameworks accelerate your vocabulary and give you mental models to apply, but they don't substitute for the feedback loop of building and shipping with accountability. Use them as preparation and scaffolding, not as a syllabus.
Are these useful for founders doing product work themselves?
Yes, particularly Cagan on discovery versus delivery, Fadell on mission-driven product, and Perri on the build trap. Founders often run product by instinct in the early stage, which works; the frameworks become most valuable at the transition point where instinct needs to become process — when you hire your first PM, when the roadmap starts being driven by sales commitments rather than user problems, or when you notice the team is shipping continuously but nothing is improving.
How do the commercial frameworks (Cagan, Torres, Dunford) fit with the design frameworks (Norman, Kocienda)?
They address adjacent problems. Cagan and Torres focus on which problems to solve and how to discover them continuously; Norman and Kocienda focus on how solutions should behave once you've decided what to build. April Dunford's positioning work sits between them — it frames how the product should be understood relative to alternatives before anyone builds anything. The most effective product teams use all three layers: discovery to find the right problem, design to solve it well, and positioning to communicate it accurately.
Save when you build a bundle.
Mix and match across categories. 4 for $14.99 (save 25%) or 10 for $29.99 (save 40%).
Browse all 512 frameworks →