“On track.” “Working on it.” “Almost done.” These phrases may be true, but they leave a teammate with the same questions they had before: what moved, what is still uncertain, and whether they need to act.
A useful update is a small piece of shared context. It is written for the person who comes to the project after the conversation is over. It should help them make the next decision without needing a private summary.
Why a status label is not enough
A label is a quick signal. “In progress” tells you where a task sits, but not why it has stayed there. The explanation might be simple: the draft is waiting for a review. Or it might reveal a decision that changes the schedule.
Use the label to scan the work; use a note to explain it. The note does not need to repeat every meeting or message. It needs to preserve the part of the story that affects what happens next.
If someone reads only this update tomorrow, can they tell what changed, what is needed, and who has the next move?
A five-part update that stays short
Start with the outcome the team is working toward, then name the change since the last update. Add the next step, the person responsible, and any open question. These pieces can fit into a short paragraph or a few lines.
- Outcome: What result is this work meant to create?
- Change: What was finished, learned, or revised?
- Next: What is the smallest useful action now?
- Owner: Who can take that action or make the decision?
- Open question: What is still uncertain or blocked?
You do not need all five headings every time. A routine finished task may need only a link and a sentence. Use the full structure when a handoff, decision, or changed direction would otherwise get lost.
Turn a vague update into a useful one
A creative review
Before: “Design is almost done. Waiting on feedback.”
After: “We have two directions for the home page. The warmer option fits the photography and is the team’s current preference. Sam has added both options to the project. Alex will choose a direction by Thursday; the page layout can move forward after that decision.”
The second update is only a little longer, but it answers several questions at once. A teammate can find the work, understand the preference, and see who needs to decide. If Thursday passes without a choice, the reason for the delay is visible.
Attach or link the relevant draft close to the note. Avoid making someone search for the artifact referred to in the text. If a decision is made later, add a new note rather than silently editing the old one; the history helps explain the project’s path.
Know when a note is not enough
Writing is useful when the question can be considered with context and answered without everyone in the room. A conversation is better when people need to explore alternatives together, resolve tension, or notice something neither side has seen yet.
Even after that conversation, leave a short written decision. Record what was chosen, why, and what follows. The conversation helps the team decide; the note helps the decision survive.
More updates do not always mean more clarity. Better context usually does.
Make the next update easier
Choose a natural moment to write: after a review, before handing a task to someone else, or when an open question is answered. Keep the note close to the task or project. Use plain language and one clear next action.
Once a week, read the notes from the perspective of someone joining the project. Can they find the current direction? Can they tell which decision is still open? If the answer is no, write one small update that closes the gap. This is often more valuable than another broad status meeting.
Try the sample workspace to see tasks move between stages, then imagine the short context note you would leave when passing one of those tasks to another person. For a fuller project path, read From idea to handoff.