When people hear "distributed studio" they imagine a coordination problem. It is not really a coordination problem. It is a writing problem. Almost every difficulty we have encountered running across three continents has been resolved by writing something down better.
The time zones are the easy part
Boulder is GMT-7. Manchester is GMT+0 (or +1 in summer). Islamabad is GMT+5. There is a four-hour overlap window where all three studios are awake — roughly 9am to 1pm Mountain Time. We don't try to expand it. We use it for the things that genuinely need everyone, and we move everything else to writing.
The hidden cost of synchronous meetings is not the meeting itself. It is the writing that doesn't happen because the meeting absorbs the energy that would have gone into the writing. Distributed studios that try to be fully synchronous burn out their best people. Distributed studios that lean on writing scale calmly.
What writing well does
Three things. First, it forces clarity. You cannot ramble in writing the way you can in speech. By the time something is written down well, you understand it better than you would have if you had only spoken about it. Second, it survives the time gap. A decision documented in a doc at 5pm Islamabad time is readable by Boulder at 6am the next day, without anyone losing sleep. Third, it scales. New people joining the team can read the project's history and catch up; they cannot watch every old meeting.
Distributed studios that try to be fully synchronous burn out their best people. Distributed studios that lean on writing scale calmly.
What we got wrong
For about the first year, we tried to run things as if the three studios were one studio. Shared standups, shared retros, shared everything. It mostly didn't work. The studios are not one studio. They are three studios that collaborate on a shared portfolio. Once we accepted that, things settled. Each studio has its own cadence, its own internal rituals, its own way of working. The shared layer is thinner than we expected. The local layer is thicker than we expected.
The asymmetry that matters most
It is not the time zone. It is the language asymmetry. We work in English across all three studios, but English is a first language for about half the team. We have learned to write more plainly, in shorter sentences, with fewer idioms. This has made our client-facing writing better too. Plainness is not a constraint we accepted reluctantly. It is, in retrospect, an improvement.
What we would tell ourselves two years ago
Three things. Hire the writer first. Not the marketer who writes — the writer who can also do the work. Their fingerprints will be on everything: briefs, proposals, internal comms, client emails, the website. Resist the urge to over-process. Most coordination problems do not need a new tool. They need someone to write a one-page note clarifying the decision. Treat the local layer as the unit. The team in Manchester is a team. The team in Islamabad is a team. The team in Boulder is a team. The studio is the loose federation of the three.
Most of what is written about distributed work assumes the unit is the individual contributor. In our experience, the unit is the studio. Get that right and most of the harder problems become easier.