Ask an agency account lead where a project's timeline actually goes off the rails, and production is almost never the answer they give you. The creative team hits its internal deadlines, the concepts go out to the client on schedule, and everything looks fine right up until the exact moment the client actually has to decide something. Then a project that should close out in a single review cycle turns into three, and it's rarely because the creative work wasn't strong enough to deserve a quick yes. It's because getting five people on the client side to genuinely agree on anything turns out to be its own separate project - one with its own timeline, its own politics, and its own way of eating into the schedule - and nobody on either side of the relationship ever scoped it or billed for it as such.
This is such a common pattern in agency life that it's almost background noise - the running joke about "just one more round of revisions" that everyone laughs at a little too knowingly, because everyone in the room has lived through some version of it more times than they can count. But it's worth taking seriously rather than shrugging off as an unavoidable cost of client services, because the mechanics behind it are specific, repeatable, and mostly have nothing to do with whether the creative work itself was any good. There's also a genuinely well-tested answer for most of it sitting in the decision-science literature, which is worth understanding in some detail before assuming this is just what working with clients is always going to feel like.
Table of Contents¶
- The Real Cost of a Slow Approval Cycle
- Why It Keeps Happening
- How This Actually Gets Fixed
- A Composite Example
- FAQ
The Real Cost of a Slow Approval Cycle¶
The most obvious cost is the calendar time, and it's real, but it's not actually the most expensive part. Extra revision rounds are, almost by definition, work the agency never originally scoped or billed for - "can we see a version with the headline changed" sounds like the smallest possible ask when a client types it into an email, but multiplied across a dozen concurrent accounts and several projects a quarter, that unbilled revision time becomes a direct, ongoing tax on agency margin, quietly eating into the profitability of accounts that otherwise look perfectly healthy on paper. It also compounds scheduling risk across the whole roster in a way that's easy to miss until it's already happened: a project that overruns its approval cycle pushes directly into time that was allocated to the next client's work, which means one indecisive client can quietly degrade service on other accounts that had nothing whatsoever to do with the original delay.
There's a relationship cost too, and it cuts in a direction agencies don't always expect going in. It's tempting to assume that a slow, thorough approval process makes clients feel more genuinely cared for - more consideration, more rounds, more attention to their input. In practice, the opposite is often closer to the truth. Clients tend to remember the projects that dragged through repeated, inconclusive rounds as frustrating and inefficient, even when the eventual creative output turned out to be strong, while a fast, decisive approval process reads as competence and confidence on the agency's part - the sense that this team knows what it's doing and can be trusted to get somewhere. A drawn-out revision cycle doesn't protect the relationship the way it might feel like it does from the inside. It slowly erodes the client's confidence that the agency actually has a clear point of view worth deferring to.
Why It Keeps Happening¶
Every one of the patterns below shows up across agencies of every size and every category of client, which is itself the tell - if this were really about any one difficult client, it wouldn't be this consistent an experience across the entire industry.
Committee Decision-Making on the Client Side¶
Creative work rarely gets approved by one person, and there's usually a legitimate reason for that: it goes to a marketing director, a brand manager, sometimes a CMO, occasionally legal, each of them with a genuine stake in the outcome and a genuinely different lens on what "good" looks like. None of them is wrong to have an opinion, and none of them should necessarily be cut out of the process. But nobody on the agency side gets to simply synthesize five separate sets of feedback into one coherent direction on the client's behalf - that's fundamentally the client's own internal alignment problem to solve. Except in practice, it becomes the agency's problem anyway, the moment those five opinions land in the same inbox and somebody on the account team has to make sense of them well enough to brief the creative team before the next round can even start.
The Agency Stuck in the Middle¶
When two client stakeholders disagree - the marketing director likes one direction, the CMO likes another, and both of them are the agency's paying client in some meaningful sense - the agency doesn't get to simply pick a side without real risk attached. Taking too strong a position in favor of one stakeholder's preference can read as favoritism or overstepping a boundary that was never explicitly drawn but is very much felt. Staying neutral instead means offering no real point of view at all, which is its own kind of failure for a creative partner the client is, after all, paying specifically to have strong opinions on their behalf. There's rarely a clean way out of this bind using judgment alone, because whichever way the agency leans, someone on the client side ends up feeling like they didn't get picked - and they'll remember that, whether or not they say so out loud.
Feedback Arriving Unstructured and All at Once¶
Client feedback usually comes back in exactly the format it was solicited in - a reply-all email thread, a shared comment doc, a live call where everyone reacts to everything at the same time, in real time, in front of each other. That format all but guarantees the agency receives five overlapping, sometimes flatly contradictory reactions to synthesize by hand, rather than a clean, structured read on which direction actually has the most support and why. The busier and more senior the stakeholders involved, the more fragmentary their feedback tends to be too - a half-formed reaction typed out between two other meetings - which makes the agency's synthesis problem meaningfully worse, not better, exactly when there's the least time available to solve it carefully.
The Loudest or Most Senior Voice Wins the Room¶
On a live review call, feedback has a predictable, almost physical way of converging on whoever speaks first or carries the most seniority in the group, entirely independent of whether that person's instinct is actually the strongest read on what will work with the client's real audience. That's not a character flaw specific to any one client - it's simply how groups behave together in real time, well documented across decades of research into group decision-making, and it means a live review often produces a decision that reflects the client's internal hierarchy far more than it reflects which creative direction would genuinely land best with the people the campaign is actually for.
Fear of Pushing Back on a Paying Client¶
When a client's feedback round produces a direction the agency's own creative team privately doesn't believe is the strongest option on the table, there's real professional risk in saying so plainly and directly. Pushing back on a paying client requires either a deep, already-established relationship built on trust, or something more concrete than "we don't think this is right" to actually stand on when the conversation gets uncomfortable - and without either of those in hand, the path of least resistance is almost always to implement the feedback as given, even when the agency's internal instinct, quietly shared around the studio, is that it's a step backward from where the work started.
"Just One More Round" as Scope Creep in Disguise¶
Every individual extra revision round sounds genuinely small at the moment it's requested - one more look, one small change, a quick tweak that surely won't take long. None of them, taken one at a time, feels like scope creep to anyone asking for it. Collectively, though, that's exactly what they are: unbilled, un-scoped work that accumulates specifically because there was never a clear, agreed-upon point in the process where the client was actually required to commit to a direction rather than simply keep iterating for as long as the relationship allows.
How This Actually Gets Fixed¶
Every one of these failure modes has a genuine counterpart in the decision-science literature, and none of the fixes require new software or a bigger budget to implement - what they require is changing how and when feedback actually gets collected in the first place.
Collect Feedback Independently Before Anyone Discusses It as a Group¶
This is the core idea behind the Delphi method, a forecasting and group-decision technique developed at the RAND Corporation in the 1950s specifically to counter the problem of dominant voices skewing a group's collective judgment: gather each participant's independent opinion before they're exposed to anyone else's take on the same question, and only bring the group together afterward, if at all, once independent judgment has already been captured cleanly. Applied to client approval, this means getting each stakeholder's individual reaction first, separately, rather than opening a shared thread or scheduling a live call where the first strong opinion in the room quietly anchors everyone who responds after it, whether or not they'd have landed somewhere different on their own.
Use Forced Comparison to Convert Scattered Opinions Into a Signal¶
Open-ended "what do you think" feedback produces exactly what it sounds like it would produce: scattered, individually reasonable opinions with no common structure underneath them to reconcile against each other. Forced, head-to-head comparison between specific creative options produces something categorically easier to act on instead - a clear, aggregated preference the whole account team can actually read at a glance. This is the same paired-comparison logic formalized by the psychologist Louis Thurstone in the 1920s, still the conceptual basis for market-research methods like MaxDiff nearly a century later, because relative judgments between two options are simply more decisive, and far less prone to individual noise, than open-ended reactions gathered to each option in isolation.
Build a Decision Deadline Into the Engagement, Not Just the Timeline¶
"Just one more round" persists specifically because there's rarely an explicit point in the process where the client is actually asked to commit rather than continue iterating indefinitely. Scoping a fixed number of structured feedback rounds into the engagement itself, upfront, before the project even begins - and treating the collection method as the forcing function that actually drives the group toward a decision - turns what would otherwise be an open-ended negotiation into a bounded process with a visible, agreed-upon endpoint everyone signed up for in advance.
Prepare a Neutral, Evidence-Based Tiebreaker in Advance¶
The agency-stuck-in-the-middle problem is genuinely hard to solve with judgment alone, precisely because judgment is exactly what's already in dispute between the two disagreeing client stakeholders - adding a third opinion, the agency's own, doesn't resolve that dispute, it just adds a third side to it. Structured, independent feedback gathered from a wider group than just the two people disagreeing gives the agency a real third data point to stand behind that isn't simply "our opinion versus yours," which changes the entire shape of the conversation from taking sides to presenting evidence neither original stakeholder generated themselves.
Separate "Which Direction Wins" From "What to Refine"¶
Just as with packaging and logo decisions, conflating "which concept do we run" with "what should we tweak about it" inside the same feedback round is part of what drags client approval into multiple loops instead of one clean cycle. Two genuinely distinct steps - a clean comparative decision first, resolved on its own, then a separate, focused round of specific feedback applied only to the direction that's already been approved - keeps each round doing one job well, instead of asking a single round to do both jobs at once and doing neither of them cleanly.
How These Five Fit Together¶
None of the five principles above are alternatives - a menu an agency picks one item from and skips the rest. They sit at different points in the engagement, which means the real question isn't "which one should we use" but "when does each one apply," and the honest answer is that they're meant to run together, as one connected process rather than five separate tips deployed in isolation.
Two of them are settled before the engagement's feedback stage even begins: building a fixed number of structured rounds into the scope, so "just one more round" has no open-ended default to fall back on, and preparing a neutral, evidence-based way to break ties between disagreeing stakeholders before any specific disagreement has actually happened.
Two of them shape how feedback actually gets collected once there's creative to react to: getting each stakeholder's opinion independently, before anyone discusses it as a group, and asking for that opinion through forced comparison rather than open-ended notes, so five different reactions arrive as one clean, aggregable signal instead of five essays to synthesize by hand.
And one governs how the results get used once they're in: resolving which direction wins first, on its own, before opening a separate, later conversation about what to refine in the direction that won.
| When | What happens |
|---|---|
| Before the engagement's feedback stage begins | Scope a fixed number of structured rounds. Prepare a neutral, evidence-based tiebreaker. |
| While collecting feedback | Get each stakeholder's reaction independently. Collect it through forced comparison. |
| Once results are in | Resolve which direction wins first - refinements come in a separate, later round. |
A Composite Example¶
How It Actually Played Out¶
Picture a five-person client marketing committee reviewing three creative directions for a Q3 campaign. The brief goes out by email with all three concepts attached and a request for feedback by Friday, worded politely enough that nobody feels rushed. By Thursday afternoon, four different replies have come back: one stakeholder likes direction A overall but wants the headline pulled over from direction B, another prefers direction C outright and says so in two lines, a third hasn't responded at all yet, and the fifth chimes in late in the day questioning whether any of the three actually fit last quarter's brand guidelines - a question nobody else had raised.
The account lead spends most of Friday trying to synthesize all of this into something the creative team can actually act on, eventually produces a fourth hybrid version combining elements pulled from two of the original directions, and sends it back out for another round of sign-off - which itself now needs approval from all five people again, several of whom feel, not unreasonably, like their original preference got lost somewhere in the merge. What should have been a single, clean decision has quietly become a second full review cycle, and nobody on either side of the relationship could point to the exact moment it stopped being efficient, because no single step in the process felt unreasonable on its own.
The Same Review, Run Differently¶
Run the same campaign through the five principles instead, starting from the same point: five client stakeholders, the same three creative directions, the same Friday deadline. The difference is built into the engagement before the brief ever goes out - the statement of work scopes exactly one structured feedback round for direction selection, followed by one smaller round for refinement, so nobody on the client side is working from an assumption that revisions can continue indefinitely.
Instead of a reply-all email inviting open-ended thoughts, each of the five stakeholders receives the same short, independent exercise: a head-to-head comparison between the three directions, completed on their own, before seeing how anyone else responded. The marketing director and the CMO still don't agree with each other - that was never going to change - but they're now two data points inside a five-person read rather than the entire visible disagreement, and direction A comes back with a clear plurality once all five responses are in. That result gets treated as settled. It isn't relitigated when the second round opens.
The brand-guidelines question - which, in the original version of this story, arrived late and derailed the whole thread - gets asked directly in that same first round, framed as its own question rather than an aside, and comes back as a clear no-conflict from the stakeholder positioned to actually know. The second, smaller round asks only about refining direction A: which headline variant, does the CTA read clearly. One review cycle closes the loop, not two, and the account lead spends Friday afternoon briefing the creative team on refinements instead of hand-synthesizing five contradictory emails into a hybrid nobody had actually asked for.
FAQ¶
Is a slow approval cycle usually the client's fault?
Not really - it's rarely a character issue on the client's side of the relationship. Committee decision-making, unstructured simultaneous feedback, and the absence of any real forcing function toward a decision would produce this same slowdown with almost any group of stakeholders, at almost any company.
Does pushing for a faster decision risk seeming pushy to the client?
Generally the opposite is true - a structured process that gets to a clear decision quickly tends to read as competence and confidence, not pressure. What actually damages the relationship more often is a drawn-out, inconclusive cycle that leaves everyone uncertain where things even stand from one week to the next.
Why does live-call feedback tend to converge on one person's opinion?
Because group dynamics in real time reliably favor whoever speaks first or carries the most seniority in the room, regardless of whether their instinct is genuinely the strongest read on the work - it's a well-documented pattern in group decision-making generally, not something specific to any one client relationship. It's the same dynamic the Delphi method was specifically designed to counter, by collecting judgment independently before any group discussion happens at all.
What is forced comparison, and why does it help with a client committee specifically?
It means asking each stakeholder to choose directly between options rather than offering open-ended thoughts on each one separately. For a committee, that matters because it converts five different styles and lengths of feedback into one common, aggregable format - instead of an account lead manually synthesizing five separate essays, the team is reading one clear distribution of preference across the whole group.
What's the biggest single change an agency can make without new tools or a bigger budget?
Separating feedback collection from feedback discussion - getting each stakeholder's independent reaction before anyone discusses it as a group - removes most of the anchoring and groupthink that quietly turns a single review into three.
We've written a separate, practical guide on running a faster, structured client approval process - see Ad Creative & Thumbnail Pre-Testing Guide