Build a useful investigation brief
Build an episode matrix
Align prior and current release identity, path, environment, data condition, traffic, symptom, mitigation, and verification result. Mark missing fields and avoid filling the matrix with remembered values.
Test the prior fix boundary
Identify what the earlier fix changed and which paths, cohorts, versions, or delayed jobs its verification covered. Compare the current failure with that boundary to find an uncovered condition.
Challenge recurrence
Search for changed dependencies, configuration, traffic, data shape, or client behavior that could produce a similar symptom. Record counterexamples and keep a new cause separate from true recurrence.
What to carry forward
The brief should distinguish repeated mechanism, uncovered condition, and coincidental symptom, with evidence for each. Conclude with recurrence confidence and a verification plan that covers the current boundary rather than replaying the old check blindly. Compare the changed boundary, test coverage, rollout exposure, and runtime evidence across episodes, then identify which earlier assumption failed to hold in the new context.
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