Make the work clear enough to check
A practical guide to setting observable expectations and delegating with clear decision boundaries.
In Jordan's six-person service team, a handoff between day and evening shifts is a useful place to replace vague requests with a shared, checkable result.
From ambiguous to observable
A worked example for the team's day-to-evening shift handoff.
| Details | Ambiguous | Observable |
|---|---|---|
| Request | “Keep the handoff tidy.” | “Before your shift ends, add each open customer case to the handoff log.” |
| What complete means | “Make sure the next shift has what it needs.” | “Include the case reference, current status, next action, and any agreed customer follow-up time.” |
| Review | “Let me know if there are problems.” | “We’ll review the first three handoffs together at Friday’s check-in and adjust the format if something is missing.” |
Delegate a result, not just a task
Keep ownership and authority explicit in the handoff-checklist example.
Ask a team member to draft a handoff checklist that captures the case reference, status, next action, and follow-up time for open cases.
They may propose the checklist layout and test it with colleagues on both shifts. They should not change the team's official case-recording requirements or promise a new customer response standard.
Agree a short review after the first three uses. The team member brings examples of what worked; Jordan decides whether to adopt the draft or seek the appropriate process owner's input.
Agree the boundaries before work starts
A simple delegation agreement keeps the result and handoff clear.
Name the outcome and the evidence that will show it is complete.
Agree which decisions the colleague can make independently.
State what must come back to you or the relevant process owner.
Set the check-in point and decide together what happens next.
If a boundary is unclear, pause that part of the work and clarify ownership before proceeding.