Aglet

Verify consistent status labels and actions across a product

Verification should compare the contexts where users interpret status and choose actions. Confirm intentional domain distinctions remain explicit while accidental synonyms and tone conflicts disappear.

Check whether the outcome improved

  1. Replay each affected context

    Review list, detail, filter, navigation, form, notification, empty, and error states for the same canonical value. Confirm visible label, qualifier, tone, and action agree with its meaning.

  2. Check state transitions

    Move through pending, active, failed, verified, completed, archived, or equivalent transitions where safe. Ensure labels change only when the underlying state changes and no stale copy remains.

  3. Review user decision

    Compare the action a user would choose from each context and apply the terminology checkpoint. Keep verification partial if a consumer, export, or role-specific page remains outside review.

What to carry forward

Verification should state consistent, intentionally distinct, still contradictory, or inconclusive for each canonical state. Close only when wording, tone, filters, and actions communicate the same decision across reviewed contexts. Replay the same state in list, detail, filter, navigation, form, empty, and error contexts, then inspect transitions to ensure labels change only with the underlying state. Check screenshots or rendered text after navigation and back behavior so a stale label does not pass review.

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