Aglet

Verify an empty state explains the right next step

Verification should exercise the state that confused users and nearby states that look similar. Confirm the heading, explanation, filters, role context, and next action agree with what the page actually knows.

Check whether the outcome improved

  1. Replay the confusing entry

    Use the original page, role, project, filters, and data condition. Confirm the empty heading explains the cause in plain language and does not imply records exist or processing finished.

  2. Check neighboring causes

    Exercise no data, no filter match, pending setup, and unavailable scope with safe fixtures. Ensure each message offers only an appropriate clear, create, connect, wait, or access path.

  3. Follow the next action

    Activate each visible link or button and confirm it reaches the promised destination while preserving useful context. Apply the copy checkpoint and keep the result partial if a cause remains ambiguous.

What to carry forward

Verification should state clear, partially clear, misleading, or inconclusive for each empty cause. Close only when the page explains what is known and offers a next step that matches the evidence. Replay each relevant empty cause and follow its visible action, confirming that clear, create, wait, connect, or access guidance matches the state and preserves useful context.

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