Aglet

How to triage a first-use help discovery gap for a clear scope

Help discovery should be triaged from a real first-use task, not from a list of missing links. Start with the page where a synthetic person is confused, record its state and role, and compare the available explanation with the action needed to continue. Keep empty, error, and permission states distinct.

Establish what is happening

  1. Name the task

    Record the concrete goal: create a workspace, create a project, make a test key, run the built-in check, or inspect its sample result. Capture the current heading, empty or error state, role, and route using synthetic data. Do not infer a need from generic browsing alone.

  2. Trace the offered help

    List visible links, labels, back actions, setup references, and any search or navigation entry. Follow each destination and record whether it explains the current state and returns to the task. Mark a dead end, wrong context, and merely concise copy separately.

  3. Compare expected capability

    Check the source and route behavior behind the help text before describing a feature. If a page mentions an external or unfinished path, record the boundary plainly. Compare owner and restricted-role states so help does not point to an unavailable action.

What to carry forward

Triage is complete when the blocked task, current state, role, route, help path, and intended destination are recorded. Classify the gap as missing guidance, dead link, wrong context, unavailable action, or unknown only after following the actual path.

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