When a team shares an office, a lot of coordination happens by accident. You overhear a decision, you notice someone is out, you grab five minutes at a desk. A distributed team gets none of that for free, so the things an office handles implicitly have to be made explicit. That is what a team-norms document is for. This note is specifically about the logistics of distance, where people are, when they overlap, and how the week is shaped. It is a companion to working agreements, which cover the behavioral commitments a team makes to each other; this one covers the mechanics of operating across timezones and a calendar.

Set norms up shortly after a team forms, revisit them whenever someone new joins, and make them big and visible. On a remote team, "big and visible" means a link somewhere everyone already looks, the top of the team chat channel, a pinned resource, the project home. A norms document nobody can find is the same as not having one.

Members and timezones#

Start with the simplest, most useful thing: a list of who is on the team and what timezone each person is in. This is not bureaucratic. When someone needs an answer at four in the afternoon, knowing a teammate is two hours ahead and likely wrapping up changes how and when they reach out. Group people by timezone so the spread is obvious at a glance.

• List each member with their timezone.
• Group by timezone so the overlap and the gaps are visible.
• Update this list the moment membership changes; a stale roster is worse than none.

Core hours and the etiquette around them#

Core hours are the block of the day when everyone is expected to be reachable, expressed in each person's local time so nobody has to do timezone math in their head. The point is a dependable window for synchronous work, while leaving the edges of the day flexible.

What makes core hours actually work is the etiquette around them:

• Schedule meetings inside core hours unless the whole team agrees otherwise.
• Avoid meetings late in the day for the latest timezone. A 4pm meeting for the people furthest ahead can be the end of their workday; respect that by pulling shared meetings earlier.
• Tell the team when you will miss core hours, even for a short absence.
• Announce out-of-office and time off via a calendar invite to the team, not just a passing message. A calendar entry is durable and visible; a chat message scrolls away.

A weekly cadence#

A distributed team needs a predictable rhythm so people can plan their week across timezones. I anchor the week with a recurring cadence, and the non-negotiable rule is that every recurring meeting has a stated purpose. These are the meetings that tend to earn their place:

• Standup keeps the team synchronized on progress. Walk the work, and have each person update their own items, move them, add notes, flag blockers, so the board reflects reality.
• Review shows progress to stakeholders regularly, gathers feedback, and confirms when work is genuinely done. On a remote team this is also how stakeholders stay confident in a team they cannot see at their desks.
• Retrospective gives the team a regular moment to inspect how it is working and adjust the norms themselves.
• Planning is where the team talks through the backlog and decides how much it is willing to commit to for the next stretch.
• Refinement is where bigger items get broken down and their acceptance criteria get pinned down before anyone commits to them.

The frequency is the team's call, daily standup, retro and planning on a cadence that matches your iteration length. What does not vary is the discipline: every meeting on the calendar, recurring or one-off, carries an agenda and a desired outcome. On a distributed team, where a meeting costs people real overlap time they cannot easily get back, an aimless meeting is more expensive than it is in an office. If you cannot state the outcome, do not hold it.

Shared expectations#

Round out the document with the handful of expectations that keep a remote team coordinated:

• Bias toward over-communication. Distance removes the ambient signals an office provides, so say the thing out loud rather than assuming it was noticed.
• Announce work that needs eyes. When something is ready for review, say so in the shared channel rather than waiting to be found.
• Assume positive intent. Text strips tone, and a remote team that reads generously avoids a lot of invented conflict.
• Make decisions visibly. Decisions that include most of the team, made where everyone can see them, keep people who were heads-down from being blindsided later.
• Celebrate wins. A remote team has to manufacture the small moments of shared momentum that an office gets for free.

None of these are exotic. The value is not in the cleverness of any single norm; it is in writing them down together, keeping them visible, and revisiting them as the team changes. For the deeper conversation about how a team builds and honors those commitments, see working agreements.