Building the Product

How do I decide what to build next?

A starting point

Prioritize outcomes, not output, and use a simple scoring frame like RICE, Reach x Impact x Confidence, divided by Effort, to compare ideas honestly. The score's real value is forcing you to admit how low your confidence is on pet projects. When in doubt, build what your best customers are already pulling out of your hands.

Go deeper

Read

📄 Article
Free Intermediate

RICE: Simple Prioritization for Product Managers

From Intercom Blog by Sean McBride ~12 min read

Why we picked it

The original, primary source where the RICE framework was introduced, cite this, not the SEO reposts. The clearest way to compare hard-to-compare feature ideas.

  • Score = (Reach x Impact x Confidence) / Effort.
  • Forces you to quantify confidence and expose low-confidence pet projects.
  • Comparable scores let you rank features objectively.
Open intercom.com →
📄 Article
Freemium Intermediate

Prioritizing

From Lenny's Newsletter by Lenny Rachitsky ~15 min read

Why we picked it

The canonical PM-community reference on choosing what to build next, from the most-read product newsletter. A pragmatic overview of scoring frameworks and how to actually use them.

  • Prioritize around outcomes, not output.
  • Use scoring frameworks (RICE/DRICE) to compare ideas objectively.
  • Deeper investigation kills 'promising' bets and elevates quiet high-ROI winners.
Open lennysnewsletter.com →

People also ask

How often should an early-stage startup ship? Ship weekly, at least, cadence is a competitive advantage because faster loops mean faster learning. You haven't really started until you launch, a... Beginner 2 resources → How do I build a roadmap without over-planning? Work in short fixed cycles with variable scope, Basecamp's Shape Up runs on six-week bets, not a rigid multi-quarter Gantt chart. Make a few bets y... Intermediate 2 resources → How do I keep talking to users while I'm heads-down building? Make discovery continuous, not a one-time phase: interview a customer or two every single week, even in a build sprint. Teresa Torres's opportunity... Intermediate 2 resources → How do product teams keep a consistent shipping rhythm as they grow? Separate your planning cadence from your execution cadence and lean on async updates instead of endless meetings. A predictable operating rhythm, w... Advanced 2 resources → How do I say no to feature requests without losing customers? Anchor every 'no' to the outcome you're chasing and the customers you're building for, most requests are solutions in disguise, so dig for the unde... Intermediate 3 resources →