How to give updates like a pro: the status OS template

Nobody reads your status update. That is the honest starting point. Your manager skims it for three things: what shipped, what’s at risk, and whether you’re going to need them to get involved. Everything else is noise you wrote for yourself.

Getting this right matters more than almost any other communication habit in your first year. Status updates are the most frequent signal your manager has about how you think. Send bad ones long enough and they start filling in the gaps with their imagination, which is never flattering.

What a status update is actually for

A status update is not a diary entry. It’s a report to a decision-maker who has twelve other things to track and limited time to read.

Your manager is trying to answer: can I trust this person to own this without me watching closely? A well-structured update answers that question every single week without them having to ask. A vague one makes them nervous. A missing one makes them assume the worst.

What good looks like vs. what bad looks like

Bad: “This week I worked on the onboarding flow and had some calls with the design team. Still trying to figure out the timeline. Also started looking into the vendor thing.”

That update takes 15 seconds to read and produces zero information. The manager walks away more anxious than before.

Good:

• Shipped: Finalized spec for onboarding flow v2, approved by design
• Next: Hand off to engineering by Thursday; vendor evaluation complete by EOW
• At risk: Legal review may push vendor sign-off; flagging now, not yet a blocker

That update takes eight seconds to read and answers all three questions. No follow-up needed.

The format is the whole game. The words inside the format matter much less than picking a format and using it consistently.

The status OS template

Use this every week, every project. Paste it into Slack, email, or your 1:1 doc.

Three rules for using this well. First: “At risk” is not a confession booth. You’re not admitting failure, you’re preventing surprises. Flagging a risk before it becomes a problem is the senior move. Second: “Shipped” means done, not in progress. “Continued working on X” is not shipped. If nothing shipped, write “Progress: validated requirements with X, awaiting review from Y.” Progress over silence, always. Third: keep the whole thing under six bullet points. If it takes longer than 30 seconds to read, you’re writing a memo, not a status update.

The compounding effect

This format starts paying off around week four or five, when your manager stops asking “so where are we on that?” because the update is already in their inbox. That question disappearing is not a small thing. It means they’ve categorized you as someone who handles their own visibility, which is the category you want to be in.

I’ve seen people write sprawling paragraph updates every Monday and wonder why their managers still peppered them with check-in questions. The updates weren’t wrong, they were just expensive to read. One well-structured six-bullet update lands harder than three paragraphs of context.

The status OS isn’t exciting to set up. It’s one of the least glamorous habits in this whole archive. But it compounds quietly, the way all the good habits do, and by the time your first review comes around, your manager has 26 weeks of receipts on what you shipped.

Further reading

• The manager 1:1 agenda that uses this as your weekly status slot
• The two-sentence recap habit that makes you look senior
• Keep a wins log even if you hate the idea