Keep the lesson for the next incident
Keep the vocabulary evidence
Record label, example, event, channel, timing, saved choice, and observed or unknown outcome. State the user-visible promise. This prevents later copy revisions from losing the behavior that made the term confusing.
Compare later choices
Review another event category, muted state, narrow layout, and available external channel after the change. Look for a synonym that still means two things or an example that implies stronger delivery than supported.
Refine one language check
Require future reviews to map each label to an event, channel, timing, and reversal path. Assign ownership and revisit date. Define the observation that would show the check reduced mistaken choices without increasing settings length. Keep the preferred wording tied to a visible consequence.
What to carry forward
The learning record connects one terminology collision to later choices and a reusable label-to-outcome check. Stop when another reviewer can apply it to a new channel. Carry forward uncertainty where device or provider presentation is outside the product’s direct control.
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