Useful change begins with a specific question. Work through the ideas below, then use the field exercise to test one of them in context.
Define the outcome
For each important result, name one owner and describe what done means. Contributors can share the work, but the owner coordinates the decision and reports progress.
- Write the outcome in observable terms.
- Agree on a date and dependencies.
- Give the owner authority to ask for help.
Check progress before the deadline
A brief review should surface blockers while there is time to act. Ask what changed and which decision is needed rather than requesting another status color.
- Review at a fixed cadence.
- Escalate risks with options.
- Update the plan when assumptions change.
Learn from misses
After a missed commitment, examine capacity, clarity, and process. Keep the record factual, then make a concrete adjustment. This makes future promises more trustworthy.
- Distinguish a poor estimate from poor execution.
- Fix one systemic cause.
- Share the lesson across teams.
The commitment review
A healthy commitment can be checked before its deadline. This four-part review makes it easier to surface a blocked result without turning the conversation into a search for fault.
- Outcome
Restate the observable result and who owns its delivery. Separate it from the tasks people are busy doing.
- Signal
Ask what evidence shows progress and what still has to happen. Make uncertainty visible rather than marking it green.
- Blocker
Name the dependency, decision or capacity issue in terms another person can act on.
- Next move
Agree on one change, an owner and a check-in date. Update the commitment openly if its assumptions no longer hold.
Imagine a customer guide due Friday while product details are still changing. On Tuesday the owner flags the missing specification and proposes a shorter first edition. The manager decides whether to narrow scope or move the date; nobody waits for a missed deadline to learn about it.
Avoid status labels without evidence. 'On track' is useful only when the next decision and the remaining risk are clear.
RESEARCH CONTEXT / Google re:Work: team effectiveness and dependability ↗
Try it in your next workweek.
Choose one cross-team deliverable and write its owner, definition of done, due date, and next checkpoint.
Hand back a result that can actually be accepted
A delegated task can reach its deadline and still leave the receiving person unable to use the result. “Finished the draft” says little about its location, unresolved questions or the decision now required. Add an acceptance check to the handoff before the work starts. The check should concern the output, not whether someone stayed busy.
Write the smallest useful contract
Use four fields: the result, the recipient, the evidence and the next decision. A result names an observable deliverable. The recipient is the person who can accept it or ask for a change. Evidence identifies what that person can inspect. The next decision distinguishes approval from information, implementation or a request for clarification.
Specify exclusions alongside the result. If the task is to prepare a supplier comparison, it may exclude choosing the supplier or signing an agreement. That boundary prevents a useful draft from being mistaken for authority to act. Agree where the file will live and what should happen if evidence is missing; a deadline does not settle those questions.
A complete fictional handoff
Imagine a small team preparing a comparison of three meeting-room suppliers. The delegated result is a two-page comparison using the team's supplied requirements. The recipient is the operations lead. Acceptance requires three offers dated in the same week, the same capacity assumption, and a visible “unknown” for any missing cancellation term. The decision requested is whether to seek clarification from one supplier, not whether to place an order.
The sender's note could read: “The comparison is in the agreed folder. All three offers use a 12-person room. Supplier B has not confirmed cancellation terms; that cell remains unknown. Please accept the comparison as a briefing or tell me which requirement is missing. No booking has been made.” This is an invented training example, not a supplier review or a recommendation.
Receiving is an action too
- Open the named result rather than accepting the status message alone.
- Check the agreed evidence and exclusions.
- Reply accepted, needs a specified change, or cannot yet be assessed.
- Name the owner of the next decision and the date for that decision.
If the recipient changes the requirement, record the change as new work. Do not quietly turn “compare three offers” into “negotiate and sign”. A person returning a task should be able to distinguish a correction against the original agreement from an expanded scope.
Try the blank acceptance contract on one low-risk task. At the next handoff, ask which field saved a clarification and which field was unnecessary. Acas guidance provides wider context on agreeing and reviewing work; this contract is an editorial exercise, not a universal management rule or an employment assessment.
Text equivalent: Result and exclusions → Inspect the agreed evidence → Accept, request change, or pause
| Field | Completed example |
|---|---|
| Deliverable and location | Two-page supplier comparison in team folder |
| Recipient and decision rights | Operations lead; briefing only |
| Acceptance evidence | Three current offers, same capacity |
| Excluded actions | No booking or contract signature |
| Unknowns | Supplier B cancellation term |
| Response and next owner | Request clarification; lead owns decision |
Blank worksheet and worked example ↓
Primary context: Acas: reviews and appraisals