So we’re trying to build a system where Russian and US creators can work on the same UGC brief, but iterate and refine together remotely. The theory is great: diverse perspectives, richer ideation, concepts that actually work across both markets. The practice is… chaotic.
Here’s what I’ve run into:
-
Communication lag is killing momentum. By the time the Moscow team responds to feedback, the New York team has already moved on or lost context. We’ve tried async docs, but honestly, it just turned into a mess of overlapping edits and confusion.
-
Cultural assumptions are slipping through. A Russian creator will suggest something that sounds amazing to them, but it completely misses for the US audience (or vice versa), and by the time we catch it, we’re already deep into iteration.
-
The brief itself is ambiguous. We’re trying to make it “flexible enough” for both markets, but that flexibility is actually just code for “nobody knows what we’re actually making.”
-
Ownership is unclear. Who’s making the final call? When Moscow and New York disagree on a creative direction, how do we actually move forward?
I feel like we’re trying to co-create something that’s maybe meant to be created separately and then integrated. But I also don’t want to give up on the idea of real collaboration.
Has anyone actually gotten this to work? What’s your process looking like when you’re working cross-border on conceptualization?
Oh, this is exactly the problem I solve for partnerships! And honestly, the issue isn’t the timezone or the language—it’s the structure. You’re treating this like a creative brainstorm when you actually need to treat it like project management with creative input.
Here’s what works: Define roles before the co-creation starts. Not “everyone ideates,” but “Moscow team validates for Russian authenticity, New York team validates for US authenticity, and there’s one creative lead who’s synthesizing.” Make that role explicit and give them decision-making authority.
For async communication, we use this format: “Idea → Russian relevance check → US relevance check → Refined brief.” Takes longer than you’d think up front, but actually saves time because you’re not reworking concepts.
One tactical thing: instead of overlapping edits in Google Docs, we use a version system. Version 1 (Moscow input) → Version 2 (NY input) → Version 3 (Final synthesis). Each version has comments explaining the why behind changes. Sounds bureaucratic, but it keeps everyone on the same page and respects each market’s input.
Also—and this is key—define what “co-creation” actually means. Are you co-ideating (both teams contribute equally to every idea) or are you iterating (one team conceives, one team refines)? They’re different processes, and mixing them is where everything breaks.
From a creator perspective, what’s happening is that you’re asking creators to do work that requires context they might not have about the other market. Like, I can ideate for US audiences pretty instinctively—I live in it, I use the apps, I know the trends. But asking me to suddenly also be an expert on Russian UGC feels like I’m pretending to know more than I do.
What would actually help: give creators from each market a specific, narrowed role. Instead of “co-create the brief,” it’s “Moscow creators: what would make this authentic for your audience?” and “US creators: what would make this scroll-stopping for your audience?” You’re asking for specific input, not asking them to be experts in a market they don’t live in.
Also—and this is just practical—timezone difference means async is your reality. So build the async into your process from the start instead of treating it like a flaw. Like, Moscow team locks in ideas by EOD Tuesday, US team gives feedback by Wed morning (their time), Moscow refines by Wed EOD. Clear timeline, clear handoffs.
The brief ambiguity you’re talking about? That’s because you’re trying to make one brief that satisfies everyone. What if you had one core brief that’s locked (the brand value prop, the product benefit, the tone), and then two executions (one optimized for Russia, one for US)? Not completely separate—they’re siblings, not twins.
One more real talk: I’d rather get a clear, specific brief that’s just for my market than a mushy brief that’s trying to be both. I can execute on clarity. I can’t execute on compromise.
Let me look at this from a process efficiency angle. Your problem has a data layer that I think you’re missing: you don’t have a shared vocabulary for what “works.”
When Moscow says “we love this angle,” they likely mean high resonance with their audience. When NY says “we don’t love it,” they might mean something completely different—maybe low swipe-through on their platform, or it doesn’t match their brand voice, or something else entirely.
Here’s what I’d do: before co-creation starts, build a brief rubric. Like, we’re evaluating every idea block on: authenticity (market-specific), clarity (universal), directness (universal), emotional resonance (market-specific). Score each idea 1-5 on each dimension, and suddenly you have a shared decision framework instead of conflicting opinions.
On the communication lag: that’s real, but it’s solvable with async batching. Your Moscow team locks in feedback in batches (not continuously), NY batch-processes those, etc. You’re trading speed for clarity. And honestly? Given the complexity, clarity wins.
How many creators are you typically involving per market? That changes the complexity significantly.
Also, are you tracking the time-cost of this co-creation process? Like, how many hours of iteration are you burning before you get to a final brief? Because that’s your signal for whether the process is actually working or if you need to restructure.
We went through this exact problem when we were scaling our product roadmap between Moscow and Berlin teams. What we learned: you can’t co-create in real-time across timezones. You CAN co-create asynchronously if you have crystal clear ownership and decision-making.
Our breakthrough was appointing one person (rotates quarterly between the teams) as the “creative decision maker” for that sprint. Not a dictator, but the person who synthesizes feedback and makes the call when opinions conflict. Before we had that, we were stuck in endless feedback loops.
Second thing: we changed from “brainstorm together” to “ideate separately, curate together.” Moscow team spends 2 days on concepts, NY team does the same, then we spend 1 day together (via sync call, during overlapping hours) picking the strongest 2-3 to refine further. It’s faster AND the ideas are better because each team’s bringing their full local expertise.
For brief ambiguity: lock down the “mandatory elements” first. What must be in the brief for any execution? What’s flexible? Once you know that, everything else fits into one of two categories, and the decision-making becomes way easier.
How many rounds of iteration are you typically going through before you lock a brief?
Also, real talk: sometimes what feels like a collaboration problem is actually a planning problem. Like, if your brief is due Thursday and Moscow time is already Friday, you’re not going to have real collaboration—you’re going to have chaos. Make sure timings actually allow for input, not just timeline pressure.
Here’s the agency playbook for this: you’re trying to solve a collaboration problem with communication, and that’s backward. Collaboration requires clear roles, clear ownership, and clear decision-making authority.
What we do: We have a “brief lead” (could be anyone, but one person per brief) who’s responsible for the final output. They solicit input from both markets, but they’re not collecting votes—they’re gathering intel. Moscow’s saying “this won’t land here,” that’s data. NY’s saying “we need more of X,” that’s data. The brief lead synthesizes that into the best possible brief.
Second: we chunk the work. Not “co-create everything together,” but “Moscow conceives ideation, NY validates market fit, Moscow refines, NY locks.” Sequential touchpoints, not overlapping discussions.
Third: we use a decision matrix. When there’s conflict between what Moscow and NY want, we have pre-agreed criteria for breaking ties. It’s not emotional—it’s systematic.
On ownership: I’d make Moscow responsible for Russian authenticity and NY responsible for US authenticity. They’re not equal votes—they’re specialist opinions. If Moscow says “this won’t land in Russia,” that’s not debatable. That’s expert input.
The biggest thing I’d change in your system: stop trying to make one brief that satisfies both markets equally. Make one brief with two audiences, and be explicit about who you’re optimizing for based on each element.
What’s your current ratio of Moscow to NY creators on these briefs?
This is a workflow design problem disguised as a collaboration problem. Let me offer a process framework:
Phase 1: Market-Specific Research (Async, Parallel)
- Moscow team: Audit Russian UGC trends, platform specifics, audience sentiment
- NY team: Audit US UGC trends, platform specifics, audience sentiment
- Timeline: 2-3 days each, independent
Phase 2: Core Brief Development (Async, Sequential)
- Synthesist role (could be either location) drafts core brief based on Phase 1 research
- Moscow team validates for authenticity and cultural fit
- NY team validates for market viability and execution feasibility
- Timeline: 3-4 days total
Phase 3: Iteration (Async, Batched)
- Feedback comes in batches (not continuous), giving synthesist time to integrate
- Maximum 2 rounds of iteration before lockdown
- Timeline: 2-3 days
Decision-making rule: If markets disagree on a brief element, the question isn’t “which market is right?” It’s “which execution-path is this element meant for?” Some elements optimize for Russia, some for US. Make that explicit in the brief.
On ownership clarity: Define it as “market ownership of authenticity, not outcome ownership.” Moscow owns validating that this will feel authentic to Russian creators. They don’t own the final brief.
What’s your current brief-to-execution timeline? And how are you tracking whether the co-creation process is actually adding value vs. just adding steps?
One data point that might help: are the briefs you’re co-creating actually performing better than briefs created market-by-market? Because if the answer is “not really,” then the async structure is just overhead.