# If Your Boss Asks You To... ! [ rw-book-cover] (https://pbs.twimg.com/profile_images/1602541464851980288/Stnr4-Bl.png) URL: https://twitter.com/nurijanian/status/1887848793535840446 Author: @nurijanian on Twitter  ## AI-Generated Summary None ## Highlights > If your boss asks you to do a RICE score, you probably feel like throwing your laptop out the window. > I used to hate it too. Then I discovered that 90% of what makes a good RICE score isn't math at all. > Here's what I learned after 5 years of mentoring overwhelmed PMs 📊 > [1/20] ([View Tweet](https://twitter.com/nurijanian/status/1887848793535840446)) > First, let's address the elephant in the room: > If you're feeling overwhelmed about getting the numbers "right", you're not alone. > Your boss doesn't expect perfect numbers. They want structured thinking. > Here's how to deliver that: > [2/20] ([View Tweet](https://twitter.com/nurijanian/status/1887848805493801188)) > The biggest mistake new PMs make: > If they try to be too precise, they get paralyzed. > If they're too vague, they lose credibility. > The solution? > Start with ranges, not exact numbers. > Here's exactly how: > [3/20] ([View Tweet](https://twitter.com/nurijanian/status/1887848817300811955)) > Let's break down RICE scoring for your first time: > R = Reach (users affected) > I = Impact (effect per user) > C = Confidence (how sure are you) > E = Effort (engineering time) > If you're new, focus on relative numbers first. > Example coming up: > [4/20] ([View Tweet](https://twitter.com/nurijanian/status/1887848828994470271)) > For REACH: > If you have 10,000 users total: > Instead of saying "2,457 users will use this" > Say: "20-30% of users will encounter this feature" > This is easier to defend and actually more honest. > [5/20] ([View Tweet](https://twitter.com/nurijanian/status/1887848840692433138)) > For IMPACT: > Don't get stuck on exact metrics. > Instead, use this simple scale: > 3 = Game-changing > 2 = Significant improvement > 1 = Minor improvement > 0.5 = Minimal effect > This works for your first few scores. > [6/20] ([View Tweet](https://twitter.com/nurijanian/status/1887848852394500565)) > For CONFIDENCE: > 100% = We've done this before > 80% = Clear data supports this > 50% = Best guess, could be wrong > 20% = Many unknowns > Pro tip: If your confidence is below 50%, that's a sign you need more research first. > [7/20] ([View Tweet](https://twitter.com/nurijanian/status/1887848864797118880)) > For EFFORT: > Don't overthink it. > Ask your tech lead: > "In developer-weeks, is this a: > - 1-2 week thing > - 1 month thing > - Quarter-long project" > Then use those numbers directly. > [8/20] ([View Tweet](https://twitter.com/nurijanian/status/1887848876553724099)) > Now, for product leaders reading this: > If your PM is doing RICE scoring for the first time: > - Help them with ranges > - Focus on reasoning over precision > - Create safe space for uncertainty > They'll get more precise with experience. > [9/20] ([View Tweet](https://twitter.com/nurijanian/status/1887848888197091738)) > Common objection: "But other teams have exact numbers!" > Remember: > If you're new to RICE, starting with ranges helps you: > - Think clearly > - Defend your logic > - Improve with feedback > Exact numbers come with experience. > [10/20] ([View Tweet](https://twitter.com/nurijanian/status/1887848900008292711)) > Here's what your first RICE spreadsheet should look like: > Feature: Login Improvement > Reach: 90-100% (all users) > Impact: 2 (significant) > Confidence: 100% (done before) > Effort: 2 weeks > Simple, clear, defensible. > [11/20] ([View Tweet](https://twitter.com/nurijanian/status/1887848911634874821)) > The tension most PMs face: > If you make the math too complex, you'll get stuck. > If you make it too simple, you'll miss insights. > The solution: > Start simple, add complexity as you learn. > [12/20] ([View Tweet](https://twitter.com/nurijanian/status/1887848923303489742)) > When presenting your first RICE score: > Lead with: "Here's our initial framework..." > Not with: "These are the final numbers..." > This gives you room to improve based on feedback. > [13/20] ([View Tweet](https://twitter.com/nurijanian/status/1887848935068471354)) > Most important rule: > Document your assumptions. > If you estimate 30% reach: > Write down WHY you think it's 30%. > This helps you improve over time. > [14/20] ([View Tweet](https://twitter.com/nurijanian/status/1887848946732876078)) > A secret about RICE scoring: > If it's your first time, your boss mainly wants to see: > - Structured thinking > - Clear assumptions > - Willingness to improve > The exact numbers matter less than you think. > [15/20] ([View Tweet](https://twitter.com/nurijanian/status/1887848958468509914)) > For those who want to dive deeper: > I've collected proven templates and prompts for prioritization in https://t.co/xfskIcNZmt > They're especially helpful for first-time scoring. > [16/20] ([View Tweet](https://twitter.com/nurijanian/status/1887848970078335354)) > Quick note: > If you're using AI to help with RICE calculations, I've got some tested prompts for impact sizing that work well. > https://t.co/CGqGlG8zKM > [17/20] ([View Tweet](https://twitter.com/nurijanian/status/1887848981876940953)) > Remember: > Your first RICE score won't be perfect. > That's okay. > Focus on: > - Clear thinking > - Documented assumptions > - Regular updates > The precision will come naturally. > [18/20] ([View Tweet](https://twitter.com/nurijanian/status/1887848993662935256)) > Next steps for you: > 1. Create a simple spreadsheet > 2. Use the ranges we discussed > 3. Document all assumptions > 4. Get feedback from your tech lead > 5. Iterate based on feedback > You've got this. > [19/20] ([View Tweet](https://twitter.com/nurijanian/status/1887849005394415741)) > Found this helpful? > Follow me for more practical PM advice from the trenches. > And remember: Every senior PM started with their first RICE score too. > You're exactly where you need to be. > [20/20] ([View Tweet](https://twitter.com/nurijanian/status/1887849016937041977))