Aglet

Prioritize inconsistent status labels in a product

A label mismatch can be harmless in a secondary description and dangerous when it changes whether work is treated as active, verified, failed, or complete. Prioritize the decision and spread of the contradiction.

Decide where the work belongs

  1. Rank action risk

    Describe whether users may approve, archive, retry, assign, close, or ignore a record based on the label. Give higher priority when visible state conflicts with an available action.

  2. Rank reach

    List pages, roles, record types, filters, exports, and notifications that use the state. Record observed contexts and unknown consumers instead of assuming one template is universal.

  3. Set a terminology checkpoint

    Choose a review after status mapping, copy, tone, filter, or component changes. State which canonical value and contexts must agree before the inconsistency can be closed.

What to carry forward

The queue result should name the canonical state, action risk, affected contexts, owner, and checkpoint. Keep priority high when users can make a different decision from different labels; lower it only when meaning remains stable. Prioritize contradictions that can cause approval, retry, closure, assignment, or filtering mistakes across repeated pages; a harmless secondary synonym can remain lower risk.

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