What Managing a Distributed Marketing Team Across Four Countries Taught Me (When I’d Never Done It Before)

I took the Head of Marketing job at a global ultra trail running championship without having run a remote international team a single day in my life. The brief was to own marketing strategy and execution end to end across four countries, and part of that meant leading four freelance social media specialists scattered across the UK, the USA, Italy, and Brazil, mostly during the live race events that were the whole point of the operation.

So this is a first-timer’s account, written by someone who figured most of it out while it was already moving. I’ll be precise about the scope, because precision is the point: these were four freelance specialists I coordinated, not a salaried department with performance reviews and headcount planning. That distinction is important, and it ended up shaping how I work as an individual contributor years later. What I learned about running a distributed marketing team came from a small, high-stakes setup where everyone was good at their job and nobody was on the same continent as me.

There’s research that would have terrified me if I’d read it first. In a study of virtual teams, Govindarajan and Gupta found that 82% fell short of their goals, and the Harvard Business Review summary of that work notes the strongest predictor of a manager succeeding is having done it before. The good news buried in the same research is that well-managed dispersed teams can beat co-located ones, and the gap between those outcomes is entirely about how you set it up.

What nobody tells you about managing a distributed marketing team across time zones

The myth is that the hard part is the clock: it isn’t. Coordinating a distributed marketing team across four countries meant the earliest and latest people on the roster were close to a full working day apart, and that sounds like the central problem until you actually do it. The clock is a logistics puzzle with a known answer: you stagger handoffs, stop expecting instant replies, and accept that some decisions get made while you sleep.

What nobody warns you about is how much of your old toolkit quietly stops working. In an office you manage through a thousand tiny signals you never consciously clocked: a tone in the hallway, a confused look in a meeting, the sense that a brief landed wrong before anyone says so; strip all of that out and you’re managing through text, on a delay, across people whose working norms you don’t share. Per Buffer’s State of Remote Work report, 62% of remote workers now sit on teams spread across multiple time zones, so this is ordinary, though it didn’t feel that way in the middle of a multi-day race when a post needed to go out in twenty minutes and the person who could write it best was eight hours behind.

The move that saved me was giving up real-time control and rebuilding everything around clarity written down in advance. Distance turns an ambiguous brief into a missed deadline or an off-brand post, with no quick conversation to catch it, so the briefs got better: specific, self-contained, written assuming the reader would act on them alone with no chance to ask a follow-up for hours.

How do you set quality standards when you can’t look over anyone’s shoulder?

You write them down before you need them, concrete enough that a freelancer in São Paulo and one in Manchester produce the same brand voice without ever speaking to each other.

That meant a real style reference, not a vibe: tone rules with examples of what passed and what didn’t, a list of phrases we never used, formatting conventions, and clear guidance on how live race coverage should sound versus a scheduled promotional post. I leaned on the same instinct I later turned into a full system at a SaaS company, which I wrote about in How I Built Editorial Standards From Zero at a B2B SaaS Company. The principle holds at any scale: documentation is what protects quality when you physically cannot be there to correct course.

I learned that the expensive way: early on I assumed shared professional common sense would cover the gaps, and it didn’t, because common sense is local. What’s obvious to a British social writer is not obvious to a Brazilian one, and neither of them is wrong; the fix wasn’t more oversight, it was removing the need for oversight by making the standard legible on the page. The HBR research lands in the same place: explicit guidelines reduce uncertainty and build trust, because people stop guessing what you meant.

The test I started using: could someone do excellent work from this brief alone, at 2am their time, with me completely unreachable? If the answer was no, the brief wasn’t finished.

The async-first workflow that actually held up

Async-first doesn’t mean never talking, it means the default is written, self-contained, and timezone-agnostic, and you save live calls for the few things that genuinely need them. Once it settled, the rhythm looked like this:

