Protocol

Swap commitments openly when a priority changes

An extra priority is a trade-off, not a new hour.

About 1 min read

Before you use it

Use when
  • A new urgent request arrives halfway through a full day.

Keep this limit in mind

  • Immediate emergencies may require action first and retrospective coordination; this rule is for normal reprioritization.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

Why it matters

Show the existing planned work and ask what should be delayed, delegated, reduced or canceled to accommodate the new request. Record the changed output and recipient. Avoid silent overtime as the default way to handle reprioritization.

Steps

  1. Identify which current commitment will move or shrink.
  2. Communicate the effect on the original owner before accepting the new deadline.

An example

A production incident displaces a planned report; tell the report owner the revised delivery.

Check your result

The replacement is explicit and someone can make an informed priority decision.

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingSwap commitments openly when a priority changes

Evidence and sources
Supports

UK government delivery guidance suggests regular explicit prioritization based on evidence, user research and available resources.

Claim limit: General public-service prioritisation guidance. It does not prescribe the card-specific effort/date comparison or establish forecasting accuracy. Commitment substitution and estimate review are editorial adaptations, not demonstrated productivity effects. Source reading history: selected_passages; 2026-10-10; Regular priority review using user research, delivery performance and stakeholders. The cited official page was retrieved on 2026-10-10 and the named passages were inspected. Card-specific adaptations are independent editorial reasoning, not validated improvements. Introductory prioritisation and capacity passages reread on 2026-10-12; they do not specify the card-specific forecasting procedure. Agent release review: Atlassian calendar guidance and the UK Government Service Manual supply context for calendar and prioritization practices. The precise estimate comparison and scheduling methods are editorial adaptations; the original data and emergency limits remain attached.

Deciding on priorities · Regular priority review using user research, delivery performance and stakeholders

All sources (1)
Edition and review

Version 0.1.0 · Published

Edition checked · 2026-11-12

Read this idea as JSON · Release details