Aglet

How to prioritize first-use help gaps with evidence

Prioritize help discovery by how directly it blocks a useful first result. A new owner trapped on a blank project needs a direct setup or check path before a broad documentation index is polished. A dead link or unauthorized destination may be more urgent than a page with short but accurate guidance.

Decide where the work belongs

  1. Classify the dead end

    Elevate no next action, dead link, wrong workspace, and misleading capability text above a missing example. Treat empty project, failed built-in check, verification pending, and invitation states as separate tasks with specific destinations.

  2. Bound reach and evidence

    Record role, route, state, viewport, task, and the synthetic or identified paths reproduced. Count only supported reports. If the underlying action or help destination is not available, state that limitation instead of proposing an unimplemented workflow as a fix.

  3. Choose the smallest resolution

    Prefer an existing setup guide, event-intake page, project route, verification page, or safe back action when it truly matches the state. Add one clear next action and its expectation. Assign a navigation owner for links and a product owner for missing capability decisions.

What to carry forward

Queue help that leaves a core setup task without a safe destination ahead of taxonomy or wording polish. Include the current state, role, route, existing destination, owner, and evidence required to show that the person can continue.

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