Decide where the work belongs
Rank the mobile action that stalls
Name whether the delay blocks sign in, reviewing a signal, saving a decision, or another primary action. Separate a slower content load from a tap that appears ignored. Weight repeated transitions and actions performed away from a stable connection because their cost accumulates.
Group reach by device and connection
Use available observations to group latency by device class, operating system, viewport, network type, route, and account size. Label untested combinations clearly. A delay on common mobile shapes supports urgent work, while a rare device-specific case may need a targeted reproduction first.
Choose a bounded mobile slice
Select immediate investigation, a payload or request-sequence improvement, or evidence collection for one missing device and connection pair. State the comparison that will change priority. Do not prioritize by desktop timing or by a laboratory network that does not match the affected workflow.
What to carry forward
Produce a queue decision tied to the blocked mobile action, confirmed device and network reach, and evidence quality. Include regression timing or scale pressure when known. The next engineer should have one representative workflow, one matched comparison, and a clear reason to work now or later.
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