Four cities, one codebase.
How a flat team hands work across Berlin, Dubai, Kuwait and Calicut without meetings.
Our working day is eleven and a half hours wide. Calicut opens it, Berlin closes it, and Dubai and Kuwait hold the middle. On paper that looks like a coordination nightmare. In practice it’s the closest thing we have to a superpower — but only because we gave up on meetings first.
The rule is simple: state lives in the repository, not in anyone’s head. If a decision isn’t written down — in the PR, the issue, or the design doc — it didn’t happen. Handoff is not a call at an hour that’s cruel for someone. It’s a well-written trail.
A time zone gap is only a problem if the work can’t speak for itself.
The mechanics
Each project has one thread, not seven channels. Every day ends with a short written close-out: what moved, what’s blocked, what the next city should pick up. Reviews happen asynchronously with a hard 12-hour SLA — which the geometry of the map turns into “overnight” for everyone.
We do keep one ritual: a single 30-minute call each week, at the only hour that’s civilized in all four cities. It is deliberately not a status meeting. Status is in the repo. The call is for the things writing is bad at — doubt, taste, and the occasional argument.
Why flat matters here
Distributed hierarchies stall because approval has a time zone. A flat team doesn’t wait for a lead to wake up. Whoever holds the context makes the call, writes it down, and the sun keeps moving.