The Revision That Ate the Project

Round one comes back. It’s close. The direction is right, but something is off and everyone can feel it without being able to name it. The client sends notes. The notes are helpful and also contain two additional thoughts that weren’t in the original brief, introduced casually, at the end, as “while we have you.” The designer incorporates the notes. Round two goes out.

Round two is better. Someone shows it to a person who wasn’t in the original meeting. That person has thoughts. The thoughts are not unreasonable. They are also the thoughts of someone who missed the brief, doesn’t know what problem round one was solving, and is evaluating the work in a vacuum. Their thoughts become notes. The notes go to the designer. Round three is requested.

By round six, the original brief is a memory. The work is solving approximately four problems, two of which were introduced after round three, one of which contradicts the original positioning, and one of which is “the CEO’s wife doesn’t like orange.” There are now seven stakeholders. No one can remember what success looks like. The designer is billing overtime. The launch is three weeks late. And somehow, somehow, everyone involved is surprised this happened.

Where it starts

It starts in the brief. The revision spiral is almost always a brief problem that presents as a revision problem. When the problem isn’t defined clearly at the start, the review process becomes the place where the problem gets defined: retroactively, out loud, through reaction to work that was built on a different understanding. Every round of revision is the client and the designer discovering, together, what the project was actually supposed to be. That discovery process is legitimate. It is just very expensive to run it during execution rather than before.

The second origin point is stakeholder management. A project with one decision-maker and a clear brief is almost never a revision spiral. A project with five decision-makers, no agreed approval process, and a brief that five people interpreted five different ways: that project is a spiral before the first file is opened. The designer will produce work that is right for one interpretation and wrong for four others, and the reconciliation of those four others is paid for in rounds.

The “while we have you” problem

Creative rounds have a gravitational pull. Once the designer is making changes anyway, the temptation to add slightly adjacent requests is irresistible. “While we have you” is the phrase that transforms a targeted revision into a scope expansion. The new requests are usually reasonable on their own. The problem is that they weren’t in the brief, they haven’t been evaluated against the strategy, and they are now being weighed at the end of a revision note alongside specific, actionable feedback, which means they get incorporated without the scrutiny they would have received in the briefing process.

“While we have you, can we also try a version with a different typeface?” is one round. “While we have you, can we also explore a completely different direction?” is a new project wearing a revision’s clothes. The client often doesn’t know the difference. The designer knows the difference and may or may not say so, depending on how the engagement is scoped. The right answer is to say so, clearly, and to have a scope that makes the conversation straightforward rather than awkward.

The revision that is actually a change of mind

There is a specific type of revision that is not a revision. It is a change of mind about the brief. The work came back exactly as requested. The request was wrong. The client now knows this because they can see the work, and seeing the work has clarified something they couldn’t have known without seeing it. This happens. It is not the designer’s fault. It is also not a free round. It is a scope change that should be acknowledged as such and handled accordingly.

Mistaking a brief failure for a design failure is the single most common source of conflict in creative projects. The work is “not right,” but it’s not right because the brief was wrong, not because the execution was wrong. The honest conversation about that distinction is uncomfortable. It is also the conversation that fixes the project most efficiently. The alternative is continuing to revise the execution of a problem that has been misidentified, which produces rounds of work that feel like progress and aren’t.

How to not do this

Write the actual brief before work starts. Define who approves the work and in what order, with a cap on how many people get a vote. Agree upfront on how many revision rounds are included in the scope and what constitutes a round versus a new scope. When new requests appear mid-project, pause and ask whether they belong in this project or the next one. And when the work comes back and your first instinct is “this isn’t right,” ask yourself whether the brief was right before you decide the work wasn’t.

None of this is complicated. It is just discipline. The projects that go well are not the ones where everyone got lucky. They are the ones where someone cared enough to set the conditions for good work at the start, instead of hoping the conditions would sort themselves out during the rounds. They don’t sort themselves out. They compound.

Frequently asked questions

How many revision rounds are normal for a design project?

Most creative engagements include two to three rounds of revisions in the standard scope. Beyond that, additional rounds typically indicate either a brief problem (the problem wasn’t defined clearly enough) or a stakeholder problem (too many people with different interpretations of the brief are weighing in). More than three rounds on a single deliverable is a signal to stop and diagnose the cause rather than continuing to revise.

What is “scope creep” and how does it happen?

Scope creep is the gradual expansion of a project’s requirements beyond what was originally agreed, usually without corresponding adjustments to timeline or budget. It typically happens through “while we have you” additions during revision rounds, late-joining stakeholders who introduce new requirements, and brief changes that are treated as refinements rather than scope changes. A clear scope of work and a defined change order process prevent most scope creep.

Who is responsible when a creative project goes through too many revisions?

Usually both parties share responsibility. The client is responsible for a clear brief, consolidated feedback from a defined set of stakeholders, and flagging scope changes rather than embedding them in revision notes. The designer is responsible for communicating when feedback represents a scope change, for pushing back on briefs that are underspecified, and for making the constraints of the engagement clear before work begins.

What’s the difference between a revision and a new direction?

A revision refines or corrects the execution of the established direction. A new direction changes what the work is trying to accomplish, who it’s for, or what it communicates. The first is expected and included in most scopes. The second is a scope change that should be acknowledged as such. Treating new directions as revisions is how projects lose their shape.