A prioritization score favors automated triage, but the data rights are unresolved. Separate a delivery commitment from a small experiment.
Updated Nov 2026 · Original practice questions with worked answers and teaching rubrics. Our editorial policy explains the sources, review process and limits.
Fictional field-service roadmap. Capacity permits one delivery project this quarter. The goal is less manual repair-scheduling effort. Reach counts distinct accounts per quarter; impact uses a common internal scale; effort includes data and integration work.
| Saved scheduling templates | Reach 1200; impact 1; confidence 90%; effort 2 person-months. |
|---|---|
| AI request triage | Reach 1800; impact 2; confidence 50%; effort 3 person-months. |
| Automated parts ordering | Reach 600; impact 3; confidence 40%; effort 4 person-months. |
| Triage dependency | Training and evaluation permissions for partner messages are unresolved. |
| Ordering dependencies | No dependable parts-availability feed or approved spending limit. |
| Templates | Uses existing supported fields; demand evidence should still be reviewed. |
Your task. Calculate RICE scores, choose the delivery commitment and any bounded evidence task, then explain how changed effort or confidence would reverse the ranking.
A prioritization score favors automated triage, but the data rights are unresolved. Separate a delivery commitment from a small experiment.
This reference answer is in Premium. Free signup opens other answers.
9 answers per topic instead of 5, and your progress kept · no cardor unlock all 420 remaining answersNo comments yet. How would you have answered?