Ten rituals for a remote team of ten: the cadence that replaces an office, with a tool-agnostic and an Atrix version of each
Remote team rituals for a team of ten: weekly update, decision log, demo day, anchor day, out-today, retro and four more, each with a tool-agnostic version.
On this page
A remote team of ten runs on rituals, not meetings: a handful of fixed, written habits that tell everyone what happened, what was decided and who is around, without a call. The ten below are the ones we have kept after four years across three time zones. Each comes in a tool-agnostic version, so you can run it in a doc and a calendar, and the version we run in our own workspace.
The test for a ritual is simple: if it stopped, would someone notice within a week? Everything on this list passes. Several things we tried did not.
Why rituals beat meetings for a small remote team
An office gives you ambient information: who is in, who looks stuck, what the founder is worried about. Remote work removes it, and the usual fix, more calls, taxes the people in the wrong time zone and leaves no record. A ritual is the written, scheduled replacement for one piece of ambient information. Ten of them cover most of what an office provided, in about two hours a week per person.
Three rules made ours stick. Each ritual has one owner, who is the person who notices if it slips, not the person who does the work. Each has a fixed slot: the same day, the same place, the same template, because a ritual that moves is a meeting. And each is written before it is spoken: if there is a call, the writing comes first and the call is for the parts the writing could not settle. Teams that skip the third rule end up with ten meetings, which is where they started.
The other thing to say up front is that ten is the number we landed on for ten people across three time zones. A team of four in one country needs about half of these; a team of fifteen will add a second demo track or a weekly planning call. Take the list as a starting set and drop whatever nobody would miss.
The ten rituals
1. The weekly update, written, same time every week
One post per person, Friday afternoon or Monday morning, three headings: done, next, stuck. Under 150 words. Everyone reads everyone's. This single ritual replaces the status meeting.
Tool-agnostic: a shared doc per week, or a thread in chat with a fixed title. In Atrix: the workspace feed, where an update is posted to the whole team, notifies phones, and sits beside the week's issues and goals in team chat. The MCP server lets people post it from Claude or ChatGPT, which is how half of ours get written.
2. The decision log
Every decision that affects more than one person gets one line: date, decision, who decided, one sentence of why. Appended, never edited. Six months later this log is the most-read page in the company.
Tool-agnostic: one page, newest first. In Atrix: a page in the docs tree with comments turned on, so the discussion stays attached to the line it was about.
3. Demo day, every two weeks
Thirty minutes, on a call, everyone shows something they shipped, even if it is a spreadsheet. No slides. Recorded for whoever is asleep. This is the ritual that makes work visible across functions and the one people say they would miss most.
Tool-agnostic: a recurring calendar event and a recording link. In Atrix: the event sits on the shared calendar, and the cycle it closes shows its burndown so the demo is the end of the sprint, not a separate thing.
4. The anchor day
One day a week when everyone is online for a four-hour overlap, whatever the time zone. Meetings, pairing and anything that needs a live answer are pushed into it. The other four days are quiet by default.
Tool-agnostic: a company calendar entry and a rule. In Atrix: the overlap block is on the calendar, and booking links are set to offer slots only inside it, so externals land there too.
5. Out today
A single place that says who is off, on leave or travelling today, visible before anyone sends a message that will not be answered.
Tool-agnostic: a pinned message updated each morning, or a shared calendar. In Atrix: leave requests in People feed a who-is-out-today view and the calendar, so nobody has to remember to post it; the MCP tool leave_out_today answers the question from chat.
6. The retro, monthly, written first
A retro once a month, not per sprint. Everyone writes three lines beforehand: keep, stop, start. The call is thirty minutes to pick two changes, and the two changes go on the decision log.
Tool-agnostic: a doc with three columns, filled before the call. In Atrix: a page from a template, comments for the discussion, and the two changes become issues in the next cycle so they are not forgotten.
7. The weekly number
One metric, posted every Monday, the same one for a quarter: revenue, active customers, deals in the pipeline, whatever the quarter is about. Seeing it move is what makes goals real.
Tool-agnostic: a line at the top of the weekly update. In Atrix: a key result on the quarter's goal, checked in weekly, visible on the workspace overview.
8. The onboarding buddy week
Every new person gets one named teammate for their first week, a checklist, and a thirty-minute call each day. Remote onboarding fails in silence; this makes the silence impossible.
Tool-agnostic: a checklist doc and a calendar series. In Atrix: the onboarding checklist in People, assigned on the day the hire is converted to a teammate.
9. The quarterly in-person
Three days a quarter in one place, if the budget allows. Not for work; for the conversations that do not happen on calls. If the budget does not allow, a full-day call with no agenda is a weak but real substitute.
Tool-agnostic: a calendar block and a travel budget line. In Atrix: expenses with approvals in People, so the budget is visible before the flights are booked.
10. The founder's note
Once a month, the founder writes 300 words on what they are worried about and what they are excited about. Unedited, unpolished. It replaces the hallway conversation that remote teams never get.
Tool-agnostic: an email or a post. In Atrix: a feed post, where it gets comments and stays findable.
The cadence at a glance
| Ritual | Frequency | Time per person | Live or written |
|---|---|---|---|
| Weekly update | Weekly | 15 min | Written |
| Decision log | As decided | 2 min | Written |
| Demo day | Fortnightly | 30 min | Live, recorded |
| Anchor day | Weekly | 4 h overlap | Live |
| Out today | Daily | 0, automated | Written |
| Retro | Monthly | 45 min | Written, then live |
| Weekly number | Weekly | 2 min | Written |
| Onboarding buddy | Per hire | 2.5 h in week one | Live |
| Quarterly in-person | Quarterly | 3 days | Live |
| Founder's note | Monthly | 10 min to read | Written |
Outside the anchor day and demo day, a person spends under an hour a week on all ten.
What we dropped
- Daily standups on a call. Replaced by the written update. Nobody missed them.
- A separate all-hands. Demo day plus the founder's note covered it.
- Per-sprint retros. Too frequent to produce a change worth logging; monthly works.
- Status dashboards nobody opened. The weekly number is one figure, and people look at it.
FAQ
What rituals should a remote team have?
A written weekly update, a decision log, a fortnightly demo, one anchor day of overlap, a who-is-out-today view, a monthly retro, one weekly metric, an onboarding buddy, a quarterly meetup and a monthly founder's note. Ten in total, under an hour a week outside the live ones.
How often should a remote team meet live?
Twice: one anchor day a week for overlap and a demo every two weeks. Everything else works better written, with a record.
What is an anchor day?
One fixed day a week when everyone is online for a four-hour overlap regardless of time zone. Live work is scheduled into it; the other days are quiet by default.
Do async rituals work across more than two time zones?
Yes, as long as the live ones are confined to the anchor day and recorded. Written rituals have no time zone.
Which tools do you need for remote team rituals?
A calendar, a place for written posts, a page for the decision log and a leave tracker. These can be four tools or one workspace; the rituals are the same.
Next step
See how the feed, calendar and leave view in Atrix team chat and People carry these rituals without extra admin, or start with a decision log page today.