Async rituals
Building something that recurs without an organiser, across time zones that never overlap.
A ritual is a thing that survives its founder losing interest
Most team traditions depend on one enthusiastic person. When that person gets busy, changes team or leaves, the tradition goes with them — which means it was never a ritual, it was a service. The test is simple: if nobody organised it next week, would it still happen?
Designing for no overlap
Teams spread across enough time zones have no shared working hour at all. Anything synchronous excludes somebody permanently, and it is always the same people. Async by default is not a compromise for those teams — it is the only design that treats everyone the same.
- Everyone gets the same window, not the same instant.
- Reveal together, so nobody is reading results before they have played.
- Let the clock belong to the team, not to the server's calendar.
Closing the loop
An async ritual needs a moment where it comes back together, or it is just a queue. A weekly close — a champion, a summary, a reset — gives the week a shape and a reason to look, and gives people who missed a day a clean place to rejoin.