Aglet

Triage notification actions before adding another button

An action is useful when its label and destination let a person predict the result before tapping. Triage the context before adding or renaming buttons. Capture event, actor, resource, state, permission, action, and destination so “open” is not mistaken for a task.

Establish what is happening

  1. Capture the action

    Record notification title and body, event, actor, resource, current state, action label, destination, and expected outcome. Include a no-action notification and one action that completes work. Keep preview length in the evidence.

  2. Compare the promise

    Ask whether the action marks, reviews, accepts, opens, or merely navigates. Compare label with resulting state and role context. A short button can still be clear when the destination carries context; a generic verb often cannot.

  3. Set an action boundary

    State which event states expose an action, what destination is required, and how the person recovers if state changes. Preserve a clear control. Stop when another reviewer can predict the outcome from the notification alone.

What to carry forward

The triage output is an action matrix with event, state, label, destination, role, and expected result. Stop when task action and generic navigation are distinguishable. If destination or state is missing, keep the action minimal and route the context gap.

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