--- name: feature-prioritization description: Apply structured prioritization matrix techniques to rank features, ideas, or design decisions by two weighted criteria (e.g. user impact vs. effort, feasibility vs. ROI). Use this skill whenever a user wants to prioritize features, compare design options, rank backlog items, decide what to build next, run a prioritization workshop, or make a structured UX or product decision. Trigger on phrases like "help me prioritize", "what should we build first", "rank these features", "should we focus on X or Y", "prioritize the backlog", "run a prioritization exercise", "impact vs effort", or any request to choose between competing options in a structured way. --- # Feature Prioritization Matrix A structured, objective approach to ranking features, ideas, or design decisions using two weighted criteria — turning team opinion into a shared visual model. --- ## When to use this Use this skill when the team needs to: - Decide which features to build or design next - Compare ideas from a discovery or ideation session - Align cross-functional stakeholders on priorities - Move beyond gut-feel or HiPPO (Highest Paid Person's Opinion) decisions - Document and communicate prioritization rationale to stakeholders --- ## Core Concept A prioritization matrix is a 2D visual that plots items against two criteria. The position of each item on the chart reflects its relative priority. Items in the **top-right quadrant** (high on both axes) are the highest priority. ``` High impact | Deprioritize | ✅ Do first |----------------|---------------- Low impact | Skip | Quick wins |________________|________________ Hard Easy (effort) ``` The process works because it: - Externalizes opinions into a shared space - Prevents any one voice from dominating - Creates a documented artifact stakeholders can reference - Forces the team to agree on criteria before debating solutions --- ## Step-by-step process ### 1. Define what you're prioritizing Write each item (feature, idea, task, persona, research activity) on a separate sticky note or card. Be specific — vague items lead to vague decisions. ### 2. Choose two criteria Pick exactly two criteria that reflect both user and business goals. Common pairs: | Axis X (horizontal) | Axis Y (vertical) | |---|---| | Effort / Complexity | User impact | | Feasibility | Business value / ROI | | Time to implement | Frequency of use | | Cost | Strategic alignment | > **Rule:** Criteria must come from project goals and business needs — not personal preference. > **Tip:** Place the *best* outcome at the top-right. E.g., "Low effort" on the right, "High impact" on top. ### 3. Vote individually, by expertise Give each team member a fixed number of votes — roughly **half the number of items** being prioritized. Use **different colors per role** so votes reflect domain expertise: - Designers vote on user impact / desirability axes - Developers vote on feasibility / effort axes - Product/business stakeholders vote on ROI / strategic value Rules: - Vote silently, independently - You may stack multiple votes on one item - Only vote within your domain of expertise > **Why:** Silent individual voting prevents groupthink and anchoring bias. The loudest voice doesn't win. ### 4. Place items on the matrix Use the vote counts as a guide to collaboratively position each item on the 2D chart. Keep discussion minimal at this stage — just get items placed. ### 5. Discuss and negotiate placement Once everything is plotted, open discussion: - Are items with equal votes truly equal? - Do we agree with the extremes (highest and lowest rated)? - Why did some items get zero votes — no value, or not enough votes to go around? Move items collaboratively. End with team agreement on final positions. ### 6. Document and drive action Photograph or digitize the matrix. Produce a clear action plan: - **Top-right quadrant** → Do first - **Top-left quadrant** → High value but hard — plan carefully - **Bottom-right quadrant** → Quick wins — do if capacity allows - **Bottom-left quadrant** → Deprioritize or cut Share with stakeholders with a brief rationale for top decisions. --- ## Adapting the matrix ### More than two criteria Visualization degrades with 3+ criteria. Instead: - Split into multiple 2-criteria matrices - Plot items across all matrices - Prioritize items that consistently land in the top-right ### Weighted voting For high-stakes decisions, have voters **rank** their dots (1, 2, 3). This surfaces not just *what* people vote for, but *how much* they care — giving more signal for placement. ### Remote or async teams If the team is prone to groupthink or hierarchy bias, run voting digitally and anonymously before any shared discussion. Tools like FigJam, Miro, or even a shared spreadsheet work well. ### Continuous scales Replace high/low axes with real numbers when precision matters: - Effort in weeks or sprint points - Reach as % of user base - Revenue impact in $ --- ## Output format When facilitating a prioritization exercise, produce: 1. **Criteria summary** — the two axes chosen and why 2. **Matrix summary** — a text representation of where items landed (quadrant-by-quadrant) 3. **Recommended action plan** — top 3–5 items to pursue, with a brief rationale 4. **Open questions** — any items the team couldn't resolve and why If producing a visual artifact, use a 2x2 grid with labeled axes and quadrant labels (Do First / Plan / Quick Wins / Deprioritize). --- ## Common mistakes to avoid - **Choosing criteria based on existing favorites** — criteria must reflect goals, not justify predetermined answers - **Skipping the silent voting step** — opens the door to anchoring bias and loudest-voice dominance - **Treating the matrix as final** — it's a discussion tool, not a contract; revisit as context changes - **Using more than two criteria on one chart** — creates visual noise; use multiple charts instead - **Forgetting to share** — the artifact only has value if stakeholders can see and reference it