We’ve gotten frustrated enough with the timezone and async collaboration nonsense that we’re honestly questioning whether remote partnerships are sustainable or if we should just bite the bullet and hire people in the markets we work in.
Here’s the situation: we’re a Russia-based agency with clients in the US and Europe. We’ve got good remote partnerships with creators and managers in different regions, but here’s what actually happens: feedback loops take forever, quality standards drift, and sometimes projects move slower than if we just did them ourselves a few time zones away.
The theory is that async work is efficient. The reality we’re seeing is that it requires so much more documentation, process definition, and clarification than synchronous work. The overhead costs time and money.
For instance, we had a UGC campaign where the creator was in the US, we were coordinating from Moscow, and the client was in Berlin. Every revision cycle took 2-3 days minimum. A simple change to a brief took a full day to clarify because nobody was online at the same time. If we had someone in-house in any of those places, it would’ve been solved in 30 minutes of actual conversation.
On the other hand, we also launched something successful with the same distributed model last quarter, so it’s not like it’s impossible. It just requires discipline.
I’m genuinely curious: for those of you who manage distributed teams or partnerships across borders, at what point did you decide “okay, we need to hire locally instead of keep doing this remote thing”? Or have you made the async model work reliably? And if so, how? What’s the actual system you use to keep things from degrading?
Я видела много teams которые боролись с этим. Вот мое наблюдение: problem не в timezone сам по себе. Problem в том, что люди не любят асинхронную работу и часто ей сопротивляются.
Люди, которые из nature synchronous communicators (те, кто нуждается в немедленной feedback), очень страдают в async системе. Но есть люди, которые процветают в async—они пишут четко, они передумывают перед тем как коммуницировать, они уважают время других.
Мой совет: не говорите всем “давайте работать async”; выбирайте людей, которые хорошо в async. Это разборчивость найма имеет огромное значение.
Также: инвестируйте в инструменты, которые упрощают async. Loom для video explanation, Figma для дизайна feedback, письменные brief которые буквально объясняют контекст. Это не волшебство, но это помогает.
Давайте посчитаем. Время, которое вы потратили на этот async UGC проект (координация, clarifications, feedback loops), поделено на количество deliverables. Это ваша “координационная стоимость”.
Ну, сравните это с гипотетической стоимостью найма человека в нужном timezone на part-time или contract basis. Часто это меньше, чем вы думаете.
Также нужна метрика “качество”. Какова была error rate на async проектах против тех, где была синхронная работа? Если качество страдает, это не просто время—это отката и переделки.
Мое предположение: для 80% ваших работ async может быть эффективно, если вы обустроите процессы. Но для 20% работ, где нужна высокая координация, найм локального специалиста даст лучше ROI. Вопрос в том, какие работы входят в эту 20%.
Я сейчас управляю distributed team для нашего стартапа, и я разделяю вашу frustration. Но я также обнаружил, что проблема часто не в самом async, а в том, что люди не хотят вписать четко и структурировано.
Когда я форсировал всю нашу коммуникацию в текст (не Slack случайные messages, а структурированные документы с контекстом), качество скачком улучшилось. Людям было ясно, что ожидается. Не было недопонимания.
Второе: есть определенные функции, где async не работает. Client communication—это не async функция, это всегда должна быть синхронная. Творческое обсуждение—тоже лучше синхронное. Но execution? Execution может быть полностью async.
Моя гипотеза для вас: наймите одного person в US кто владеет клиентским отношением и творческие decisions. Все execution—outsource async. Это даст вам лучшее из обоих миров.
I’ve been through both models, and here’s what I’ve learned: async works great until your client timeline is compressed. The moment a client needs turnaround measured in hours, not days, async breaks down. So the real question is: what percentage of your work is time-sensitive?
For us, we found that about 30% of our work requires synchronous communication or at least same-day feedback. That 30% is what drove us to hire locally in key markets. We didn’t hire full teams; we hired one senior person per region who could handle the time-critical work and coordinate async for the rest.
It’s a hybrid model, and it’s more expensive than pure async or pure local, but the client satisfaction and project velocity jump are worth it.
One more thing: we standardized our brief and feedback templates obsessively. This sounds small, but templates reduce ambiguity by 70%. When everyone’s working from the same brief structure and everyone provides feedback in the same format, async becomes way more predictable.
Don’t settle for async being chaotic. Make it systematic, and it works better than you’d expect.
As someone who works on campaigns like this, I’m on both sides. I work async with some agencies and synchronously with others. Here’s what makes a difference from my perspective:
Async works when the brief is really clear and when feedback is specific. “Make this more energetic” is useless async feedback. “Lower the pacing, add more jump cuts, keep the B-roll segment at 0:30-0:45” is actionable async feedback.
The agencies that do async well are the ones that invest in clear communication upfront. Like, they spend 30 minutes explaining the brand, the audience, the vibe. That prevents 10 feedback rounds later.
Hiring locally does have benefits, though. Someone in my timezone who can do a quick call to clarify is huge. But not every project needs that. For routine UGC creation? Async works fine. For strategic content initiatives? I’d want synchronous input from the client or strategist.
This is a structure problem, not a people problem. Let me reframe.
Async collaboration works when: (1) Context is clear from the start, (2) Decisions are made upfront, (3) Execution is standardized. It fails when: (1) Context is assumed, (2) Decisions emerge during the process, (3) Every project requires customization.
So the real question isn’t “should we hire locally?” It’s “can we structure our work so it doesn’t require constant decision-making across timezones?”
Here’s what I’d do: map your typical project workflow. Where are the decision points? How many feedback loops? Can you move decisions upstream (into the pitch/proposal phase) so execution is prescribed rather than emergent?
Second: tier your work. Some projects (brand strategy, creative direction) need synchronous input. Some projects (content creation, reporting, routine operations) are pure async. Hire locally for tier 1, keep async for tier 2.
Third: measure the actual cost of async overhead. You might find that hiring one local strategist who removes decision ambiguity costs less than the coordination overhead you’re currently eating.
Finally, async doesn’t work if your culture doesn’t support it. You need people who are thoughtful communicators, who can document decisions, who don’t need constant validation. That’s a hiring discipline, not a process problem. Culture fits matter here.