Why updates get delayed
An update can feel like another large task when the writer has to reconstruct the whole project, decide how much context is enough, and explain a problem perfectly. The delay then makes the eventual message harder.
Use one fixed structure
- Done: the change since the last update.
- Next: the next visible action and expected timing.
- Blocked: the decision, access, information, or capacity needed from someone else.
| Line | Weak update | Useful update |
|---|---|---|
| Done | Made progress on the options | Compared both approved options against the agreed criteria |
| Next | Will keep working | Draft the recommendation by Thursday afternoon |
| Blocked | Waiting for information | Need the budget limit from the project owner before finalizing costs |
Example without overexplaining
Done: compared the two approved options. Next: draft the recommendation by Thursday afternoon. Blocked: need confirmation of the budget limit before finalizing the cost section.
Attach the update to a cue
- Choose a recurring project event: end of day, team check-in, or handoff point.
- Keep the template where the work already happens.
- Send early when a blocker changes the promised date.
- Ask the recipient whether the level of detail is useful.
Use the organization’s controls
For regulated, safety-critical, legal, financial, or clinical work, a three-line update does not replace required documentation, escalation paths, or formal review. Follow the organization’s process first.
Send the smallest useful update
For one current low-risk project, write three lines now. Make Done verifiable, make Next observable, and make Blocked a request to the person or role that can change the state. Send it through the normal work channel before the blocker changes an agreed date.
If there is no blocker, write “Blocked: none known” only when you have actually checked the dependencies that matter. A short update earns trust by exposing uncertainty, not by sounding certain.
Sources and further reading
Sources support the health and diagnostic context. Practical workflow suggestions are low-risk editorial adaptations, not clinical treatment.