What managing a distributed marketing team across four countries taught me (when I’d never done it before)

Managing a distributed marketing team works when the clarity is written down before anyone needs it, and I learned that by doing it for the first time with no rehearsal. I was the Marketing Manager and sole marketing lead for a global ultra trail running championship that ran across more than five countries, without having run a remote international team for a single day. Part of the job was coordinating 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, and I’ll be precise about the scope: these were four freelance specialists I coordinated, not a salaried department with performance reviews and headcount planning. That distinction counts, and it fed into how I’ve worked as an individual contributor since. What I learned came from a small, high-stakes set-up where everyone was good at their job and nobody was in the same country as me.

There’s research that would have terrified me if I’d read it first: when Vijay Govindarajan and Anil Gupta studied 70 global business teams, they found 82% fell short of their intended goals, and a third rated their own performance as largely unsuccessful. Keith Ferrazzi’s review of the research on virtual teams adds that the best predictor of success for managers leading dispersed teams is having done it before. The same piece also finds that well-managed virtual groups can outperform teams sharing an office, and the gap between those outcomes is mostly about how you set things up.

What’s the hardest part of managing a distributed marketing team?

Losing the office signals that catch problems early; the time zones are the easy part. Coordinating a distributed marketing team across four countries put the earliest and latest people on the roster most of a working day apart, which sounds like the central problem until you 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. It’s also ordinary now: in Buffer’s 2023 State of Remote Work report, 62% of respondents said their immediate team spanned multiple time zones, though it didn’t feel ordinary 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.

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 clock: a tone in the hallway, a confused look in a meeting, the sense that a brief landed wrong before anyone says so. Strip all that out and you’re managing through text, on a delay, across people whose working norms you don’t share.

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 I made the briefs better: specific, self-contained, and written assuming the reader would act on them alone, with no chance to ask a follow-up for hours. Here’s what replaced what:

What an office gives you	What replaced it on a distributed team
A quick chat to clarify the brief	A brief complete enough to act on alone
Spotting confusion on someone’s face	An explicit invitation to challenge the brief
Correcting course over someone’s shoulder	Written standards with examples of what passes
Being there to make the call on the day	A live-event playbook agreed before the race
“Change this” in passing	Written feedback with the reason attached

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 working style reference: 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 compared with a scheduled promotional post. It’s the same instinct I later turned into a full system at a SaaS company, which I wrote about in building editorial standards from zero. Documentation is what protects quality when you can’t be there to correct course, at any scale.

I learned that the expensive way, because early on I assumed shared professional common sense would cover the gaps, and it didn’t: common sense is local, and what’s obvious to a British social writer isn’t obvious to a Brazilian one, and neither of them is wrong. The fix was removing the need for oversight by making the standard legible on the page, and adding more oversight would only have slowed everyone down. Teams that work this way rely on it: GitLab’s handbook on asynchronous communication says “The importance of strong documentation for async communication truly can’t be overstated.”

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.

What does an async-first workflow look like for a distributed marketing team?

Written by default, self-contained and time-zone agnostic, with live calls saved for the few conversations that need them. Once it settled, the rhythm looked like this:

• Briefs went out as complete packages: context, the ask, brand reminders, the deadline in the specialist’s own time zone, assets attached, and nothing went to “let’s discuss on a call” where a document would do.
• During multi-day races nobody had time to wait for me, so live events ran on a pre-agreed playbook: everyone knew in advance what to cover, the tone, the cadence, and who made the call on anything ambiguous. Event-day coverage pulled around three times our usual daily impressions, which I broke down in sports marketing lessons for B2B, and that only worked because we’d made the decisions before the starting gun.
• Feedback was specific, written and reasoned, because “change this” is useless across a delay, while “change this because our voice avoids hype language, see the style note” lets the person absorb the rule and not need me next time.

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

How did cultural differences show up, and what did I get wrong?

In communication style, mostly: in how directness was given and received, and in what people assumed they could do without asking. None of it was dramatic or a stereotype. Erin Meyer’s Culture Map research maps nationalities on scales that include how people evaluate others and how openly they disagree, and I watched both play out without knowing the framework existed.

Some specialists pushed back openly when they thought a brief was weak, which I loved and which made the work better. 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, when 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 say explicitly that questioning a brief was part of the job, not a challenge to my authority, and to ask direct questions instead of waiting for concerns to float up. Ferrazzi’s HBR piece borrows a phrase from James O’Toole and Warren Bennis for what you’re after here, “observable candor”, and on a distributed team the leader has to draw it out deliberately.

How do you build trust with people you’ve never met in person?

Through consistency and follow-through, more than face time. It was what I worried about most and, oddly, the part that went best. 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 instead of a person to blame, because across that much distance blame makes people defensive and quiet, and quiet is exactly what kills a distributed marketing team.

The other half was giving 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 that many time zones would have been impossible and insulting. Distance makes trust fragile, too: Karen Sobel Lojeski’s research on what she calls virtual distance, reported in strategy+business, found trust among team members declined 83% when that distance was high, along with sharp drops in innovation and satisfaction.

What would I do differently now?

Mostly, I’d front-load what I learned the hard way.

I’d build the cultural-communication groundwork in from day one instead of discovering it: 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, which is the same upfront exchange Ferrazzi recommends, and I learned its value by its absence.

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 fundraiser my campaigns supported later beat its target by over €150K, a story I told in content strategy for fundraising, and the operation behind it was tighter because the earlier chaos forced the documentation into existence. I’d rather have had it before the chaos taught me to want it.

And I’d be straight 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 set-up like this, here’s how I want us to work, tell me where it breaks.”

The limit of my story is its scale: four freelancers and one year. Managing a salaried distributed department adds performance reviews, career paths and headcount, none of which I dealt with here, and annual performance reviews bring their own problems.

Which management skills followed me into individual-contributor roles?

Writing briefs complete enough to act on with zero follow-up, and treating ambiguity as a defect to design out. 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 someone can act on alone is now how I write everything: project requests, handoffs to freelancers I coordinate, documentation for whoever inherits my work. Designing ambiguity out, instead of smoothing it over in a quick chat, is the most useful habit I took from that year, and it’s the same instinct behind treating content as a documented system, which I dug into in why you need a content system, not a content team.

It also changed 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 sharpened how I hold brand consistency under pressure, which I later applied when building a brand’s positioning from the ground up, something I covered in building brand positioning from scratch.