Keep the lesson for the next incident
Document the representative mobile matrix
Keep device class, operating system, viewport, connection profile, route, account shape, and action sequence together. Explain which interval blocked usefulness and which comparison was healthy. Avoid treating one phone or one signal condition as a universal mobile baseline.
Preserve the first-action contract
Write what content or control must be available before the workflow counts as usable, plus the progress, error, retry, and cancellation behavior expected while waiting. Pair that contract with a repeatable journey so payload reductions cannot quietly remove the information needed for the decision.
Recheck after payload or request changes
Review the matrix after new fields, media, authentication steps, dependencies, or client startup work are introduced. Compare waterfall, transfer, device processing, and recovery. Add a separate case if a new route has a different first action or connection sensitivity instead of stretching the old case.
What to carry forward
The learning record should retain the device and network matrix, first-action definition, waterfall boundary, and recurrence trigger. It is complete when future engineers can replay realistic mobile conditions and distinguish a transfer improvement from a client or server change that only helps one case.
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