- How to use this list
- 1. RICE — Reach x Impact x Confidence / Effort
- 2. ICE — Impact x Confidence x Ease
- 3. Kano Model
- 4. Jobs to Be Done (JTBD)
- 5. North Star Metric
- 6. HEART — Happiness, Engagement, Adoption, Retention, Task success
- 7. MoSCoW — Must, Should, Could, Won't
- 8. Value vs Effort 2x2
- 9. RACI — Responsible, Accountable, Consulted, Informed
- 10. OKRs — Objectives and Key Results
- 11. Hooked Model (Trigger → Action → Reward → Investment)
- 12. Opportunity Solution Tree (Teresa Torres)
- How to pick the right framework
- Anti-patterns
- Practice these in a mock
How to use this list
These 12 frameworks are not equal — some are for prioritisation, some for research, some for measurement, some for stakeholder alignment. Read the "when to use" line for each before you deploy it. Frameworks are tools, not badges of seniority.
1. RICE — Reach x Impact x Confidence / Effort
When to use: quarterly feature prioritisation with a data-informed team.
How: for each candidate feature, score Reach (users touched per period), Impact (0.25-3, small to massive), Confidence (0-100%), Effort (person-months). Divide. Rank.
Watch out for: false precision. RICE looks quantitative but every input is a guess. It is a discussion tool, not an oracle.
2. ICE — Impact x Confidence x Ease
When to use: early-stage teams that need speed over rigour.
Same idea as RICE, no reach denominator. Faster to run, easier to game. Great for growth teams and hackathons.
3. Kano Model
When to use: deciding which features delight vs which are hygiene.
Bucket features into: Must-haves (their absence causes churn), Performance (more = better), Delighters (unexpected value), Indifferent (do not bother), Reverse (users hate them).
4. Jobs to Be Done (JTBD)
When to use: discovery, positioning, and finding the real customer motivation.
Instead of "our user is a 25-year-old marketer", ask "what job is she hiring our product to do?" People do not buy a drill, they hire a hole in the wall. Great for reframing tired product debates.
5. North Star Metric
When to use: aligning a whole product org on a single measure of value.
One metric that captures customer value delivered. Examples: Airbnb — Nights Booked; Spotify — Time Listening; PhonePe — Successful transactions. Pair every North Star with 2-4 guardrail metrics.
6. HEART — Happiness, Engagement, Adoption, Retention, Task success
When to use: setting up a UX measurement stack from scratch.
Google's HEART framework forces you to pick a signal for each row and each stage of the funnel. Especially useful for pre-launch OKR-setting.
7. MoSCoW — Must, Should, Could, Won't
When to use: scoping a single release with fixed date or capacity.
Very useful in Agile teams and BA-heavy environments. See our BA career roadmap for how MoSCoW shows up in day-to-day requirements work.
8. Value vs Effort 2x2
When to use: a 30-minute whiteboard call to align a team on the next 2 weeks.
Plot every candidate on a value/effort grid. Ship the quick wins, plan the big bets, kill the low-value work. Simple and effective.
9. RACI — Responsible, Accountable, Consulted, Informed
When to use: messy cross-functional launches where ownership is unclear.
List every task, then tag one Accountable person per row. Solves the "everyone thought someone else owned it" failure mode.
10. OKRs — Objectives and Key Results
When to use: quarterly planning and cross-team alignment.
One Objective (qualitative), 2-4 Key Results (measurable). Set 60-70% confidence — if you hit 100%, they were too easy. OKRs work when the org actually commits; they fail when they become vanity docs.
11. Hooked Model (Trigger → Action → Reward → Investment)
When to use: designing habit-forming loops in consumer products.
Especially useful for retention-focused PMs in fintech, social and gaming. Do not use it to build dark patterns.
12. Opportunity Solution Tree (Teresa Torres)
When to use: mapping discovery to delivery.
Start with the desired outcome, branch into opportunities (customer needs), branch each into 2-3 candidate solutions, and design experiments for each. The best modern framework for continuous discovery.
How to pick the right framework
- Ranking features? → RICE or ICE
- Deciding delighters vs table-stakes? → Kano
- Understanding user motivation? → JTBD
- Setting product-wide alignment? → North Star + OKRs
- Scoping a release? → MoSCoW
- Clarifying ownership? → RACI
- Structuring discovery? → Opportunity Solution Tree
Anti-patterns
Do not spray five frameworks over one decision. Do not fake precision in RICE by inventing numbers. Do not use OKRs if leadership will not commit. Do not use JTBD to avoid quantitative work.
Practice these in a mock
The fastest way to internalise frameworks is to use them in a mock interview. Book a 60-minute mock PM interview on Topmate and we will grade your framework fluency across product sense, estimation and strategy.
Turn what you learned here into a real portfolio
The PM Codex BA Practical Masterclass ships every student with 30+ interview-ready product artifacts. 6 weeks, live cohort, lifetime access.
See the curriculum →