Establish what is happening
Record the stopping point
Capture the workspace and project state using synthetic identifiers, the last completed core step, the action offered next, and any validation or permission message. Note whether the person left after a successful save or before a response, because those states require different recovery paths.
Reproduce the handoff
Start with a new workspace and follow the setup guide through project creation, test-key creation, and the built-in check. Pause at each transition, refresh, and return through the workspace route. Record redirects, persisted state, and the first action that no longer feels clear.
Separate required work
Mark optional teammate invitation or agent-profile work separately from the core setup. Compare owner and viewer behavior, because a hidden permission boundary can resemble abandonment. Keep browser, viewport, and timestamp evidence attached to each synthetic attempt.
What to carry forward
Triage is complete when the exact unfinished step, workspace state, role, and visible next action are recorded. If the person simply chose to stop without a blocker, classify it as an unconfirmed abandonment and avoid inferring a usability cause.
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