A new client came to us recently in a state I recognize immediately.
Frustrated. Slightly embarrassed. And holding a piece of work that had been going backwards and forwards internally for two weeks. It was a small job (not a campaign, not anything with real strategic stakes) that nobody could get finished.
They handed it over with something close to “just deal with it.”
We dealt with it. One round of edits. Published. Fifteen minutes, start to finish.
The client was relieved. Probably a little annoyed too, in the way you get annoyed when something difficult turns out to be straightforward, because it raises the obvious question of why it wasn’t straightforward the first time.
That’s the question I want to answer here. Not to make anyone feel bad about it. But because understanding why it happened is the only way to make sure it doesn’t keep happening.
What was actually going on
The easy explanation is that the internal team wasn’t good enough, or the brief was bad, or the stakeholders were difficult. But that’s almost never the real story.
The real story is cognitive. And it has a name.
Psychologists call it functional fixedness, a bias first documented by Karl Duncker in 1935 and consistently replicated since. The short version: the more familiar you are with a problem, the harder it becomes to see solutions outside your existing frame. Your brain has already decided what the problem is, what it needs, and what done looks like. New information gets filtered through that frame rather than genuinely evaluated.
The more rounds you run, the worse it gets. There’s a related phenomenon called the Einstellung Effect: the negative influence of prior attempts on subsequent ones. Every failed revision leaves a residue. The next round starts contaminated by what didn’t work before. You’re no longer solving the problem. You’re solving the accumulated history of attempts to solve the problem.
By round six, a small job feels enormous. Not because it got harder. Because everyone’s relationship with it did.
You’ve seen this before, just not in a brief
There’s a specific corner of the internet dedicated to Photoshop requests gone wrong. The format is always the same: a completely reasonable request meets a very literal interpretation, and the result is technically correct and entirely useless.
“Can you remove my ex from this photo?”
The ex is removed. So is the arm around the subject, and roughly a third of the image. The request was followed to the letter. The outcome made everything worse. And, crucially, whoever executed it couldn’t see why. They did exactly what was asked.
All photos by James Fridman (@fjamie013) via Bored Panda
This is funnier when it happens on the internet than when it happens in your content pipeline. But the underlying behaviour is identical. When people are too close to a problem (too embedded in the history of it, too loaded with prior feedback) they start executing the literal instruction rather than solving for the actual need. Not from lack of skill, but because accumulated revision history crowds out clear judgment.
And then there’s the committee problem
Layer on top of this the way internal creative review typically works, and you start to understand how a small job disappears for two weeks.
When multiple stakeholders review work, and when all of their input is treated as equally valid, the work stops moving toward a solution and starts moving toward consensus. These are not the same destination. In that two-week loop, nobody was being obstructive. Nobody was deliberately making it harder. The process itself was the problem. Feedback from multiple sources, no clear decision-maker, each round adding new direction without resolving the previous round’s.
The result is what it always is: work that moves, just never forward.
What we do differently, and why It works
When that job landed with us, we weren’t smarter than the people who’d been working on it. We were just structurally better positioned to solve it. That’s not an accident, it’s something we’ve deliberately built for. Here’s what that looks like in practice.
Pattern recognition from volume. We see similar requests from different clients constantly. That repetition builds an intuitive shorthand for what a brief actually means, as opposed to what it literally says. An internal team only ever sees their own work. We see the same creative problem (in different forms, across different companies) hundreds of times. That makes us significantly faster and more accurate at reading intent rather than instruction.
Shorthand briefing. Because we carry that pattern knowledge, clients don’t need to over-specify. An exhaustive brief is often a symptom of a team trying to compensate for the fact that the people executing the work don’t have enough context. We usually do. The brief can be shorter because we already understand the shape of what’s needed.
The account manager as translator. This is the fix most internal teams don’t have, and it’s underrated. Our account managers take a proportionate amount of time to brief the designer accurately: not too little, not too much. They act as a filter between the client’s feedback and the person executing the work. The designer gets one clear, interpreted direction. Not six stakeholder opinions forwarded in a chain. This single translation layer eliminates more rework than almost anything else we do.
Single point of feedback. Internally, feedback often arrives from multiple sources simultaneously, with no mechanism for resolving conflicts between them. We consolidate. The AM receives the feedback, interprets it, filters what’s a genuine creative direction from what’s a stakeholder preference or a personal opinion, and delivers one brief. The designer is never navigating contradictions, they’re just doing the work.
Defined revision discipline. We operate with clear expectations around revision rounds: what constitutes a revision, what constitutes a new brief, and what the limit is. Internal teams almost never define this, which means rounds multiply without boundary and nobody has a framework for calling it. Knowing when a round is a revision and when a job has simply changed scope is one of the quietest operational advantages we have.
Objectivity by design. We don’t have the history. We don’t have the half-remembered conversation from three weeks ago, the stakeholder who weighed in once and then disappeared, the “we tried that in Q3” institutional memory that poisons fresh thinking. We have the brief and the work. That’s it. Fresh eyes aren’t a nice-to-have. They’re the structural default of a well-run external production partner.
Common sense as a process output. Common sense is a process output, not a personality trait. When work isn’t loaded with internal politics, prior attempts, and stakeholder anxiety, the person executing it can apply straightforward judgment. Common sense isn’t a personality trait, it’s what’s left when you remove all the noise.
The cost nobody talks about
What happened in that two-week loop isn’t unusual. It’s just usually invisible because it doesn’t show up as a line item anywhere.
It shows up as management time. Revision rounds. Senior capacity pointed at something that should have been resolved at coordinator level. In an era where responsible growth demands that every function justify its cost, that invisible spend matters more than it ever has before.
We’ve written about what creative operational friction actually costs in financial terms and the numbers are larger than most teams realise. But beyond the numbers, there’s something harder to quantify: the quiet drain on a senior person’s time and patience when a small job won’t end.
The client who handed us that job wasn’t a bad ops person. They were a good ops person caught in a process that wasn’t designed to let them finish. The fixes above aren’t complicated. They’re just not in place internally, and until they are, the same jobs will keep going backwards and forwards.
One metric worth owning
We track revision rounds closely. This is not because fewer is always better, but because revision count is one of the clearest diagnostic signals in creative operations. High rounds almost never mean the work was wrong. They mean the brief lacked clarity, the decision structure was unclear, or the team had accumulated too much history with the problem to see it straight. Our rework rate runs below 4%. Industry average is 15-20%. The gap is structural, not talent.
That job took six rounds internally. One round with us. The work didn’t change dramatically. The conditions around it did.