A status without another meeting: what people need to know about each other's work
Write useful status updates that show results, blockers and the action a colleague needs to take.
Article language: English

In this article
“Editing is ongoing. Design is ongoing. We are waiting for materials.” A meeting can move to the next item while nobody knows whether the album launch is at risk. A list of activities describes what a team is doing, not what the listener should do.
A useful update addresses its reader: what changed, which result is available, what blocks the next step and whose action is needed by when? Not every update needs every answer, but it should leave the reader better able to understand the current state.
Progress has an object; a blocker has an effect
Imagine a fictional publisher preparing an album. “The layout is 80% complete” could mean most pages have a layout but the cover photo is missing, or that the remaining pages use a template and the cover is approved. The same percentage hides a difference that matters to the next stage.
A better update identifies the result and its boundary: “The chapter layouts are ready for checking; the cover is waiting for one photograph to be selected.” It then explains the effect: the agreed cover version cannot be finalised until that choice is made. The reader can see whether to start work, make a decision or simply take note.
A GitLab team's example of weekly updates combines progress, next steps, blockers and confidence about a milestone. It is one organisation's practice, not a requirement for every company to use the same form or publish on Wednesday.
The publisher's checker and photo chooser need different information. One update can serve both if the recipients and requested actions are clear. “Chapters are ready to check” starts checking; “a photo choice is missing” requests a decision; “the next version follows receipt of the material” identifies a dependency. Ready for checking is not approved, and one finished chapter is not a finished album. A short update must retain that boundary.
A status should not pretend to be a consultation
If the author needs an assessment of two cover versions, “waiting for feedback” is not enough. Identify the material and the question: a direction, a specific photograph or an error? The reader should not have to guess what response would help. A Polish guide to asking a team for help (in Polish) discusses identifying the obstacle and the kind of help needed.
A consultation may require looking at material together; conflicting requirements may require a decision. A status mainly communicates the current state and any next action. Mixing these purposes can turn an information meeting into unprepared design work, with people who have no role in the problem as an audience.
The Polish guide to decision meetings (in Polish) discusses preparing material and defining the decision. When a joint assessment is genuinely needed, invite the appropriate people and say what they need to resolve. A brief update can reveal that need rather than attempting to settle it between unrelated reports.
Distinguish no progress from no new information. Work can remain on plan without a new result every day. Give the next check point rather than inventing small achievements to fill a form.
The reader need not be available at the same moment
GitLab's communication handbook describes asynchronous communication as a starting point while recognising cases for conversation, including complex disagreement or unclear context. This is one company's model, not a promise that written threads can replace every meeting.
Here asynchronous means the author provides material and the reader can consider it and respond later. For that to work the update must stand on its own; it cannot require the author beside the reader explaining which version is meant.

In the fictional publisher, the cover message should point to the current material and state the answer needed. For an urgent question, state the deadline and consequence of no decision. Posting a message does not prove that the authorised person has read it. The photo chooser needs the current options and a question; the chapter checker needs to know which sections can be reviewed. Sending everyone one link may leave coordination to private follow-up messages.
Consider the Polish article on interruptions at work (in Polish). If a team records status and each person soon asks the same question separately, the document has not changed how information is used. It may be hard to find, out of date or too vague. Investigate before adding another report.
Close the loop after a decision. Once the photo is selected, record the outcome and scope. An obsolete blocker invites people to solve it again; deleting it without recording the decision leaves returning colleagues unable to understand the state. Preserve the connection between question, answer and current result.
Colour does not decide who must act
Green, yellow and red can help if the team shares definitions. Otherwise one person may use yellow for any uncertainty and another only for a confirmed deadline risk. Similar symbols then carry different meanings.
Add the effect and requested intervention: “A photo has not been selected; the cover approver must decide before the file is finalised” is clearer than three red dots. If no action is needed now, say so. A percentage also needs a clear object; if the team cannot say what is counted, describe finished and open elements instead of presenting false precision.
A Polish guide to handing over ongoing cases (in Polish) considers what the incoming person needs: actions taken, open dependencies and the next step. A status understandable only to regular meeting participants may not help someone returning after a break.
A blocker may depend on an external item or another role. “We have not received the material needed to finalise the cover” states the situation; claiming someone neglected the project requires different evidence. If scope is unclear, ask for a consultation and provide the material needed to discuss it. A percentage or colour cannot decide what should be produced.
Test the message with the two album readers. Can the checker identify the chapters ready to review? Can the chooser identify the question, options and time to answer? If both still need to ask the author what is expected, the update has not served its purpose.
When a new photograph appears after the question concerned two earlier options, show the new scope rather than leaving the old request unexplained. If a joint discussion is needed, name its subject and arrange it. Repeating “waiting for a decision” does not provide the conditions to decide. After a photo is chosen, make clear that the cover may be unblocked while the chapters are not necessarily approved.
AI can help write a sentence, but needs the right state
A tool using notes can draft an update, but the project must check whether its source includes the current state. An old agreement, a proposal and an approved choice should not become equivalent facts in one polished sentence. The author should confirm the result, scope and intervention. If the tool lacks data about a decision, a clear unknown is better than accepting a plausible but premature conclusion.
The Polish article on auditing AI in meeting notes (in Polish) discusses the connection between source and record. A status is not the same as minutes: it helps the reader understand the state now, while minutes may preserve a wider discussion.
A working language shared across an international team benefits from simple sentences and unambiguous state names. Explain a change in reporting to the people who must use it: what they do differently and where current information is found. Cancelling a meeting alone can scatter the same need into private messages.
For an agreed trial period, replace one type of meeting with a written update and check whether recipients recognise their actions and receive answers in time for the matter. If unclear private questions increase, revisit the content and distribution. Fewer calendar entries alone do not establish that the team understands the work better. Keep meetings where people need to work together on a real problem.







