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.