Shortcut keeps your Stories organized with Epics, Iterations, and Labels. But when it comes to deciding which Stories matter most, Shortcut gives you a Priority dropdown (Urgent, High, Medium, Low) and nothing else. That is not a scoring system. It is a guessing system.
This guide shows you how to add RICE scoring to your Shortcut workflow so your team ships what actually moves the needle.
Why RICE Works for Shortcut Teams
Shortcut is popular with engineering-forward teams that want a clean, fast project tracker. These teams often skip formal prioritization because the tool does not enforce one. RICE fills that gap.
RICE scores each feature on four dimensions: Reach (how many users), Impact (how much it moves your metric), Confidence (how sure you are), and Effort (how many person-weeks). The formula produces a single number you can sort on.
Setting Up the Workflow
Step 1: Identify candidates. Pull 15-25 Stories from your Shortcut backlog that are competing for the next Iteration. You do not need to score everything. Focus on the items your team is actually debating.
Step 2: Score in IdeaPlan. Open the RICE Calculator and enter values for each candidate. Be specific about Reach. "A lot of users" is not a number. "2,000 monthly active users in the affected segment" is.
Step 3: Add scores to Shortcut. Create a Custom Field called "RICE Score" (number type) in Shortcut. Paste the calculated score into each Story. Custom Fields are available on Shortcut's Team plan and above.
Step 4: Sort and commit. In your Shortcut workspace, create a saved search sorted by the RICE Score field. Review the ranked list with your team and pull the top items into the next Iteration.
RICE vs. Shortcut's Built-in Priority
Shortcut's Priority field is a four-level dropdown. The problem is calibration. When every PM on the team marks their pet feature as "High," you end up with 40 high-priority Stories and no clear ordering.
RICE replaces the dropdown with math. Two PMs might disagree on whether a feature is "High" priority, but they can discuss whether Reach is 500 or 5,000. That discussion is more productive.
If RICE feels too heavyweight, try ICE scoring first. ICE uses three factors (Impact, Confidence, Ease) and is faster to calculate. It sacrifices the Reach dimension, which matters less for early-stage products with small user bases.
Tips for Shortcut-Specific Workflows
Use Shortcut Labels to mark Stories as "RICE-scored" or "needs-scoring." Create a filter that shows unscored Stories in your backlog. This keeps your scoring process visible.
For teams using Shortcut Milestones, attach RICE scores at the Milestone level to compare strategic bets, not just individual Stories. Score each Milestone by aggregating the top Stories within it.
Shortcut's Iteration velocity view shows completed points per cycle. Pair this with RICE scores to check whether your team consistently ships high-RICE items or burns capacity on low-impact work.
Consider using weighted scoring if your team needs additional criteria beyond RICE's four dimensions. Some teams add "strategic alignment" or "revenue impact" as extra factors.
Scaling Across Multiple Shortcut Teams
Organizations with multiple Shortcut teams should standardize RICE definitions. Write a one-page guide defining what each Impact level (1, 2, 3) means in your context. Share it in your team wiki.
Cross-team prioritization becomes possible when everyone uses the same scale. A RICE score from the growth team and one from the platform team are directly comparable.
Review the prioritization guide for a broader look at how scoring fits into your product process.