Decide where the work belongs
Score present impact
Describe affected requests, customers, environments, and failure severity using the evidence already available. Distinguish blocked transactions from noisy retries or duplicate reports, and state what population has not been checked.
Compare competing work
Place the spike beside current deadlines, unresolved regressions, and known business-critical paths. Move it ahead when harm is broad or growing, not merely because a deployment is recent. Record the comparison that explains the queue position.
Choose a review horizon
Set a concrete next review based on signal velocity and operational exposure. A fast-growing checkout failure needs a shorter horizon than a stable internal warning. Name the evidence that would raise, lower, or close priority.
What to carry forward
Prioritization should produce a queue position, a responsible reviewer, and a time-bounded reassessment rule. If impact cannot be measured yet, mark the item as needing evidence and schedule that evidence gathering instead of labeling the release defective.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow