Building the Product

How do I say no to feature requests without losing customers?

A starting point

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 underlying problem first. Score it against everything else on the list; if it doesn't move a key outcome, it waits. Saying no to good ideas is how you have time to ship the great ones.

Go deeper

Hand-picked from around the web, each with a note on why it earns your time.

3 resources 3 link-checked Listen Read

Listen

🎧 Podcast
✓ Link checked India Free Intermediate

Why we picked it 150+ candid conversations with Indian founders and investors on how they actually found their idea and their first customers, in the Indian market context that YC and a16z never speak to. Real playbooks from people building here.

The Neon Show (formerly 100x Entrepreneur)

On Apple Podcasts by Siddhartha Ahluwalia podcast series (45-90 min episodes)

  • How Indian SaaS and consumer founders validated in a price-sensitive market.
  • First-customer and early-GTM stories specific to India.
  • Investor perspective on what early signal looks like locally.
Listen on Apple Podcasts podcasts.apple.com →

Read

📄 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.

RICE: Simple Prioritization for Product Managers

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 →
📖 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.

Continuous Discovery Habits

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 →

People also ask

How do I decide what to build next? Prioritize outcomes, not output, and use a simple scoring frame like RICE, Reach x Impact x Confidence, divided by Effort, to compare ideas honestl... Intermediate 2 resources → 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 know when something we shipped is actually working versus just launched? Launching is an event, working is a signal, and founders confuse the two constantly. Before you ship a feature, write down the one number you expec... Intermediate 3 resources →