Keep the lesson for the next incident
Write the help map
Document the task, page state, role, existing destination, expected result, and safe return action for workspace, project, test-key, check, verification, invitation, and empty states. Mark unsupported or future paths explicitly instead of linking to a placeholder promise.
Keep navigation fixtures
Save synthetic traces for each state-specific entry point, destination, deep link, back path, keyboard focus, and narrow layout. Assert heading, context, available action, and result expectation. Avoid using a screenshot as the only evidence for a link’s behavior.
Define recurrence signals
Reopen review when a help link dead-ends, changes workspace context, points to an unavailable role action, or describes a capability not present in the route. Record external timing and device limits and assign owners for task map and destination changes.
What to carry forward
Close learning with the task-to-route map, state-specific recovery fixtures, role boundaries, and recurrence signals. Help is durable when it guides a real next action and returns the person to the same scoped onboarding context with test evidence.
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