Decide where the work belongs
Classify the mobile harm
Elevate controls that cannot be tapped, fields that lose input, and errors that disappear above a cosmetic spacing issue. Treat a responsive route that changes workspace context as a context finding. Record keyboard, orientation, and touch conditions for each queue item.
Bound device reach
List viewport, browser class, orientation, route, role, setup step, and observed fixture count. Use synthetic or identified reports only. If device coverage is limited to one narrow width, state the limit instead of calling the entire mobile experience blocked.
Choose a safe mobile action
Prefer a visible, thumb-reachable next step that preserves saved progress and explains any scrolling needed. Avoid hiding required setup behind a collapsed control without a clear label. Assign layout and domain owners separately when both symptoms appear.
What to carry forward
Queue mobile paths that cannot reach or preserve a core setup action ahead of spacing and density refinements. Include exact viewport, role, route, safe recovery, owner, and evidence needed to determine whether the issue generalizes.
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