Build a useful investigation brief
Compare then and now
Map the original expected and observed outcomes to current screens, roles, data states, and product versions. Identify changed labels, defaults, integrations, or policies that could make the old evidence no longer comparable.
Replay representative paths
Run the current workflow with conditions from the original reports and one adjacent scenario. Record success, failure, workaround, and any new friction. Keep a failed recreation distinct from proof that the historical issue never existed.
Test the silence hypothesis
Check whether feedback sources, customer segments, or workflow usage changed during the quiet period. Rank resolution, avoidance, channel loss, and measurement gaps as hypotheses tied to observations, not conclusions based on time alone.
What to carry forward
A useful brief states whether the old symptom reproduces now, what changed, and how reporting coverage affects confidence. Stop when current behavior and silence have plausible evidence-backed explanations; otherwise leave the request open with a targeted observation gap.
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