Build a useful investigation brief
Freeze cohort definitions
Capture version, flag, region, tenant class, device, and time filters used to define each cohort. Check that records remain stable during the analysis. If membership can change, snapshot the query and note its limits.
Compare the execution path
Trace requests or jobs through routing, dependencies, configuration, and data validation. Identify the first step where outcomes diverge, then compare a matching control at that step instead of comparing only final errors.
Challenge the leading explanation
Look for counterexamples: exposed successes, unexposed failures, a second region with the same version, or a different data shape. These tests can weaken a rollout hypothesis and prevent a configuration coincidence from becoming a conclusion.
What to carry forward
The investigation brief should include stable cohort queries, a first divergent step, representative records, and competing explanations. Conclude with a confidence level and a bounded follow-up that can be repeated before exposure changes again.
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