How to Prioritize Features When Everything Feels Important

This week’s template talks about how to cut through the chaos and make confident product decisions, even when everything feels like a must-have.

🤯 The Problem

You’ve got 17 features on the board.

Your users want 5. Your investor wants 2. Your gut wants to ship something cool.

Sound familiar?

When everything feels urgent, nothing gets done, or worse, you build the wrong thing.

🎯 The 3-Point Prioritization Lens

Use this lens for every feature:

Lens	Ask Yourself	Example
1. Impact	Will this move the needle on a key metric?	“Will this increase signups, retention, or revenue?”
2. Confidence	Do we have data or strong signals backing this?	“Have users asked for this 3+ times?”
3. Ease	Can we ship this quickly and cleanly?	“Is this a 1-week build or a rabbit hole?”

ICE Score = Impact × Confidence × Ease

Higher score = higher priority.

🧮 Example: Prioritizing Two Realistic Features

Feature A: Add Slack integration for notification alerts

Impact: 7 (Would improve retention for teams already using Slack)
Confidence: 6 (Requested by a few users, especially teams)
Ease: 4 (Requires external API work and testing)
ICE Score: 7 × 6 × 4 = 168

🤯 The Problem

🎯 The 3-Point Prioritization Lens

🧮 Example: Prioritizing Two Realistic Features

Feature A: Add Slack integration for notification alerts

Feature B: Add a quick-start template gallery for new users