When a rollout is running late, the instinct is to hire more people or push the studio harder. Sometimes that’s the answer. More often the delay hides somewhere else: in the points of the workflow where time disappears without anyone noticing.
People I’ve worked with and respect have a phrase for it: garbage in, garbage out. In global asset rollouts, this is a rule. One small mistake at the start: a wrong color in the master, an incomplete brief, a partial package rushed into production. It doesn’t create one bad asset. It creates hundreds of them, all of which need to be redone. Adaptation at scale multiplies everything, including errors.
Garbage in, garbage out. One mistake in the master becomes hundreds of mistakes in the adaptations. The pre-work is not optional. It’s what makes the scale possible.
These are the seven places I look first.
1. The brief that leaves the client incomplete
A brief that’s missing information doesn’t get put on hold. It gets interpreted. Designers make assumptions about format, spec, tone, and intent. Some of those assumptions are right. Some aren’t. The ones that aren’t generate rounds of revision that could have been avoided with a 20-minute call before production started.
The most common gaps: format specs that don’t match the actual delivery requirements, missing live text versus outlined preferences, no reference for how much adaptation is permitted versus what’s locked, and no clarity on which language has priority when copy length creates layout conflicts.
A brief should answer every question a designer could reasonably ask before they ask it. If it doesn’t, it will cost you time on the back end.
2. Sequential approvals
One person approves. Then the next person reviews it. Then the legal team. Then the regional marketing lead. Each one receives the file, takes a few days, makes comments, and passes it on. If one person is travelling, the whole pipeline stops.
This is the most common source of delay on large-scale rollouts, and it’s entirely structural. The solution is parallel review: all stakeholders receive the file at the same time, with a defined window to respond, and a clear escalation path for conflicting feedback. Sequential approvals feel more controlled. They’re actually slower and produce more conflicting feedback at the end of the process, not less.
3. Files being shared instead of templated
When each market adaptation starts from a different version of the master, exported at different times by different people, you build inconsistency into the process before a single change is made. One studio has a version from three weeks ago. Another is working from a PDF. A third has the live file but an older version of the font.
Templates with locked elements and clearly defined editable zones change this. Each adapting studio starts from the same source, with the same constraints, and the scope of permitted change is explicit. What should take a day takes a day. What shouldn’t be touched isn’t.
4. Adaptations treated as new jobs
A resize from landscape to square is not a new creative job. An adaptation from English to French in an approved layout is not a new design brief. Adaptation is following the master. The creative decisions have been made. The job is to execute them accurately at scale.
That distinction matters practically. When adaptations are briefed as standalone jobs, each with individual timelines, individual quotes, and individual approval rounds, they’re resourced and tracked as if they were original creative work. They’re not.
The right sequence is: approve the formats before adaptation starts. You start with the masters, typically landscape and portrait, and you define all the output formats the campaign needs before anyone adapts anything. Then you approve those formats in English first. Only once the English adaptations are signed off do you proceed to other languages. This way, any structural issues in a format are caught once, in one language, before they’re replicated across 15 markets.
On a 20-market campaign with 8 format variants per market and 4 language versions, that’s a lot of files. The production volume isn’t the problem. The overhead per file is, if each one is being treated as a fresh brief.
Batch these. Brief adaptations in format families. Run approval on a representative set, then apply to the batch. The output is the same. The calendar is not.
5. Starting before the complete master package arrives
One of the most reliable ways to lose time on a rollout is to start adaptation before all the masters are ready. The pressure usually comes from the client. The creative agency has used most of the available time, the deadline is visible, and the client asks whether you can begin with what’s there. The vertical is locked. Can you at least start while the horizontal is still being finalized?
On a global rollout, the answer is no. Not as a matter of stubbornness, but because adaptation works at scale. You take the complete master package and run the full production process in one coordinated batch. If you start with partial masters, you’re running two separate production cycles: one for what arrived first, one for the rest. That means two briefings, two QC rounds, two approval chains. It doesn’t save time. It generates more overhead per asset, not less.
All master files need to arrive together as a complete package. And when they do, the first step is not to start adapting. It’s to check the files.
Every master must be QC’d against the campaign guidelines before adaptation begins. Confirm the files follow the approved creative direction. Check the colors. A designer who didn’t use the hex code and instead picked a color by eye on screen can produce something that looks right on their own monitor and is measurably wrong everywhere else: wrong in print, wrong on calibrated displays, wrong in the adaptation. That error is invisible in the source file and obvious in 200 adapted assets when a client sees them side by side. Check that no component is using an older logo, an unapproved typeface, or an element that shouldn’t be in the campaign at all.
An hour of master QC at intake prevents a week of corrections downstream. The assets that need redoing are the expensive ones, because the mistake was already in the source. This is the garbage in, garbage out principle in practice: adaptation doesn’t fix problems in the master. It copies them, at scale, across every market and every format.
6. QC at the end
The final QC round is where problems that were introduced in week one get discovered in week four. By then, fixing them is expensive. Either other elements have been built on top, or the delivery date is close enough that a fix in one market triggers a cascade of late deliveries.
QC should happen at every stage, not just the last one. A 30-minute check at the brief stage catches spec errors before production. A check after the first round of adaptations catches drift before it’s replicated across 20 markets. A pre-final QC check catches the things that slipped through.
The total time spent on QC doesn’t increase much. The cost of the errors it catches drops significantly.
7. No campaign guardian
Most rollouts have a brand guardian: someone responsible for making sure the creative stays on brand. Fewer have a campaign guardian: someone responsible for the operational reality of getting a specific campaign to market across multiple countries, formats, and languages.
These are different roles. A campaign guardian is not a project manager and not a creative director. They sit between the two. They have an overview of the masters, the countries in scope, and the status of every market’s requests. They know which country is waiting on an approval, which format is blocked, and which market has a local legal requirement that’s about to conflict with the global creative.
Critically, they can communicate in both directions. They translate technical constraints into language the global client understands: why something can’t be done as requested, what the alternative is, and what it costs to deviate from the master. And they translate client direction back into production-ready instructions for the studios.
Without this role, communication fragments. Markets contact the creative agency directly. The agency gives conflicting answers to different markets. The client makes decisions without understanding the production implications. Problems that could be solved in a five-minute conversation instead become revision rounds that run for days.
On a large rollout, the campaign guardian is not overhead. They’re the person who makes the rest of the workflow function.
This is a role I’ve filled on campaigns across multiple markets and languages. If your rollout is missing this function, get in touch. It’s exactly the kind of engagement I take on.
None of these are exotic problems. They show up on almost every large-scale rollout I’ve worked on, and they’re fixable without a new tool, a larger team, or a longer timeline. What they need is someone willing to look at the process before the work starts, not after it’s already late.
FAQ
What does “garbage in, garbage out” mean for asset production?
One small mistake in the master, a wrong colour, an incomplete brief, a partial package rushed into production, does not create one bad asset. It creates hundreds, because adaptation copies the master at scale. The pre-work is not optional. It is what makes the scale possible.
Why are sequential approvals slower than parallel review?
With sequential approvals, each stakeholder receives the file, takes a few days, and passes it on. If one person is travelling, the whole pipeline stops. Parallel review sends the file to all stakeholders at once, with a defined response window and a clear path for conflicting feedback. It is faster and produces less contradictory feedback, not more.
Should adaptations be treated as new creative jobs?
No. A resize or a language swap in an approved layout is execution, not new creative. The decisions are already made. Briefing adaptations as standalone jobs with individual timelines, quotes, and approval rounds adds overhead per file. Batch them in format families and run approval on a representative set.
Can I start adaptation before all the master files arrive?
On a global rollout, no. Starting with partial masters means running two production cycles instead of one: two briefings, two QC rounds, two approval chains. It generates more overhead per asset, not less. All masters should arrive together as a complete package, and the first step is to QC them, not to start adapting.
What is a campaign guardian and why does a rollout need one?
A campaign guardian owns the operational reality of getting a campaign to market across countries, formats, and languages. Not a project manager, not a creative director, but the person between them. They track which market is blocked, which approval is pending, and which local legal requirement is about to conflict with the global creative, and they communicate in both directions. Without this role, communication fragments and small problems become multi-day revision rounds. This is a role I fill on multi-market campaigns. If yours is missing it, get in touch.
// More like this in your inbox
Practical notes on rollouts, localization, and production. No filler.