Aglet

Verify a proportional response to high-volume feedback

A proportionate response may be copy, guidance, instrumentation, or a code change. Verification should match the chosen intervention to the reported friction, test representative high-volume paths, and ensure the response did not hide a severe subgroup or make the workflow less clear.

Check whether the outcome improved

  1. Check the intended effort

    Repeat representative workflows before and after the response, counting actions or decision points only when they explain the reported cost. Confirm the expected shortcut, message, or affordance is visible to the affected context and remains understandable.

  2. Test the edge contexts

    Exercise roles, input states, accessibility paths, and fallback routes that were absent from the dominant sample. Verify that the response does not remove needed detail, bypass a safety boundary, or make an error state harder to recover from.

  3. Review the outcome signal

    Compare new reports, abandonment observations, support themes, or workflow checks against the original hypothesis. State what the signal can and cannot prove, and keep the item open if the response changed wording without changing the underlying effort.

What to carry forward

Verification passes when the chosen response reduces the documented effort for representative users, preserves adjacent paths, and produces an interpretable follow-up signal. If only message visibility improved, report that narrower result and leave the underlying friction open for a later 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