The Product Manager’s Atlas
Domain 09 Β· 13 notes

The Frameworks Toolkit

The frameworks I actually reach for, and when each one is just theater.

4 min readΒ·804 words

This is my opinionated index of every framework in the Atlas, the tools I actually reach for, grouped by the job they do. I keep them in one place because the most common framework mistake is not picking the "wrong" one. It is not knowing which job you are doing, so you grab whatever is fashionable and start filling in its boxes as if the boxes were the answer.

β–²A framework is a tool, never a box to fill in

Frameworks do not produce decisions. They produce structured arguments. They force your criteria into the open and make your reasoning auditable instead of political. The output of any of these is an input to judgment, not a substitute for it. The moment a team treats "we filled in the RICE sheet" or "we ran a SWOT" as having decided something, the tool has become theater. Use them to force the conversation, then bring taste. And pick a few you will use consistently, because framework-hopping every quarter destroys the one real benefit, which is comparability over time.

#How to read this index

Find the job to be done, then the tool. Many frameworks live in other domains (discovery tools in Customer Insight, strategy tools in Product Strategy), but they are all indexed here so this is the one map you need.

#Prioritize: choosing what to do, and how hard

FrameworkOne-line jobHome
RICE and Scoring ModelsRank comparable features by Reach Γ— Impact Γ— Confidence Γ· EffortStrategy
The Impact-Likelihood MatrixFast portfolio triage: Home Runs vs Stuff You Shouldn't Be Doinghere
The Kano ModelWhat kind of value: basic, performance, or delighthere
MoSCoW PrioritizationScope a release: Must / Should / Could / Won'there
The Eisenhower MatrixPersonal/team triage by urgency Γ— importancehere
The LNO FrameworkHow much effort a task deserves once it's chosenhere
The Initiative PyramidOrganize bets by risk and escalation levelStrategy
Prioritization FrameworksThe meta-note: matching method to decision altitudeStrategy

#Discover: finding what's worth building

FrameworkOne-line jobHome
Jobs To Be DoneFrame demand around the job, not the demographicCustomer Insight
The Opportunity Solution TreeMap outcome β†’ opportunities β†’ solutions β†’ experimentsCustomer Insight
Build-Measure-Learn and the MVPLearn cheaply under uncertainty; the MVP is an experimenthere
Hypothesis-Driven DevelopmentTurn beliefs into falsifiable bets with kill criteriahere
Experimentation and A-B TestingThe rigorous read on whether a hypothesis heldCustomer Insight

#Strategize: where to play and why you'll win

FrameworkOne-line jobHome
The DHM ModelStrategy should Delight, be Hard-to-copy, Margin-enhancingStrategy
The North Star FrameworkOne value metric + the inputs that move itStrategy
OKRs and Goal-SettingSet and track outcome-based goalsStrategy
SWOT and Porter's Five ForcesClassic company/market lenses, and their limits for producthere
The Initiative PyramidRisk-tiered initiative planning and escalationStrategy

#Decide: making the call and shipping it

FrameworkOne-line jobHome
The 10-50-90 Execution FrameworkMy execution OS: phases Γ— confidence Γ— rolesExecution
RACI and Decision RightsWho actually gets to make each callExecution
Sound Product Decision-MakingOne-way vs two-way doors; bias to actionExecution
theScore Product PrinciplesPre-made decision rules for the teamhere
Writing Good Product PrinciplesThe how-to for authoring your ownhere

#Focus: allocating yourself and assessing your craft

FrameworkOne-line jobHome
The LNO FrameworkMatch effort to leverage; stop gold-plating overheadhere
The Three Levels of Product WorkImpact / Execution / Optics, and why teams talk past each otherhere
The Eisenhower MatrixDefend Quadrant-2 important-not-urgent timehere
The PM WheelSelf-assess the shape of your skillshere
The PM Competency ModelThe rigorous, leveled competency mapIntroduction

#Attribution

I built The Impact-Likelihood Matrix and theScore Product Principles, and The 10-50-90 Execution Framework is theScore's. The rest belong to the people who created them: Shreyas Doshi (LNO and the three levels), Petra Wille (The PM Wheel), Noriaki Kano (The Kano Model), Eric Ries (Lean Startup), Dai Clegg (MoSCoW), Eisenhower/Covey, Humphrey (SWOT) and Porter (Five Forces). I keep the credit for a practical reason and not just a polite one. Borrowed frameworks carry their authors' assumptions, and knowing the source is how you know the limits.

#Continue Reading