Teams can agree with an ambition while disagreeing about what it requires. “Improve service” might mean faster replies to one person, more complete answers to another and fewer unnecessary contacts to someone else. The problem is not always motivation. It may be that the commitment has never been made clear enough to guide a choice.
Begin by describing the difference you want to make for a specific person or process. Then distinguish the outcome from the activity intended to support it. Publishing a guide is an activity; helping colleagues complete a task without avoidable confusion is an outcome. Both can be discussed, but they should not be treated as interchangeable.
Write the agreement in ordinary language
A workable commitment names the intended result, a responsible owner, a review point and the evidence you will consider. It also identifies what is outside the team’s control. Ownership should mean coordinating the agreement, not carrying blame for every dependency.
Try this structure: “We will change this part of the work so that these people can do this more reliably. We will review these examples or measures at this point, while checking these risks.” If the sentence becomes crowded, the goal may contain several different commitments that need separating.
George T. Doran’s SMART framing can prompt useful questions about specificity and timing. Edwin Locke and Gary Latham’s goal-setting research also provides important context. Neither should be used as a reason to ignore task complexity, learning needs or the possibility that a target is poorly chosen.
| Outcome | Receiving colleagues can act on a handover without avoidable clarification. |
|---|---|
| Practice | Trial a short handover template on the next suitable transition. |
| Evidence | Review the handover note and ask the receiving colleague what was missing. |
| Guardrail | Do not omit important context just to keep the note short. |
| Review | Discuss the trial after the transition, then retain, revise or stop it. |
Choose measures that answer a question
Start with the question you need to answer rather than the data that happens to be available. If you want to know whether handovers are useful, counting completed templates is incomplete evidence. You also need to understand whether the receiving person could act and whether important information was accurate.
Pair an outcome indicator with a quality check or a qualitative example where appropriate. Explain what each measure cannot show. A shorter turnaround time does not establish that work was correct, accessible or sustainable. A high activity count can coexist with duplicated effort.
Charles Goodhart’s warning about measures becoming targets is a helpful caution against treating an indicator as the whole purpose. Avoid individual rankings built from collaborative work. The person resolving difficult cases may appear slower than someone handling straightforward ones, even while making an essential contribution.
Expose dependencies before promising a date
Ask what the team needs from other people, systems or decisions. Record uncertainty rather than hiding it inside an optimistic deadline. A commitment dependent on legal review, customer availability or specialist access should make that dependency visible.
When capacity changes, discuss what stops or moves. Adding a priority without removing anything can turn a planning problem into an apparent personal failure. If your team uses objectives and key results, associated with Andy Grove and later popularised by John Doerr, retain this capacity conversation rather than treating the framework as a substitute for judgement.
Review progress without losing context
Use the review to compare an agreement with evidence, not to stage a defence of a number. Begin with what happened. Then ask what changed in demand, available time, quality requirements or dependencies. Invite the people doing the work to describe the conditions behind the result.
Distinguish explanation from exemption. Context does not mean no one is responsible; it helps you identify the responsibility accurately. A missing skill may require practice and support. An unclear decision may require a leadership change. A fragile process may need redesign rather than another reminder.
W. Edwards Deming’s emphasis on understanding systems and variation is useful here. Avoid drawing a firm conclusion from a single unusual week. Look for patterns, check the comparability of cases and remain explicit about uncertainty.
Finish with a decision
A review should end with something more useful than “try harder.” Keep the commitment, revise it, stop it or run a smaller experiment. Name who will take the next action and when you will revisit its effect.
Where performance information affects pay, promotion or formal employment decisions, use your organisation’s documented processes and seek appropriate HR or legal guidance. This page is a planning aid, not a replacement for fair procedure or professional advice.