Skip to content
All posts

Daily Updates That Your Team Actually Reads

Most standup updates are a list of tickets nobody listens to. A good daily update takes two minutes to write and saves your team hours, if you write it for the people reading it instead of for yourself.

Harshil Moradia

5 min read

Daily Updates That Your Team Actually Reads

Every team has some version of the daily update. Maybe it's a 15-minute standup call, maybe a Slack thread, maybe a bot that asks "what did you do yesterday?" at 9am. And on most teams, it quietly turns into a ritual: everyone recites ticket numbers, nobody really listens, and the one thing that actually mattered gets lost between "continued working on the API" and "will keep working on the API."

It doesn't have to be like that. A daily update is one of the cheapest tools a team has for staying in sync, but only if you write it for the people reading it.

Who the update is really for

It's tempting to treat the daily update as proof you were busy. That's the wrong audience. The real readers are:

  • Your teammates, who need to know whether your work affects theirs.
  • Your lead or manager, who needs to spot problems early, while they're still cheap to fix.
  • Future you, who will be grateful for a written record when someone asks in three weeks why the migration slipped.

None of them care how hard you worked yesterday. They care about what changed, what's next, and whether anything is stuck.

The three-part update

The classic format still works, as long as each part says something real:

Done: what changed since the last update, as outcomes rather than activity.

  • Weak: "Worked on the login bug."
  • Better: "Found the cause of the login bug (session cookie expired early on Safari). Fix is in review: PR #482."

Next: what you'll do today, specific enough that someone could notice if it changes.

  • Weak: "Continue on the dashboard."
  • Better: "Wire the dashboard filters to the new API. Should be ready for review by end of day."

Blocked / need help: the part that matters most, and the one people skip most often.

  • Weak: (nothing, because saying you're stuck feels bad)
  • Better: "Blocked on staging DB access. @sam, can you add me to the group? Without it I can't test the migration."

Say "blocked" early

The most expensive sentence in software is "I've been stuck on this for three days." Almost every time, someone on the team could have unblocked it in ten minutes on day one.

A good rule: if you've been stuck for more than half a day, it goes in the update. It's not a confession. It's information. And name a person when you can. "Need help with X" goes to everyone, which means it often goes to no one. "@alex, do you know how the retry queue is configured?" gets answered.

Flag risks, not just status

The most useful updates mention things that might go wrong before they do:

  • "The payment API docs don't match what it actually returns. Might add a day."
  • "This touches the auth middleware, so whoever reviews it should know that code."
  • "I'm out Friday, so if this isn't merged by Thursday it slips to next week."

A lead who hears about a risk on Monday can adjust the plan. One who hears about it on Friday can only apologize to someone.

Keep it short and skimmable

A daily update should take under two minutes to write and thirty seconds to read.

  • Use bullets, not paragraphs. Readers skim.
  • Link instead of explain. A PR or ticket link carries the details for anyone who wants them.
  • Skip the routine. "Attended meetings" and "answered messages" aren't news.
  • Bold the blocker. If one line needs action, make it impossible to miss.

In a spoken standup, the same applies: give the short version and offer to go deeper afterwards with whoever needs it. A standup is for finding out who should talk to whom, not for solving problems with eight people watching.

Remote and async teams

On a distributed team, the written update often is the team's shared picture of the work. A few habits help a lot:

  • Post at a predictable time, ideally early in your day, so people in other time zones can respond before you log off.
  • Write for someone who wasn't in yesterday's call. Spell out the context instead of saying "the thing we discussed."
  • Read everyone else's too. Updates only work if people read them. Replying with a quick "I can help with that" is how blockers get cleared without a meeting.

Why it's worth the two minutes

Clear daily updates do more than keep a team in sync. They build trust. When your lead can see, every day, what you're doing and where you're stuck, they stop needing to check in on you. You get more autonomy, fewer surprise meetings, and a reputation as someone who's easy to work with.

And when review season comes around, you'll have a written record of everything you shipped, one short update at a time.

Thanks for reading. If this was useful, the newsletter below is the best way to catch the next one.

Keep reading

More essays