Working Flexible Hours on a Remote Team

Marcus logs off at 2:30 every afternoon. He collects his daughter from school, runs the homework-and-dinner stretch, and comes back online around 8pm for two quiet hours while his teammates in California are still mid-afternoon. On paper it's a strange day. In practice he's one of the most dependable people on the team, because everyone knows precisely what that day looks like and he never misses the parts that count. The 2:30 gap costs the team nothing. It took me a while to understand why.

The usual story about remote work is that it buys you flexibility: work from anywhere, at any hour, around whatever your life demands. That's the pitch. What nobody tells you is that flexibility is a skill, not a perk, and most people are quietly bad at it. They take a job that could be shaped around the school run and a doctor's appointment, then sit at the desk from nine to five anyway, because that's the only shape of a workday they've ever been handed.

The solid workday was already fiction

A distributed team forces you to notice something, if you're paying attention. The contiguous nine-to-five, everyone online together in one block, is already dead the moment your colleagues span more than a few hours of difference. If you're in London and half your team is in San Francisco, there is no shared nine-to-five to protect. Their morning is your evening. Your afternoon is their dawn. The solid block of overlapping presence that an office used to guarantee simply does not exist, and pretending it does just means you perform being online during hours when the people you work with are asleep.

So the question isn't whether to break the day into pieces. The day is already in pieces. It's whether you arrange them on purpose, around what matters to you, or let them fall wherever the calendar's inertia drops them. Once you see it that way, the split shift stops looking like a special accommodation you have to ask permission for. It's just the honest shape of working async-first across timezones in the first place.

Build the day around the fixed points first

The move that makes flexible hours work is almost embarrassingly simple: find the parts of your life that can't move, and build the work around them instead of the reverse.

Some things in your week are genuinely fixed. School pickup at 3pm. A standing physio appointment. The hours a partner is also working, so somebody has to be with the kids. The two or three slots a week where you actually need to overlap live with a colleague on the other side of the planet. Those are the pegs. Everything else is soft, and soft work can go anywhere there's a gap. Deep, uninterrupted thinking tends to be best in the quiet hours when the rest of the team is offline and nothing is pinging you, which for a lot of people is early morning or late evening, exactly the hours a rigid schedule wastes on checking email that could have waited.

Marcus didn't design his day around his job and then squeeze his daughter into the cracks. He pinned the 2:30 pickup first, then slotted the work around it: a solid morning block, the afternoon off, a short focused evening session that happened to line up beautifully with his West Coast colleagues' working hours. The timezone gap that would have been a problem for someone chained to a London nine-to-five became the thing that made his evening block useful.

The real failure mode is a fourteen-hour day

Now the honest part, because flexible hours have a failure mode and it's worth naming before you fall into it.

When you stop working in one block, the risk isn't that you work too little. It's that the work smears across the whole waking day and never properly stops. You answer a message over breakfast, do the school run, reply to something in the pickup line, work through the evening, check Slack one last time in bed. You've technically carved out the afternoon for your kid, but you spent it half-present, one eye on your phone. That isn't flexibility. It's a fourteen-hour workday with holes punched in it, and it's worse for you than the nine-to-five you were trying to escape.

The split shift only works if the pieces have real edges. When you're off, be off. The gap for the school run is not a "lighter work" window, it's a closed window, and the way you make it genuinely closed is the same mechanics you'd use for protecting your evenings on an always-on team: mute the notifications, set the status, and trust the team's response-time norms so that stepping away for two hours costs nothing. If you can't close a window, you don't have a flexible schedule. You have a long one.

Make your pattern boring and predictable

A split day is only a problem for other people when they can't predict it. That's the whole catch.

If your teammates never know whether you're around, they stop relying on you. They route the question to someone else, leave you off the thread, stop assuming you'll see the thing in time. You become the person work flows around rather than through, and on a distributed team that's a slow, quiet way to make yourself less valuable without anyone ever saying so. The fix is not to work more conventional hours. It's to make your unconventional hours legible, so a colleague can look at your schedule and know, without asking, that you're reachable until 2:30, dark until 8, and back online after. This is where publishing your working hours as shared data earns its keep. A split shift that's written down and consistent is easy to work with. A split shift nobody can see is just you being unreliable with extra steps.

Consistency matters more than the specific shape. A weird schedule that's the same every day is something a team adapts to in a week. A schedule that's different every day, where you're online at random and offline at random, is one people give up trying to track no matter how many hours you put in. Pick a pattern and hold it. Boring is the goal.

Reliability is what buys the freedom

I'll be blunt about the trade, because people skip it. Flexible hours are earned, and what earns them is reliability, not hours logged.

The teammate who can take Wednesday afternoons off without anyone blinking is the one whose commitments land every time. When they say a thing will be done by their end of day, it is. When someone needs them in the overlap window, they're there. They send proposals instead of leaving questions open overnight, so their being offline for a stretch never blocks anyone. They've made themselves trustworthy on output, and a team that trusts your output genuinely does not care which hours you produce it in. You get to disappear for the school run precisely because you've proven you'll deliver the work regardless.

It also means a flexible schedule is not a hiding place. If the work is reliably good and the commitments are reliably met, the odd shape of your day is nobody's business. The moment the work slips, though, the first thing that gets blamed is the schedule, fairly or not, and you'll find the freedom quietly withdrawn. So treat the two as linked, because they are. The best argument for working the hours that fit your life is a track record that makes the question of hours irrelevant. Make your work easy to see and easy to count on, and the when takes care of itself.

If you're the manager

Most of this lands on the individual, but you set the ceiling on it. If flexible hours in theory come with a raised eyebrow every time someone's offline at 11am in practice, nobody will actually use them, and you'll have the costs of distributed work without the one real benefit. Judge people on what they deliver and whether they keep their commitments, not on when the green dot is lit. Say out loud that a split day is fine, then model it yourself by visibly logging off for something in your own life, because your team reads what you do far more closely than what you permit. The person who shapes their work around their kid's bedtime and still ships is not a problem to manage. They're the whole point.

Let Timely Handle the Clock Math

A flexible day gets a lot easier when nobody has to translate it. When you tell the team you're back online at 8pm your time, or you're free to sync at 10am before the school run, Timely reads each person's Slack timezone and shows that moment in their own local clock, so your split shift makes immediate sense to a colleague eight hours away instead of becoming one more thing they have to work out in their head.

Add Timely to Slack — Free · See how it works