Aglet

Learn from recurring document stage action confusion

Repeated questions about what to do next show that status labels alone do not carry the workflow. Learning should preserve the pending, partial, and failure cases that exposed uncertainty and document the action and capability relationship for future processing stages.

Keep the lesson for the next incident

  1. Cluster action uncertainty

    Group cases by waiting, retrying, replacing, partial use, failure recovery, and revisit. Record the state wording, available controls, action users chose, and document outcome for each cluster.

  2. Write the state-action table

    For every processing state, document capability, expected wait or completion condition, safe action, identity effect, and failure path. Include a partial derivative and a failed stage so the table covers more than ready and error.

  3. Trigger action review

    Require the table and fixtures when changing processing queues, status copy, retry behavior, derivatives, or document controls. Assign an owner who can approve the safe action for each new state before exposing it.

What to carry forward

The learning record is complete when every processing state has a capability, a safe action, and a recovery fixture that reviewers can follow. If teams disagree about an action, record the decision owner and keep the interface explicit about the unresolved choice.

Technical background: W3C guidance.

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