• Briefs went out as complete packages. Context, the actual ask, brand reminders, the deadline in the specialist’s own time zone, assets attached. No “let’s discuss on a call” where a document would do.
• Live events ran on a pre-agreed playbook. During multi-day races nobody had time to wait for me, so everyone knew in advance what to cover, the tone, the cadence, and who had the call on anything ambiguous. Event-day coverage pulled around 3x our usual daily impressions, and that only worked because the decisions were made before the starting gun.
• Feedback was specific, written, and reasoned. “Change this” is useless across a delay; “change this because our voice avoids hype language, see the style note” lets the person internalise the rule and not need me next time.

What I underestimated was how much this demanded of me, not them. Async-first puts the burden on whoever sets the work up to be clear and complete before they hit send. If I was vague, the cost surfaced hours later as wasted work in another country, which is a brutal feedback loop for sharpening your own communication.

How cultural differences showed up in the work, and what I got wrong

Not as stereotypes, and not as anything dramatic; they showed up in communication style, in how directness was given and received, and in what people assumed they could do without asking.

Some specialists pushed back openly when they thought a brief was weak, which I loved and which made the work better, while others held a version of politeness where flagging a problem upward felt presumptuous, so they’d quietly do exactly what the brief said even when they could see it wasn’t quite right. Early on I read that silence as agreement. It was a different default about whose job it is to raise the flag, and that one was on me. I’d built a workflow that rewarded speaking up, then assumed everyone would read “speak up” the same way I did.

Once I clocked it, the fix was to make explicit that questioning a brief was part of the job, not a challenge to my authority, and to ask direct questions rather than wait for concerns to float up. HBR calls this pulling dispersed teams toward observable candor, noting that remote leaders have to actively draw frankness out of people.

Building trust with people you’ve never met in person

This was what I worried about most and, oddly, the part that went best: trust remotely runs on consistency and follow-through, not face time. I paid people on time, every time, which sounds basic and is the fastest way to lose a freelancer’s goodwill if you get it wrong; I gave credit specifically and publicly, and when something went wrong I treated it as a process gap to fix rather than a person to blame, because across that much distance, blame just makes people defensive and quiet, and quiet is exactly what kills a distributed marketing team.

The other half was giving real autonomy and meaning it: these were specialists, hired because they knew their craft and their local audience better than I did, so micromanaging them across eight time zones would have been impossible and insulting. The HBR research backs this with a figure that stuck with me: teams with high “virtual distance” saw trust drop by 83%.

What I’d do differently now

1. I’d build the cultural-communication piece in from day one instead of discovering it. I’d have an explicit early conversation with each person about how they prefer to work, how they like feedback, and how comfortable they are challenging a brief. HBR recommends exactly this upfront “how I work” exchange, and I learned its value by its absence.
2. I’d also invest earlier in the live-event playbook. We got there, but the first race had more scrambling than it needed because I was building the system while running it. The fundraising campaign we eventually ran beat its target by over €150K, and the operation behind it was tighter precisely because the earlier chaos forced the documentation into existence. I’d rather have had it before the chaos taught me to want it.
3. And I’d be honest sooner about what I didn’t know. I spent too long performing competence I didn’t have yet, when the team would have responded better to “this is my first time running a setup like this, here’s how I want us to work, tell me where it breaks.”

The management skills that followed me into every IC role after

I’ve spent most of my career since as an individual contributor, by choice, and people sometimes assume a stint leading a team is irrelevant to that, but it’s the opposite. Writing a brief so good that someone can act on it with zero follow-up is now just how I write everything: project requests, handoffs to freelancers I coordinate, documentation for whoever inherits my work. Treating ambiguity as a defect to design out, rather than something to smooth over in a quick chat, is the single most useful thing I took from that year, and it’s the same instinct behind treating content as a documented system rather than a pile of one-off tasks, which I dug into in Why You Need a Content System, Not a Content Team.

It also rewired how I show up as a teammate; having sat on the management side of the distance, I know how a vague request or a delayed reply lands on someone eight hours away, so I don’t do it to them, and it also sharpened how I hold brand consistency under pressure, which I later applied when I rebuilt positioning from the ground up, something I unpacked in Building Brand Positioning From Scratch.