Triage Component Requests With RICE, Not Volume
Route a component request by evaluating RICE evidence and choosing a proportionate system response.
The intake moment A high-visibility team requests a new EmptyState component after a missed upsell opportunity. The request is plausible, but plausibility is not priority. RICE routing Reach, Impact, Confidence, Effort Use the four factors to decide the next route: build, discover, keep local, or stage. Loud ask react to volume The request gets a route that matches the evidence. Prioritization is a governance service: it makes tradeoffs visible before the roadmap hardens. 01 Reach 02 Confidence 03 Route Step 1 One team asks for EmptyState, but three other teams have similar screenshots in audit notes.
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in