📄 Article
✓ Link checked
Free
Intermediate
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.
From
Intercom Blog
by Sean McBride
~12 min read
- 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
✓ Link checked
Free
Intermediate
Why we picked it
Des Traynor makes the case that "no" is the product strategy, and that adding a feature for one loud customer quietly costs every other user. It gives you language to defend a tight v1 against constant requests. Short, sharp, and directly about the discipline of cutting.
From
Intercom (Des Traynor)
by Des Traynor
~8 min read
- A cohesive product with clear boundaries beats a pile of tangential features.
- Every feature you add has an ongoing cost, not just a one-time build cost.
- No single customer request is worth more than a coherent product.
Open
intercom.com →
📖 Book
✓ Link checked
Paid
Beginner
Why we picked it
The single best thing ever written on customer conversations. It teaches you to ask about the customer's life and past behaviour, not your idea, so you can't be lied to. If a founder reads one thing before talking to a single customer, it's this.
From
momtestbook.com
by Rob Fitzpatrick
~130 pages
- Talk about their life, not your idea.
- Ask about specifics in the past, not opinions about the future.
- 'That's so cool, I'd totally buy it' is a compliment, not data, dig for commitment and evidence.
Open
momtestbook.com →
📖 Book
✓ Link checked
Paid
Intermediate
Why we picked it
The definitive text on how strong product teams discover and deliver products customers love, from the most cited voice in modern product management. The reference for shipping and iterating with intent.
From
Silicon Valley Product Group
by Marty Cagan
~370 pages
- Empower teams to solve problems, not just build features.
- Run continuous discovery in parallel with delivery.
- Move from output-driven to outcome-driven roadmaps.
Open
svpg.com →
📖 Book
✓ Link checked
Paid
Intermediate
Why we picked it
The standard modern playbook for keeping discovery continuous so roadmap decisions stay grounded in real customer input, not one-off research. Exactly what founders need to stay close to users while shipping.
From
Product Talk
by Teresa Torres
~240 pages
- Start from a clear desired outcome.
- Interview customers weekly to surface opportunities.
- Use an opportunity solution tree to visualize and align your decisions.
Open
producttalk.org →
📖 Book
✓ Link checked
Free
Intermediate
Why we picked it
Basecamp's battle-tested, opinionated system for shipping meaningful work in fixed cycles without endless backlogs, a primary source, free in full. The antidote to over-planning your roadmap.
From
Basecamp / 37signals
by Ryan Singer
free online book
- Work in short cycles with a cool-down between them.
- Fix time, vary scope, use 'appetites,' not estimates.
- Make bets, not plans; no runaway backlog.
Open
basecamp.com →
📄 Article
✓ Link checked
Freemium
Intermediate
Why we picked it
Lenny addresses prioritization specifically for early startups, where the usual scoring frameworks break down and speed matters more than spreadsheets. It helps you decide what to work on when you have almost no data and everything feels urgent. Practical and grounded in how real early teams actually choose.
From
Lenny's Newsletter
by Lenny Rachitsky
~15 min read
- Heavy prioritization frameworks are usually overkill before product-market fit.
- Bias toward the few bets that could actually move whether people want the core thing.
- Shipping and learning fast matters more than perfectly ranking your backlog.
Open
lennysnewsletter.com →
📄 Article
✓ Link checked
Freemium
Intermediate
Why we picked it
A thorough, practical walkthrough of turning a messy backlog into a prioritized roadmap, from sourcing ideas to sizing them against metrics. It connects the day to day scoring to the higher level question of strategy, so you do not confuse a roadmap for a plan. Useful once you have a few people and more ideas than time.
From
Product Growth (Aakash Gupta)
by Aakash Gupta
20 min read
- Source ideas widely, then size them against clear metrics
- A roadmap is not a strategy, the strategy sits one level above it
- Commit to a few stretch outcomes rather than a long feature list
Open
news.aakashg.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
Turns the vague feeling of product-market fit into a number you can move. Ask users how they would feel if they could no longer use the product, then track the share who say 'very disappointed'. Under 40 percent means keep working. A test you can run on an idea long before you scale it.
From
First Round Review
by Rahul Vohra
~20 min read
- The 40 percent 'very disappointed' benchmark for product-market fit.
- Segment to your high-expectation customers and build for them.
- Make the fit score a metric you improve quarter by quarter.
Open
review.firstround.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
ICE (Impact, Confidence, Ease) is RICE's lighter cousin, and it is often the right tool when you are moving fast and just need to rank a pile of ideas this week. This piece explains the formula, where it shines, and its failure mode of always chasing quick wins. Handy as a faster alternative when full RICE feels like overkill.
From
Growth Method
by Stuart Brameld
12 min read
- Score each idea as Impact times Confidence times Ease
- Great for high velocity experiments where speed of decision matters
- Watch the trap of only ever picking easy low value wins
Open
growthmethod.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
Not all features move satisfaction the same way, and Kano gives you a lens to tell basics from performance features from genuine delighters. It stops you from over investing in things customers merely expect while ignoring the small surprises that earn loyalty. A useful complement to a pure scoring frame when you are weighing the emotional payoff of an idea.
From
Product School
by Carlos Gonzalez de Villaumbrosia
12 min read
- Sort features into must be, performance, and delighter buckets
- Missing basics hurts more than adding another performance feature
- Delighters are unexpected and can create outsized satisfaction
Open
productschool.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
This is a focused piece on the outcomes over output idea in our short answer, and it catches a common trap: writing goals that are really features in disguise. Pichler gives you a simple test, keep asking why, to turn a feature wish into the real result you want. Read it to make sure your roadmap describes impact, not just a list of things to ship.
From
romanpichler.com
by Roman Pichler
10 min read
- State the result you want, not the feature you plan to ship
- Ask why repeatedly to find the true outcome behind a request
- An outcome roadmap keeps the team solving problems, not ticking boxes
Open
romanpichler.com →
✍️ Essay
✓ Link checked
Free
Intermediate
Why we picked it
A tight essay separating the work of figuring out what to build (discovery) from building it well (delivery), and arguing you must do both in parallel. It reframes what to build next as an evidence question you answer with cheap tests, not a bet you make once. Short and clarifying if you tend to jump straight to shipping.
From
Silicon Valley Product Group
by Marty Cagan
8 min read
- Discovery answers what to build, delivery answers how to build it well
- Gather evidence with opt in customers before committing to production work
- Run discovery and delivery in parallel, not as strict phases
Open
svpg.com →
Why we picked it
The permission slip to recruit users by hand, do things manually, and deliver 'insanely great' experiences to your first few customers. The cheapest, most honest way to validate demand is to go get it one person at a time.
From
paulgraham.com
by Paul Graham
~15 min read
- Recruit your first users manually, don't wait for them to come.
- A tiny group of users who love you beats a big group who like you.
- Manual, unscalable effort early is a feature, not a failure.
Open
paulgraham.com →
