Prioritisation
Part of Improving team productivity without more activity tracking
Distinguishing busy schedules from completed outcomes
Trace scheduled work to usable outputs and intended outcomes without treating a full calendar or unfinished tasks as a productivity score.
A full calendar shows where time was booked, not what the team finished or what changed for the people it serves. To see the gap, take one recent period and trace a few scheduled activities to usable outputs and, where possible, to the later outcomes they were meant to support. Keep essential service, coordination and support time in view; an empty calendar is not the goal.
Read the calendar as a clue
Pick a reasonably typical week rather than the most frantic one. With the people involved, identify the main categories of scheduled time: making a deliverable, responding to a live service need, deciding, coordinating, learning or waiting. Include necessary work that never appears as a meeting, such as reviewing a colleague's draft or covering a customer queue.
Do not add up hours and call the largest category waste. A discussion may prevent a misunderstanding; quiet drafting time may produce a document that cannot be used. The calendar tells you where to ask questions, while the work record and recipient tell you what happened.
Key Performance Indicators for Work Effectiveness
- Time Category Focus
- Identify dominant work types (e.g., decision-making, service coverage)
- Usable Outputs Produced
- Track deliverables like drafts, decisions, resolved issues
- Unresolved Items After Block
- Note whether tasks remain open due to input delays or complexity
- Service Impact
- Assess whether outcomes improved for clients or internal teams
Trace the intended result
For each significant block, ask: What was meant to move forward? What changed by the end? What is the next step, and who can take it? Record a small note in the team's existing system:
| Scheduled work | Expected output | Evidence to check |
|---|---|---|
| Proposal review | A decision or specific changes requested | Current proposal and recorded response |
| Customer coverage | Requests answered or passed to an owner | Service record and unresolved cases |
| Project work block | A usable draft or a resolved question | Current work item and recipient feedback |
These are examples, not a reporting template. A block may have produced valuable investigation without a finished artefact. Describe what uncertainty it removed or why work remains open instead of marking it ‘unproductive’.
A completed output is not necessarily a completed outcome. A proposal may be ready for a decision while the eventual customer result depends on other steps. Where the intended outcome can be checked, ask whether the output was used and what else influenced the result. If it is too early to know, record the usable output without claiming the later outcome.
Busy Schedules vs. Completed Outcomes: Key Differences
- Calendar Activity
- Shows where time was booked
- Completed Outcome
- Evidence of change or progress for the people served
- Usable Output
- A draft, decision, or resolved issue that can be used
- Unfinished Work
- Not necessarily failure—may reflect complexity or ongoing service needs
Tracing Scheduled Work to Intended Results
- Identify a typical weekAvoid peak periods; focus on routine workload
- Categorise scheduled timeDeliverables, service response, decisions, coordination, learning, waiting
- Ask 'What was meant to move forward?'Determine expected output and next steps
- Record evidenceTrack current proposal, service records, feedback, or unresolved cases
- Assess outcome relevanceCheck if output was used and what influenced final result
Explain the gap before changing the diary
If many sessions lead to no settled decision, check whether the decision-maker, question or required information was missing. If focused time repeatedly ends with unfinished work, ask whether inputs were late, an urgent duty took precedence or the task was larger than expected. Those explanations call for different responses. Do not infer a person's effort from the visible calendar or from online status.
Compare the work intended for the period with usable results, but avoid treating every unfinished item as a failure. Some tasks deliberately span weeks; service roles may spend time preventing or resolving issues as they arise. Note changes in demand and complexity before comparing periods or teams.
Choose one finding to act on: clarify what a session must decide, make an input available earlier or protect coverage while another person completes a deliverable. At the next review, ask whether the intended result moved forward and whether quality or service suffered elsewhere. A less crowded calendar is helpful only if the work it released can be used.
