Synchronous Collaboration

Collaborative sessions to get things done

A synchronous session is the most expensive thing a hybrid team does, so it should earn its place.

Synchronous collaboration is any time the team is live together: a video call, a workshop, a brainstorm, a standup. These sessions are powerful for things that genuinely benefit from real-time exchange: building trust, resolving conflict, making a decision that needs everyone in the room, doing creative work together.

In a hybrid team, synchronous time is a shared resource that has to be used carefully. It is expensive: it requires everyone to be available at the same moment across time zones, it interrupts deep work, and it often leaves remote participants in a harder position than office participants unless the session is designed well.

The strongest hybrid teams are deliberate about which moments need sync and which do not. They protect synchronous time for what it does best, and they invest in making those sessions high-quality so the time is genuinely worth it.

Make it explicitAgree on what kinds of work actually need synchronous time, and make that the filter for whether you call a meeting.

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.

Start with a clear purpose

Every sync session should have a stated goal that could not be achieved async. If the agenda could be a well-written document, it probably should be. Teams that name the purpose before scheduling tend to have fewer meetings and better ones.

Design for the remote participant

The person joining by video is the default design constraint. That means camera on, equal speaking turns, shared docs visible to everyone, and no side conversations in the physical room that the camera cannot pick up.

Close with written outputs

At the end of every sync session, the decisions and next steps go into writing immediately, in a shared place. This is the bridge back to async, and without it, the session might as well not have happened for anyone who was not in it.

Protect the overlap window

Distributed teams with time-zone differences often have a narrow window when everyone is online. Strong teams protect that window for the sync work that truly needs it, rather than filling it with check-ins that could have been an update.

Questions for your team

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

Which meetings on your current calendar could not have been a document or a short async update?
How do remote participants experience your synchronous sessions compared to those in the office?
When you finish a meeting, does everyone know what was decided and who is doing what next?
Is there a shared understanding of when it is worth calling a meeting versus using another channel?
How do you make sure people in other time zones are not systematically excluded from the sync moments that matter?

Watch for

A meeting that serves as a status update is almost always a sign that async documentation is not working well enough.
Hybrid sessions with a mix of in-room and video participants often have an uneven dynamic that nobody names: the room talks to the room and the video windows become observers.
When sync time is overloaded, people start multitasking in calls, which means the session is doing neither job well.