Build a useful investigation brief
Build the symptom matrix
Create rows for each representative report and columns for version, route, account state, inputs, timing, expected result, observed result, and reproduction status. Use redacted references when needed. Highlight the smallest set of conditions shared by every report.
Test competing explanations
Try the most plausible shared mechanism and at least one split hypothesis. For example, compare a client validation path with an API timeout when both produce the same blank screen. Record observations, environment differences, and negative results instead of only confirming evidence.
Write the evidence-backed brief
State whether one mechanism explains all reports, only a subset, or none. Link each conclusion to a representative observation, identify reports that remain unexplained, and propose the next bounded experiment. Avoid converting correlation into a causal claim.
What to carry forward
A complete investigation brief identifies the shared symptom, tested conditions, observed results, unexplained cases, and current confidence. Its stopping condition is a reproducible explanation for the selected scope or a clear split into separate investigations with owners and evidence gaps.
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