2x2 Prioritize

Use this when you have a set of features, initiatives, tasks, or ideas that need prioritization and want a visual 2x2 matrix framework. Supports common axes (effort/impact, urgency/importance, confidence/value) or custom axes. Produces a categorized placement with rationale and a recommended action sequence.

Related resources: 2x2-prioritization-guide.md -- 4-step Quick Start Guide for running a 2x2 prioritization exercise (standalone, printable).

Process

Step 1: Gather inputs

Ask the user:

1. Items to prioritize — List the features, initiatives, stories, or ideas. For each, provide a brief description and any known context (size estimate, user demand, strategic alignment).
2. Axes — Which 2x2 framework do you want?
   • Effort vs. Impact (default) — horizontal: effort/cost to deliver; vertical: expected impact on users or business.
   • Urgency vs. Importance (Eisenhower) — horizontal: importance to long-term goals; vertical: time sensitivity.
   • Confidence vs. Value — horizontal: how confident you are in the idea; vertical: expected value if it works.
   • Custom — define your own two axes and what high/low means for each.
3. Decision context — What decision will this prioritization inform? (Next sprint, quarterly roadmap, resource allocation, feature cuts.)
4. Constraints — Any fixed commitments, deadlines, dependencies, or capacity limits?

Step 2: Identify which personas are affected

Before prioritizing, prompt the user:

Persona check: Which user persona(s) does each item serve? If you have defined personas (e.g., from /persona-create or /persona-draft), name them. If not, describe the key user types briefly.

This grounds your prioritization in real user impact and prevents the matrix from reflecting only internal priorities.

Step 3: Score each item

For each item, assess placement on both axes using a 3-point scale (High / Medium / Low). Present the reasoning:

## 2x2 Prioritization — (Context/Sprint/Roadmap Name)

**Date:** (Date)
**Framework:** (Effort vs. Impact / Urgency vs. Importance / Custom)
**Decision context:** (What this informs)

---

### Item Scoring

| # | Item | Axis 1 (Horizontal) | Axis 2 (Vertical) | Quadrant | Persona(s) Served |
|---|---|---|---|---|---|
| 1 | (Item name) | (H/M/L + brief rationale) | (H/M/L + brief rationale) | (Quadrant name) | (Persona names) |
| 2 | (Item name) | (H/M/L + brief rationale) | (H/M/L + brief rationale) | (Quadrant name) | (Persona names) |

Step 4: Generate the 2x2 matrix

Produce the matrix with quadrant labels and item placement:

### 2x2 Matrix

(For Effort vs. Impact — the default framework:)

                    High Impact
                         |
      QUICK WINS         |      BIG BETS
      (Low effort,       |      (High effort,
       high impact)      |       high impact)
       → Do first        |       → Plan and invest
                         |
  Low Effort ————————————+———————————— High Effort
                         |
      FILL-INS           |      MONEY PIT
      (Low effort,       |      (High effort,
       low impact)       |       low impact)
       → Do if easy      |       → Avoid or defer
                         |
                    Low Impact

### Placement

**Quick Wins** (do first):
- (Item) — (1-line rationale for placement)
- (Item) — (1-line rationale)

**Big Bets** (plan and invest):
- (Item) — (1-line rationale)

**Fill-Ins** (do if capacity allows):
- (Item) — (1-line rationale)

**Money Pit** (avoid or defer):
- (Item) — (1-line rationale)

For other frameworks, adjust quadrant labels:

• Urgency/Importance: Do Now, Schedule, Delegate, Eliminate
• Confidence/Value: Proven Wins, High-Value Bets, Safe Bets, Skip
• Custom: User-defined labels

Step 5: Recommend an action sequence

Based on the matrix, produce a prioritized action list:

### Recommended Action Sequence

1. **(Item)** — (Quadrant). (Why this should go first — e.g., "Quick win that unblocks 2 downstream items.")
2. **(Item)** — (Quadrant). (Rationale.)
3. **(Item)** — (Quadrant). (Rationale.)

### Items to Defer or Drop

- **(Item)** — (Why this doesn't make the cut right now.)

### Uncertainty Flags

- **(Item)** — Placement depends on (unknown factor). Recommend (investigation or experiment) before committing.

Step 6: Review and validate

Ask the user:

• Do the axis scores feel right? Any items you'd move?
• Does the action sequence match your capacity and timeline?
• Are there dependencies between items that change the order?
• Any items where the team would disagree on placement?

Adjust as needed. A 2x2 is a conversation tool — the value is in the discussion, not just the diagram.

Related skills

• /rice-score — if you need quantitative RICE scoring instead of a 2x2 visual.
• /moscow — if you need a MoSCoW categorization (Must/Should/Could/Won't).
• /backlog-refine — for ongoing backlog health and ordering.
• /now-next-later-roadmap — to translate prioritization into a stakeholder-ready roadmap.
• /experiment-design — for items flagged as uncertain bets that need validation.

Output location

Present the scored table, 2x2 matrix, and action sequence as formatted text in the conversation. The user copies the matrix into their planning documentation or shares it in team discussions.