← Notes
RemoteProcess

On working remote across time zones

Three years into Amsterdam and async-first. A few things I've learned about working with teams in different time zones without losing the texture of collaboration.

28 May 2026

The calendar problem solves itself faster than you expect. The culture problem takes longer.

When I moved to Amsterdam in 2021 and started working with teams across multiple time zones, the first challenge felt logistical: overlapping hours, async updates, knowing when to respond and when to let something sit until morning. That part, you adapt to within a few months.

What takes longer is learning to work without the ambient information that co-location provides for free. The hallway conversation that clarifies direction. The moment you glance at a colleague’s screen and catch a problem before it becomes a decision. The subtle signal of someone’s energy in a meeting that tells you the room hasn’t actually agreed, even though no one said so.

Remote strips those signals out. What you’re left with is: written communication, structured meetings, and whatever trust you’ve built over time.

Writing as a design tool

One shift I didn’t expect: writing became more central to how I work as a designer. Not documentation (that’s different), but thinking-through-writing. When you can’t walk someone through a decision in person, you have to make the thinking visible in a way that doesn’t require your presence to land.

This is harder than it sounds. A good async design explanation isn’t just a Loom recording or a Figma comment. It’s a frame: here’s the problem we were solving, here’s what we considered, here’s what we chose and why, here’s what we’re not doing and why not.

That discipline — of making the decision legible without being there to defend it — has made me a clearer thinker. I’d recommend it even to teams who sit in the same room.

What you lose, honestly

I’m not going to pretend there’s no loss. Spontaneous collaboration is harder. Building trust with someone new takes more intentional effort when you’re not sharing physical space. And there are days when a complex problem would genuinely be solved faster if you could both just point at the same screen.

But I’ve also found that the constraints produce something useful. Async work creates a record. You can trace decisions. You can read back through the context of a choice six months later, which in an office might just be gone — someone’s memory, or nobody’s.


Three years in, I still prefer it. Not because remote is objectively better, but because it suits how I work: deliberate, writing-first, with deep focus time built in by default.