Agree what fits, and what moves
When the work on hand exceeds the time available, use this conversation to agree priorities and record the decision. In this fictional example, Northstar Service Desk weighs an urgent backlog review against its weekly queue summary. This is a work-prioritization conversation, not a measure of productivity or a staffing dashboard.
Work through the decision together
Keep the discussion specific to the work, the time available, and the consequences of moving a commitment.
-
1
Make the work visible
List current commitments, deadlines, dependencies, and the time realistically available in the period being discussed. Identify what has changed since the work was planned. -
2
Compare urgency and consequences
For each item, discuss what happens if it is done now, later, or not at all. Distinguish a fixed deadline or dependency from a preference, and name who or what is affected. -
3
Choose what continues, stops, or moves
Agree which work stays first and which work pauses, stops, or is deferred. Surface any work that needs a separate decision rather than assuming everything still fits. -
4
Name an owner and review date
Record the choice and its rationale, assign each follow-up to a role or participant in the conversation, and set a date to check whether the priorities still fit.
Worked example: protect time for the urgent review
Fictional Northstar Service Desk decision. The work details are illustrative, not live operational data.
- Keep summary this week:
- Prepare the weekly queue summary
- Defer summary; review backlog first:
- Use the available time for the urgent backlog review
- Keep summary this week:
- Less time remains for the backlog review
- Defer summary; review backlog first:
- The weekly summary moves to the next planning period
- Keep summary this week:
- Not included
- Defer summary; review backlog first:
- Included
Decision record
Fictional sample: Northstar Service Desk
Decision date: 10 October 2026
Priority: Use this week's available work block for the urgent backlog review. The team chose this option because unresolved items need assessment before the next planning period.
Deferred work: Move the weekly queue summary to the next planning period. Do not count it as completed or silently add it back into this week's workload.
Evidence considered: The pair compared the backlog review need, the remaining work time, and the consequence of delaying each activity. No backlog size, service-level target, or customer impact is assumed in this example.
Owners: The manager communicates the priority change and raises unresolved priority conflicts. The team member records the backlog review findings and tells the manager if workload or timing changes.
Review date: 17 October 2026. At that check-in, the pair will confirm whether the review is complete, whether the summary still needs to be done, and whether new work changes the plan.
If competing demands remain unresolved, raise the conflict through the organization's established manager or People Development route.