Aglet

Prioritize notification grouping by resource and action

Grouping work matters when repeated updates bury a decision or when one summary makes several resources look interchangeable. Compare the attention cost of separate items with the context a group preserves. A narrower key may be safer than grouping every event from one actor.

Decide where the work belongs

  1. Name the action cost

    Describe what a person must find or decide and whether grouping hides a child’s action. Compare one project with several work items and a single conversation. Keep a noisy group separate from a useful compact summary.

  2. Compare grouping scopes

    Set resource, project, conversation, actor, date, and no-group behavior beside one another. Consider child completeness, summary text, and destination. Prefer a scope that reduces repetition while keeping each item independently understandable.

  3. Choose the first slice

    Record resource type, owner, and revisit evidence. Decide whether to change grouping key, summary, child labels, or destination. Preserve before-state events and one separate control so the queue decision can be evaluated after a change.

What to carry forward

Prioritize grouping where repeated updates obscure resource-level action or where a summary misattributes work. The decision should state grouping key and preserved context. If children already stand alone and grouping adds little, queue copy or delivery volume instead.

Technical background: Android 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