Keep the lesson for the next incident
Cluster by boundary
Group previous episodes by region, tenant class, flag state, version pair, or dependency route. Record which dimensions repeated and which were incidental. Do not merge episodes solely because they happened during staged releases.
Improve the control
Document whether the unexposed cohort was truly comparable and what signal arrived too late. Choose one stronger control, such as a matched path or version marker, that can be captured without changing product behavior.
Create a review memory
Write the rollout checkpoint, evidence owner, and recurrence condition in the release record. Include the cohort query or stable identifiers so the next reviewer can recognize the pattern before exposure expands.
What to carry forward
The lesson is useful when it changes one repeatable comparison or decision point and names the signal that should reveal recurrence. Keep the boundary conditional until later rollout evidence confirms that the improved control is timely and comparable.
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