Prioritization Frameworks
How decisions about what matters most get made
Most organizations have more than one prioritization framework in play at any given time. The frameworks used by teams on the front lines to prioritize day-to-day decisions often differ from the frameworks used by leadership to prioritize big bets, strategic initiatives, or cross-functional investments. This is normal. Different scopes, time horizons, and decision rights naturally lead to different approaches.
For this activity, the goal is to simply catalog the prioritization frameworks currently used across your company. We are not trying to score them, compare them, or argue for one over another. Instead, we want to understand:
- Which frameworks exist in practice
- Where they show up (team-level, function-level, leadership-level)
- What they are used for
- How formal or informal they are
- How people actually make trade-offs today
Some teams may use structured models like WSJF, RICE, MoSCoW, or Impact vs. Effort. Others may use a theme-based approach. Others may rely on what leadership wants, or what a major customer needs, or what is feasible given technology constraints. And often, prioritization varies by artifact—roadmaps, backlogs, experiments, customer commitments, OKRs, platform work, etc.
The purpose is to see the landscape, not judge it.
Approach
1. Identify the frameworks currently in play
Examples include, but are not limited to:
- WSJF (Weighted Shortest Job First)
- RICE
- Impact vs. Effort matrix
- MoSCoW
- HiPPO
- Buy-a-Feature
- Theme-Based Prioritization
- “Leadership Top 5”
- “What Sales Needs Now”
- “What Tech Can Actually Deliver”
- “What's on fire this week”
2. Describe where each framework is used
For each one, capture:
- Which teams or groups use it
- What decisions it applies to
- What types of work it prioritizes
- Whether it is formal, informal, or somewhere in between
3. Capture how the framework actually works in practice
Examples:
- WSJF for quarterly planning, but tickets are prioritized ad hoc
- RICE used for shaping opportunities, but ignored during sprint planning
- Impact vs. Effort used during ideation but not roadmapping
- Leadership uses a separate criteria set for strategic bets
4. Note any gaps or conflicts
- Does the company have a unified way of talking about importance?
- Do functions prioritize differently?
- Are some frameworks used only ceremonially?
- Are there mismatches between “official” and “unofficial” methods?
Example Framework Catalog
| Framework Name | Where It's Used | What It Prioritizes | How It Works in Practice | Notes |
|---|---|---|---|---|
| RICE | Product teams | New ideas and features | Used during shaping to compare options, but not updated once work starts | Simple, familiar, and works fine for early-stage decisions |
| Financial Lens (ROI / Budget Impact) | Executive leadership + Finance | Big bets, annual planning, major investments | Leaders look at expected ROI, cost, and budget impact to decide what moves forward | Often overrides team-level frameworks when funding or headcount is tight |
You're Done When
- You've listed all frameworks currently used (formal and informal).
- You've documented where each is applied and what it prioritizes.
- You've captured how each framework actually works in practice.
- You've surfaced mismatches and the moments when one lens overrides another.
- You've compiled a prioritization framework catalog.