Updates

Keep people up to date

In a hybrid team, if it is not written down and shared, it might as well not have happened.

Updates are how the team stays aligned between meetings: progress on work, decisions made, blockers, changes to the plan. In a shared office, updates happen naturally through overheard conversations, quick catches in the corridor, and the general visibility of being in the same space. In a hybrid team, none of that is available, so updates have to be deliberate.

Poor update habits create an uneven team: people who are in the office or highly active in chat feel informed, while remote members or people who step away to focus come back to a changed landscape with no record of what happened or why. This is one of the most common sources of exclusion in hybrid teams, and it is usually nobody's fault individually.

Good updates are not about more communication, they are about timely, findable, structured communication. A brief daily note in a shared place, a clear decision log, a short end-of-week summary: these habits keep the whole team in the picture without adding meetings.

Make it explicitAgree on one shared place and format for regular team updates, and make it a standing habit rather than something that happens when people remember.

How strong hybrid teams handle it

The same building block, handled well. These are patterns from teams that work well across locations, offered as illustrations to react to, not rules to copy.

Async standup over a daily meeting

Many hybrid teams replace or supplement a daily standup meeting with a short written update each morning: what you did yesterday, what you are doing today, anything blocking you. This respects time zones, does not require simultaneous availability, and leaves a searchable record.

Update the project, not just the chat

Progress and decisions should land in the project tool where the work lives, not only in a chat message that disappears up the scroll. When the update is attached to the relevant task or thread, anyone can find it later.

Flag changes to the plan explicitly

When priorities shift or a deadline moves, that change should be announced clearly to the whole team, not just mentioned in passing in a thread. Strong hybrid teams treat plan changes as broadcast-level information.

Make the update easy to skip if not relevant

Good updates are structured so people can scan them quickly and read only what is relevant to them. A consistent format (a few bullets, clear headers) makes it possible to stay informed without reading everything in full.

Questions for your team

Use these on your own or in a group. There are no right answers, only better conversations.

How does someone on your team find out what happened while they were away or in deep work?
Where do decisions land after they are made, and is that place findable later?
Are there team members who consistently feel less informed than others, and what causes that?
When priorities change, how quickly does the whole team know, and how?
Does your team have a regular update rhythm, and does it actually work for people in different time zones?

Watch for

Chat is not a updates channel: important information gets buried in the scroll within hours, and people who were not online at the right moment miss it completely.
Updates that only flow from team members to the lead, but not laterally between teammates, create information silos even when individual people are well-informed.
The team members who are least visible in chat are often also least informed, and that gap compounds over time into a significant disadvantage.