The right to disconnect: keeping balance in a distributed team
Remote work removes the commute, but it also removes the office door. When a message can arrive at any hour, a team needs an explicit agreement that work is only one part of a person's life. This guide explains the right to disconnect as a working principle, shows how flexible schedules can be structured around time zones, and gives a checklist for defining balance for yourself.
What balance means when work has no fixed address
A distributed team runs on a long horizon. Treating the work as a marathon rather than a sprint means people need room to recover, and that requires a shared expectation: after hours, you are allowed to be unavailable.
The principle is simple. A job is one strand of a life, not the whole of it, and people need room for the other strands. In practice, that principle has to survive a world with no office, where a text, email, or chat message can reach anyone at any time. The source organization treats this as one of its stated values, and describes it as the foundation beneath its other three: providing a great customer experience, continuously shipping, and taking full ownership of the work. Those specific values belong to that organization; the useful general point is that a boundary only holds if the team's other commitments are designed not to override it.
Balance is hard to define because it is personal. The source gives a spread of examples rather than a single rule: someone whose focus peaks late and who therefore starts later; someone who steps out for a few hours to hike, works from a balcony, or collects a child from school in the afternoon. A policy does not need to prescribe one shape. It needs to protect the space for each person to choose theirs.
Flexible schedules in practice: a split day across time zones
A flexible schedule is not the same as an unstructured one. The useful pattern is to anchor the day around the people you need to reach, then protect the rest.
Consider an engineer based in Australia who trains at 5 am every day, which also lines up conveniently with colleagues on the US west coast. A schedule like this often splits the day, taking time off in the middle and returning in the evening to overlap with Europe. The arrangement is deliberate: it serves both a personal routine and the team's need for coverage, and it shows how a split day can be shaped around two different regions.
That pattern is worth adapting as a template:
- Anchor block: the hours when you must be reachable for a specific group.
- Protected block: the hours you keep for training, family, rest, or focus.
- Overlap block: a second window that covers a different region.
A split day only works if the team agrees that the gap is not a gap in commitment. The schedule is the contract; the messages sent during the protected block are the test of whether the contract is respected.
Why the end of the commute matters more than it looks
The rise of remote work reflects a refusal to spend five days a week in an office and to give up precious time to commuting. The source material records two concrete examples of what that time cost, both from named employees of that organization.
A senior data scientist described roughly 2.5 hours of commuting per day, often eating dinner at the office and hoping for a 30-minute reduction in the trip. A head of finance and business operations described 1.5 hours each way, every day: about two miles on foot to the train, roughly 50 minutes on the train, then a five-minute walk to the office.
Those figures are personal accounts rather than a survey, but they are a reminder that the hours reclaimed by remote work are not abstract. They are the hours that make a training routine, a school pickup, or an evening meal possible. A team that wants to keep its people should treat those hours as part of the compensation, not as slack to be filled with more meetings.
Parents, care, and the asynchronous advantage
For parents who want a career and also want to care for their children, the style of work matters as much as the hours. An asynchronous culture helps because the work does not have to happen at the same moment for everyone, so family commitments can be balanced against the schedule.
In the source material, one engineer described the arrangement this way: family and health come first, so there is no worry when a person or their children get sick. Other team members try to fill the gap until the person is back and ready to work again. That account shows how coverage can work in practice when family and health come first.
That is the operational test of a balance policy. It is easy to state; it is harder to cover for a colleague without making them feel they owe the team an apology. A good team treats coverage as normal, not as a favor.
The other side of the ledger: staying connected
Freedom to choose where, when, and how you work goes a long way, but balance is itself a balancing act. A globally distributed team can find it hard to build relationships and socialize, so the moments when people do meet up deserve deliberate effort.
The source material records several such moments from that organization: a team offsite in Berlin in 2022, another offsite in Mallorca for two engineering groups, and a product manager based in the Netherlands meeting colleagues in New York for co-working time. Each gathering is a chance to build the trust that keeps a distributed team together between meetings.
These are not perks bolted onto the policy. They are the counterweight that makes the right to disconnect sustainable, because a team that has met in person finds it easier to trust that a quiet colleague is resting rather than disengaged.
A checklist for defining your own balance
The source's closing point is that no one else can hand you a definition: the person doing the work is the one who decides what balance looks like and then builds it. Use this checklist as a starting point.
- Name your anchor. Which hours must you be reachable, and for whom?
- Name your protected block. What activity gets the time you are not working, and when does it happen?
- Set a response expectation. What is a reasonable reply window for non-urgent messages, and who decides what counts as urgent?
- Agree on coverage. When you are away, who fills the gap, and how is that arranged without asking permission each time?
- Schedule the human contact. Put at least one in-person or co-working moment on the calendar each period.
- Review it. Balance changes with seasons, family needs, and time zones; revisit the schedule rather than letting it drift.
A team that answers these six questions in writing has something more useful than a wellness slogan. It has a working agreement.
Frequently asked questions
What does a right to disconnect mean?
It means work is treated as only a part of your life, and you are expected to make time for other things that are important to you. In a remote team, the policy has to be explicit because messages can arrive at any hour.
Is a flexible schedule the same as being always available?
No. A flexible schedule is a deliberate arrangement with anchor hours, protected hours, and overlap hours. Being always available is the absence of a schedule, and it is the condition the right to disconnect is meant to prevent.
How does an asynchronous culture help parents?
Because the work does not have to happen at the same moment for everyone, family commitments can be balanced against the schedule. Team members can cover for each other when someone is out, so illness or a family need does not become a crisis.
Is remote work right for everyone?
Not necessarily. The source material acknowledges that remote work is not for everyone. The right to disconnect is a policy for teams that choose a distributed model, not a claim that every person or role fits it.