Decide where the work belongs
Classify the blocked outcome
Put a missing project, missing test key, failed check, unclear redirect, and optional invitation into distinct queue categories. Elevate a state that loses saved work or leaves the workspace without a clear next action. Keep voluntary pauses distinct from observed blockers.
Bound the affected path
List the role, workspace state, browser, viewport, and setup step reproduced. Count only synthetic attempts or identified reports that support the scope. If the number of affected workspaces is unknown, state that gap instead of guessing at completion or abandonment rates.
Choose a recovery
Prefer a reversible next action that resumes the last durable step and explains what remains. Do not reset a project or key to simplify the interface. Assign an owner for the blocked step and a reassessment trigger after the recovery path is tested.
What to carry forward
Queue a core-step blocker ahead of optional onboarding polish, especially when progress is not saved or the next action is ambiguous. Include the exact role and step, observed scope, safe recovery, owner, and evidence needed to lower priority.
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