Decide where the work belongs
Name the decision cost
Describe what a person cannot predict from the current settings and which event may be missed. Compare blanket mute, duplicate toggles, and a category that has a real distinct purpose. Keep preference complexity separate from delivery failure.
Compare simplification sizes
Set grouped categories, clearer labels, per-channel examples, defaults, and advanced controls beside one another. Consider whether grouping hides an important event. Prefer a structure that keeps essential updates visible and optional choices understandable.
Choose the first slice
Record event categories, channel, owner, and revisit evidence. Decide whether to simplify copy, group controls, or map delivery behavior first. Preserve the current control and one important-event path for comparison. State which choice can be simplified without removing control.
What to carry forward
Prioritize simplification where preference complexity causes blanket muting or hides an important event. The decision should name retained choices and channel scope. If controls are clear but events still arrive unexpectedly, queue delivery behavior separately from settings hierarchy.
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