---
title: "How to manage a remote team: 6 rules from my daily work"
description: "Manage a remote team with six rules from my own work, from fixed working hours to judging results. Each rule comes with questions for your team."
canonical: "https://benjaminschleier.com/en/guides/how-to-manage-a-remote-team/"
language: "en"
---

# How to manage a remote team: 6 rules from my daily work

Remote work

I have spent more than ten years leading teams across several time zones, often from the road. These six rules are what stayed with me.

6 rules · 3 min read

## In short

Six rules from my work with teams across several time zones. They cover fixed working hours, the tool stack, documentation, decision rights, availability and judging work by results. Each rule comes with questions to check your own team against.

## 1. Fixed working hours, wherever you are

Block fixed hours every day, tell your team when they can reach you and protect those hours without compromise. The rest of the day is yours. Place the window so it overlaps with your team's working day, even if that means early mornings or late evenings for you. Then put it in the shared calendar, in your team's time zone. The more I traveled, the more structure I needed. Without it, you work badly and still get nothing out of the place you are in.

### Questions to ask

- Is your availability window in the shared calendar?
- Does it overlap with your team's working day?

**Warning sign** You answer messages around the clock, and nobody on your team knows when you are really there.

## 2. A tool stack everyone uses

Use a chat for daily communication, one tool for project tracking and video calls for anything that needs nuance. The tool matters less than the discipline to use it consistently. I have seen teams with elaborate wikis nobody maintains, and teams with plain spreadsheets that run like clockwork. Write down one sentence per tool saying what it is for. A task that lives only in the chat counts as unassigned.

### Questions to ask

- Where does a task have to be written down to count as a task?
- If someone needs today's decision three months from now, which place will they find it in?

**Warning sign** Information is scattered across five different platforms.

## 3. Document everything, assume nothing

Every recurring task, every standard procedure and every decision framework should live where your team can find it without asking. Then nobody needs you for routine decisions. Start with the questions you get asked most often, the ones that keep coming back. Answer each one once in writing, and next time just send the link. Flights and bad wifi happen, and during those hours nothing should depend on you. Let new people correct the documentation while they are onboarding, because they spot the gaps on day one.

### Questions to ask

- Which questions do you get asked every single week?
- Can a new team member find the answer without you?

**Warning sign** Knowledge lives in private messages and in your head.

## 4. Clear ownership and decision rights

Everyone knows their area and which decisions they can make without checking back. When you are on a twelve-hour flight, the business does not pause. Write down for each role what it decides alone and what it clears with you first. A budget limit helps, up to which nobody has to ask. The result is that features keep shipping and customer emails keep getting answered, even when you are unreachable for a day.

### Questions to ask

- Which decisions does each role make without you?
- Up to what amount does nobody need to ask?

**Warning sign** A decision sits and waits because nobody knows whether they are allowed to make it.

## 5. Say where you are

Share your weekly plan, your time zone and every day with limited availability. Before a trip, settle all pending decisions and name someone to stand in for you. Your team cannot see whether you are at your desk or on a mountain, so write it down. It may feel excessive. It removes the question that wears remote teams down, which is where the founder is and why he is not answering. I do not hide my travels, and that openness has built trust.

### Questions to ask

- Does your team know which time zone you will be in next week?
- Who decides when you cannot be reached?

**Warning sign** Your team learns from an out-of-office reply that you are away for a week.

## 6. Measure the output

Agree on what should be finished by the end of the week, and look at it together. Finished means more than ticked off. Quality counts, and so does whether others can rely on that person. Being online says nothing about any of it. If you lead by the green dot, you get people who tend their status.

### Questions to ask

- What is finished on Friday that did not exist on Monday?

**Warning sign** You keep checking who is online right now.

Why I run companies this way is covered in two blog articles.

[Remote leadership while traveling](https://benjaminschleier.com/en/blog/remote-leadership-while-traveling/)

### Frequently asked questions

#### How do you lead a team across time zones?

With fixed windows when you can be reached, and documentation for everything else. Put the window into the overlap with your team's working day. Decisions that can be made without you are written down in advance, so nobody has to sit and wait for your answer.

#### What tools does a remote team need?

A chat for everyday matters, a tool for project tracking and video calls for conversations that need nuance. Which products you pick is secondary. What matters more is that everyone uses the same tools and that every piece of information has exactly one place where it can be found.

#### How do I know remote employees are actually working?

Agree on what will be done by Friday, and look at it together. Someone's online status tells you nothing about that.

## Keep reading

- [Remote leadership while traveling](https://benjaminschleier.com/en/blog/remote-leadership-while-traveling/) · Leadership · October 6, 2024 · 2 min
- [The benefits of remote-first teams](https://benjaminschleier.com/en/blog/benefits-of-remote-first-teams/) · Remote work · October 6, 2024 · 2 min
- [Choosing a SaaS development partner: 6 checks](https://benjaminschleier.com/en/guides/saas-development-partner-checklist/) · SaaS · 6 checks · 3 min
