Aglet

Learn from notification preference overload and blanket muting

A preference lesson should preserve which choice became hard and what a person risked missing. Compare later settings journeys with the original event map, then refine one review question about categories, defaults, channel consequences, or grouped controls without assuming fewer switches always means better control.

Keep the lesson for the next incident

  1. Keep the choice map

    Record event, category, channel, frequency, default, label, and resulting delivery for the confusing path. State what the person expected. This distinguishes a true taxonomy problem from a delivery or permission issue.

  2. Compare later settings

    Review new and returning contexts after the change, including a user who keeps optional updates off. Look for an important event hidden by grouping or a category that still overlaps. Preserve a control where the setting was predictable.

  3. Refine one review question

    Require future reviews to ask what each choice controls, what stays available, and how the person can reverse it. Assign ownership and revisit date. Define the observation that would show the question reduced blanket muting without removing useful control.

What to carry forward

The learning record connects one preference collision to later evidence and a repeatable settings review. Stop when another reviewer can explain each choice’s consequence. Carry forward uncertainty where platform-level controls or delivery permissions limit what the product can observe.

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