Distributed teams are rarely short of meetings. They are short of texture: the incidental knowledge of each other that an office supplies for free. These rituals are chosen because they survive repetition — a weekly thing that gets stale in six weeks is worse than nothing, because its decline is visible to everyone.
The schedule
-
Weekly, 10 min
Open the team meeting with a round
Top of the regular team meeting, every week, no exceptions. The facilitator goes first and names a real thorn. Watch the pattern across weeks rather than reacting to individual items.
-
Fortnightly, 40 min
Structured peer consultation in rotating pairs
One rotation, breakout pairs, the no-advice-for-six-minutes rule enforced. This is the ritual that teams defend when the calendar gets cut, because it is unmistakably useful work.
-
Monthly, 45 min
Short talks about something other than work
Six five-minute talks, work subjects banned. Keep a running list of who has spoken and invite privately.
-
Monthly, 20 min
Route recognition to the people who never get it
Random assignments sent a day in advance so the praise is specific. Not weekly — the supply of specifics runs out.
-
Quarterly, 75 min
Remove something that wastes everyone's time
The one longer session. It must end with something actually cancelled while the call is still running.
-
Quarterly, 60 min
Something with no purpose at all
Alternate between them so the register changes. Explicitly no learning objective, and say so — a team can tell the difference between a break and a workshop wearing a hat.
-
December, 45 min
Close the year without assuming anyone's holiday
Either works. The exchange is better for teams under twenty; the wall is better after a hard year, because it shows a group how much they actually did.
What it looks like when it is working
- The weekly round produces a thorn that nobody had raised through any other channel, at least once a quarter.
- People start proposing their own lightning talk subjects rather than being asked.
- The quarterly waste session finds something smaller each time — which means the previous ones worked.
Things that are hard to recover from
- Do not run every ritual at the same time of day for a team across several time zones. Rotate which region takes the awkward slot, and say that you are doing it.
- If attendance at a ritual drops below about two thirds, stop it rather than nagging. A ritual people avoid is doing active harm to the credibility of the rest.