12 Product Management Frameworks Every PM Should Know

Frameworks are thinking tools, not rules to follow blindly. The best PMs reach for the right one at the right moment and discard the rest. Here are twelve frameworks worth knowing, grouped by the decision they help you make.

Prioritization

• RICE — score initiatives by Reach, Impact, Confidence, and Effort. Best when you need a defensible, comparable ranking across many ideas.
• MoSCoW — sort into Must, Should, Could, and Won't. Great for scoping a single release with stakeholders.
• Kano model — classify features as basic expectations, performance needs, or delighters. Use it to balance must-haves against differentiators.
• Cost of Delay — quantify the economic impact of not shipping something yet. Powerful for sequencing time-sensitive work.

Discovery and problem framing

• Jobs To Be Done (JTBD) — frame products around the progress a user is trying to make, not demographics. Keeps you focused on the real problem.
• Opportunity Solution Tree — connect a desired outcome to opportunities and then to solutions. Prevents jumping to features before understanding problems.
• The Five Whys — repeatedly ask "why" to reach a root cause instead of a symptom.

Strategy and positioning

• North Star Framework — pick one metric that captures the value your product delivers, and map the inputs that drive it.
• Working Backwards — start by writing the press release and FAQ for a finished product. Forces clarity on customer value before building.
• Porter's Five Forces — assess competitive dynamics when entering or defending a market.

Execution and measurement

• OKRs — set ambitious Objectives with measurable Key Results to align teams around outcomes, not output.
• AARRR ("Pirate Metrics") — track Acquisition, Activation, Retention, Referral, and Revenue to find where your funnel leaks.

How to actually use frameworks

A framework is only useful if it changes a decision. Three rules keep them honest:

1. Match the framework to the question. Don't run RICE when the real problem is that you haven't talked to users yet.
2. Use the lightest tool that works. A two-line problem statement often beats an elaborate scoring spreadsheet.
3. Treat outputs as inputs to judgment. Scores inform debate; they don't end it.

Where to go from here

Knowing frameworks is easy; knowing when to apply each one is the craft. That judgment is built through structured practice on real problems — which is the foundation of the Core Product Manager track at Mentra Academy.

For more, see our guides on how to become a product manager and breaking into AI product management.