Decide where the work belongs
Rank the blocked first action
Name what a person cannot do while the page loads, such as reading an account status or submitting a form. Count affected route families and session types from available observations. A delay before a high-value action deserves more weight than an equally long wait before secondary content.
Separate regression from long-standing cost
Compare recent deploy or asset changes with the last known healthy trace using the same route and conditions. Mark whether the delay is new, growing, or stable. New regressions usually compete for urgent capacity, while stable costs need a scoped improvement with an explicit owner.
Choose a queue decision with a bound
Select one next move: investigate now, schedule a measured fix, or collect a missing comparison. State the evidence required to advance and the date or event that will reopen the item. Avoid prioritizing from a single peak value when the affected population is unknown.
What to carry forward
Produce a queue decision that names affected work, evidence quality, urgency, and the smallest useful next slice. Include uncertainty when reach or regression timing is incomplete. The output is ready when another engineer can understand why the item is now, later, or waiting for one specific missing observation.
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