How to manage distributed teams across locations and time zones

The short version

1. Make writing the default.
2. Agree what each channel is for.
3. Keep all work in one shared workspace.
4. Make status visible so nobody has to ask.
5. Design around time zones.
6. Hold fewer, better meetings.
7. Onboard deliberately.
8. Manage by results, not presence.

A distributed team is any team whose members do not share an office every day: fully remote, hybrid, or spread across several offices or countries. The same principles apply to all of them.

Step 1: Make writing the default

In an office, context travels through overheard conversations. In a distributed team, anything not written down is effectively lost to someone. Encourage people to:

• Write decisions down where the work lives, not only in a call.
• Post updates in shared project channels rather than private messages.
• Explain the "why" behind requests, since the reader may not be able to ask straight away.

Good written communication is a skill. Short, structured messages with a clear ask at the top are easier to act on across time zones.

Step 2: Agree what each channel is for

Distributed teams suffer when the same kind of message could appear anywhere. A simple agreement solves most of it:

Write this down and share it with every new joiner.

Step 3: Keep all work in one shared workspace

When tasks, files, chat and calendars sit in separate tools, a distributed team pays twice: once in searching and again in the delay of waiting for a colleague in another time zone to answer "where is it?". Pick one workspace as the home for project work and organise it by client, project or team. See tool sprawl for why this matters.

Step 4: Make status visible

"What is everyone working on?" should be answerable without a meeting. Use a shared board or task list where each task has an owner, a status and, where needed, a due date. Ask people to mark blocked work with the reason so others can help while the blocked person is offline.

Step 5: Design around time zones

• Map working hours. Know when each person is usually available.
• Set overlap hours. Agree a short daily or weekly window when everyone is reachable for live discussion.
• Default to asynchronous. Outside overlap hours, expect replies within a working day, not minutes.
• Rotate meeting times if some people always end up with early or late calls.
• Use notification controls so people can switch off at the end of their day.

Step 6: Hold fewer, better meetings

Replace status meetings with written updates. Keep live meetings for discussion, decisions and relationships. Always share an agenda beforehand and a written summary afterwards, so those who could not attend are not left behind. Our guide on how to run weekly team meetings covers this in detail.

Step 7: Onboard deliberately

A new remote joiner cannot learn by watching. Prepare a written onboarding plan with the first week's tasks, the key documents to read, the people to meet and the channel rules. Give them access to the right projects on day one, and a named buddy to ask questions.

Step 8: Manage by results, not presence

Green online dots and fast replies are poor measures of contribution. Agree clear goals and deliverables, make progress visible and review outcomes. This builds trust and lets people work when they are most effective.

Common mistakes

• Recreating the office online, with constant calls and expected instant replies.
• Private side channels, so part of the team misses decisions.
• Information across too many tools, which hurts most when colleagues are asleep.
• Always favouring one time zone for meetings.
• Unclear expectations about response times and working hours.

How to do it in Emitii

Emitii is a business workspace that keeps communication, projects, tasks, documents and calendars together, which suits teams that cannot tap a colleague on the shoulder.

• One space per project or team. Each space holds the Board, Tasks, Schedule, Timesheet, Docs & Files, Pulse (the space group chat) and Posts for longer updates.
• Channel rules built in. Pulse for quick project chat with threads and mentions, comments on cards, to-dos, events, docs and posts for feedback, Posts for announcements with "Notify everyone", and direct or group messages for private matters.
• Visible status. Cards show owners, due dates, priority and a blocked flag with a reason. Home shows each person what needs them, what is overdue and what is upcoming across every space.
• Time zones and focus. Notification levels ("Everything", "Involved", "Just me"), quiet hours, "Pause everything" and "Email me what I missed" let people switch off and catch up later. Messages can be saved for later or set to remind you.
• Catching up. In the space Emit tab, ask "Catch me up on this space" when you start your day.
• Onboarding. Admins invite people, add them to groups and departments, and grant space access to a whole group at once. People profiles show availability.
• Mobile. Emitii installs as a web app on phones and computers, with push notifications.

Voice and video calls are coming soon to Emitii. Until then, distributed teams pair it with their existing call tool.

See team communication in Emitii, Emitii for remote teams, the employee onboarding template for a sample setup, and how Emitii differs from a chat-only tool in Emitii vs Slack.