The status update has a simple job: tell people what is happening so they can make decisions or take action. Somewhere along the way, it became a performance.

The corporate status update often reads like a press release written by someone who is afraid of bad news. It is full of momentum language, passive constructions, and carefully worded non-information.

What a useful status update contains

A useful status update answers four questions:

  • What is done? Specific things that are complete.
  • What is in progress? Specific things being worked on now.
  • What is blocked? Anything that cannot move forward without help or a decision.
  • What is next? The specific next actions and who owns them.

That is the whole update. Everything else is optional.

What a performative status update contains

The performative status update replaces information with reassurance. It says things are "progressing well" without saying what progress means. It describes work as "ongoing" without saying when it will be done. It mentions "challenges" without saying what they are or what help is needed.

This kind of update protects the writer from accountability while providing the reader with nothing useful.

The blocked item problem

The most important part of a status update is often the blocked item. This is the thing that cannot move forward without a decision, a resource, or someone else's action.

Many people bury blocked items or omit them entirely because they feel like admissions of failure. They are not. A clearly stated blocker is a request for help. An unstated blocker is a project that quietly stops moving.

The plain-language test: Read your status update and ask: if I received this, would I know what is happening and what, if anything, I need to do? If the answer is no, rewrite it.

Length

A status update should be as long as it needs to be and no longer. For most routine updates, that is a few bullet points. For complex projects with multiple workstreams, it might be longer — but it should still follow the same structure.

If your status update requires a scroll to read, consider whether it should be a document with a short summary at the top.