How to Write a Weekly Update
Your Team Actually Reads
Most team updates are either too long, too vague, or so positive they stop being useful. The weekly update that works is honest, short, specific, and written for the person reading it — not for the person writing it. Here’s the format, the prompts, and the habits that make it stick.
- Why most weekly updates fail
- The format that takes 10 minutes to write and 2 to read
- What to include — and what to cut
- The founder update vs the team update
- How to make honesty feel safe
- Using AI to write faster without losing your voice
- Making the habit stick
Why Most Weekly Updates Fail
Most weekly updates fail for one of three reasons: they’re too long (people skim or skip), too positive (people stop trusting them), or too focused on activity rather than outcomes (people read them and don’t know if things are going well or not).
The other common failure: updates written for the writer rather than the reader. The person writing wants to show they were busy. The person reading wants to know what to pay attention to, what’s at risk, and whether the company is on track. These are different documents.
The update that works is short enough to read in under 2 minutes, honest enough that the team can calibrate their own decisions based on it, and specific enough that it’s clear what “good” and “not good” look like for the current period.
The weekly update that nobody reads is usually the one nobody needed to write. If your team is in the same room every day and communicating constantly, a formal update may be overhead rather than value. The update matters most for remote teams, fast-growing teams, and founders who spend significant time away from the day-to-day.
The Format That Takes 10 Minutes to Write and 2 to Read
Five sections, none of them more than 3-4 bullet points. The discipline to keep it short is the discipline that makes it read.
This week’s headline: One sentence. The most important thing that happened or didn’t happen this week.
What went well: 2-3 specific things. Not “good progress on product” — “shipped the new onboarding flow to 100% of users, first feedback is positive.”
What didn’t go well: 1-2 honest things. This is the section most updates skip. It’s also the section that most builds trust. A team that never sees problems in updates learns to distrust the updates.
Next week’s focus: 2-3 priorities. Not a task list — the outcomes you’re aiming for.
What I need: Optional, but powerful. A specific ask from the team — a decision needed, a blocker to help clear, information required.
“Write a weekly team update based on these notes from my week: [paste rough notes — what happened, what shipped, what went wrong, what’s coming next week]. Format it with these five sections: Headline (one sentence), What went well (2-3 bullets, specific), What didn’t go well (1-2 bullets, honest), Next week’s focus (2-3 priorities), What I need from the team (1 specific ask if applicable). Total length: under 200 words. Honest and direct — not a PR document. Use plain language.”
What to Include — and What to Cut
Include: Key metrics that moved (or didn’t), specific wins that the team contributed to, honest problems that the team should know about, decisions made that affect how people work, priorities for next week.
Cut: Activities that don’t connect to outcomes (“had 12 meetings this week”), problems you’ve already solved that don’t affect the team, any information the reader can’t act on or use, anything that’s better communicated in a direct conversation rather than a broadcast update.
The test for each bullet: if you removed this line, would a team member’s understanding of the week change? If the answer is no, cut it.
The Founder Update vs the Team Update
The update the founder sends to the team and the update each team member sends up to the founder serve different purposes and should have different formats.
The founder-to-team update is about context and direction — what the company is dealing with, what the priorities are, what the founder wants the team to know about the outside world (investor conversations, market changes, customer feedback patterns).
The team-to-founder update is about execution and blockers — what was done, what’s stuck, what the person needs. It’s operational, not strategic.
Both should be short. Neither should substitute for the conversations that context and complexity actually require.
How to Make Honesty Feel Safe
The team update culture you create is modelled on what the founder puts in their own update. If the founder’s update is always positive, the team learns that negative information isn’t welcome in updates. If the founder’s update includes honest misses and things that didn’t go as planned, the team learns it’s safe to do the same.
The founder who writes “we lost a customer this week — here’s what I think happened and what we’re doing about it” models the honesty that makes team updates genuinely useful. The founder who never mentions problems trains the team to hide them.
“This was a difficult week. Here’s what happened: [describe the challenges, misses, or problems honestly]. I need to write a team update that: acknowledges what went wrong specifically, explains my understanding of why without making excuses, shares what we’re doing about it, and doesn’t end on fake positivity. The goal is to keep the team informed and confident that leadership has a handle on things — not to alarm them, but not to pretend either. Under 200 words.”
Using AI to Write Faster Without Losing Your Voice
Weekly updates are a good candidate for AI assistance — they’re repetitive in format, they’re based on notes you already have, and the writing itself doesn’t need to be brilliant, just clear. The risk is that AI-generated updates lose the personal tone that makes team updates feel like communication rather than corporate communication.
The workflow that works: take 5 minutes to write rough notes about the week — bullets, fragments, whatever comes. Paste them into an AI prompt. Review the output and add 2-3 personal touches — a specific name, an observation that only you would make, an honest sentence that AI would soften. The result is faster than writing from scratch and more personal than pure AI output.
Making the Habit Stick
The weekly update is one of those habits that’s easy to skip once and hard to restart. The first skipped week feels fine. By week three without an update, the team has filled the information vacuum with their own assumptions — usually more negative than reality.
Block 30 minutes on Friday afternoon. That’s the update slot. Every week, regardless of what happened. The discipline of publishing an update even on a bad week — especially on a bad week — is what builds the trust that makes the update worth reading.
Get 50 more prompts for team communication, ops, and running a lean startup — free.