Decide where the work belongs
Name the choice error
Describe what a person expected from the label and what event or channel they received. Compare a technical word with an outcome-based label and keep timing confusion separate from channel confusion.
Compare language remedies
Set canonical terms, short examples, timing notes, grouped channels, and inline consequences beside one another. Consider narrow layouts and localization. Prefer concise context that improves choice without turning settings into a glossary.
Choose the first change
Record channel, event, owner, and revisit evidence. Decide whether to correct labels, map behavior, or adjust settings hierarchy. Preserve the current label and one clear control so the queue decision has a before-state. Tie the queue choice to one observable settings mismatch.
What to carry forward
Prioritize channel language where terminology changes a meaningful delivery choice or hides an important event. The decision should name the channel and context. If labels are clear but delivery is wrong, queue the underlying behavior instead of adding copy.
Technical background: Apple developer documentation.
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