Aglet

Triage inconsistent status labels across a product

Status labels are part of the product’s record contract. Begin with the canonical state value and compare how lists, details, filters, empty states, and actions present it. Keep genuine domain differences separate from accidental wording drift.

Establish what is happening

  1. Inventory the state

    Record model or domain state, page, component, visible label, color or icon, filter value, and available action. Use stable examples and note whether the underlying state is truly the same.

  2. Compare user interpretation

    Describe whether labels imply different progress, ownership, severity, or next steps. Check list, detail, navigation, form, and notification contexts for contradictions that could change a decision.

  3. Bound the workflow

    Identify whether users misclassify, filter out, duplicate, or act on a record incorrectly. Separate a cosmetic synonym from a status that changes what the user believes is complete or blocked.

What to carry forward

Triage should state the canonical state, inconsistent presentations, affected contexts, and user decision at risk. Escalate when wording or tone changes action meaning; otherwise record a bounded terminology quality gap. Record canonical state, visible label, tone, filter value, icon, and available action in each context, then identify which contradiction could change a user decision.

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