Cheaper versions

Your leverage in prioritization is not voting louder. It is honest effort, a cheaper path to the same learning, and a log of why the team overrode a score.

1. Honest effort — include design, QA, migrations, feature flags, monitoring. A "one week" that is really three weeks of half-done work warps every score. See estimation.
2. Cheaper versions — "If the goal is learning whether users want X, we can Wizard-of-Oz it in three days instead of building for six weeks."
3. Risk callouts — "This touches billing; Effort 2 assumes no PCI scope creep."
4. Sequencing — "B is fast if we do the notification infra once for B and E."

When sales asks for custom roles (RICE 360 vs onboarding at 12,800), a good eng response is not "no." It is: "Full custom roles is 3 months. Role templates covering 80% of those deals is 3 weeks. Which deals actually need the full thing?"

Engineers also surface hidden coupling. Two medium RICE items that both touch the billing service may together exceed the risk budget of either alone. Call that out so the team can sequence, combine, or buy time with feature flags.

Frameworks as conversation tools

Anti-patterns: precision theater, gaming Confidence, one score to rule them all, set-and-forget scores from Q1 deciding Q3, optimizing the score instead of the user outcome.

Run a 45-minute scoring session: PM proposes Reach/Impact/Confidence; eng leads Effort; someone plays skeptic on Confidence. Revisit when discovery changes the numbers. Document why you overrode a score (deal, dependency, regulation) so the override is accountable.

Pick one framework and stick with it for a quarter so scores stay comparable. Publish the ranked list where the team can see it.

A decision log beats a spreadsheet alone

2026-03-10 Chose A (onboarding) over B (Slack).
Reason: RICE 12800 vs 5600; activation is company KR.
Override note: none.
Displaced: Slack moves to Next; depends on notif infra later.

When someone asks "why aren't we doing my feature?" you point at the log instead of re-litigating from scratch. That is how prioritization becomes a system rather than a weekly argument.

Common mistakes

• "One week" that hides QA, flags and monitoring. Every score warps.
• Saying no instead of a 3-week template that covers 80% of the deals.
• Overrides with no written reason. The Monday debate never dies.

Check yourself

Sales wants full custom roles (3 months). What's the engineer move? Offer role templates in 3 weeks covering 80% of deals. Ask which deals need the full thing.

Leadership overrides RICE to take a deal. What do you write down? The reason, next to the item. Overrides are allowed; silent ones are not.

Key takeaways

• Engineers win with accurate effort, cheaper learning paths and sequencing insights.
• Treat frameworks as structured debate, not oracles. Document overrides.
• A short decision log stops the same argument from restarting every Monday.

Further learning

RICE — IntercomPrioritization is a challenge for any product manager. How do you decide what to work on first? Here is a simple scoring system to help prioritize well.The Intercom Blog

Lenny's NewsletterDeeply researched product, growth, and career advice for product leaders, founders, and ambitious builders. Click to read Lenny's Newsletter, a Substack publication with millions of subscribers.lennysnewsletter.com

Map: prioritization.