Establish what is happening
Confirm the affected context
Identify the roles, workflow state, product version, permissions, and account conditions shared by the reports. Count distinct affected accounts conservatively and record whether the cohort is known, sampled, or still being discovered.
Describe the severe consequence
State the blocked outcome, irreversible action, lost time, or operational risk in observable terms. Separate what customers reported from what the team suspects, and note any workaround plus its cost and failure conditions.
Bound the possible spread
Check adjacent roles, configurations, and workflow paths for evidence of broader exposure without claiming that untested paths are safe. Route credible severe harm for immediate investigation while keeping the reach estimate labeled as limited.
What to carry forward
The output is a bounded severe-impact record with a defensible cohort count, concrete consequence, workaround status, and evidence limits. Stop triage when the urgent investigation scope is clear; do not inflate reach or downgrade severity because the cohort is small.
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