How many revisions are enough: iteration and boundaries in the contract

Iteration, the continuous cycle of improvement, is how design actually works. No product is right the first time. No idea is complete before it passes through feedback. But there is a paradox here that leaves many brand projects worse off than where they started: people mistake "more revisions" for "higher quality," when in reality the opposite is true.

Iteration is essential, not a mistake

In The Design of Everyday Things, Don Norman describes design as a process of parallel discovery. You do not know what you really need until you see something that is not it. This is not a weakness of the method. It is how the human brain processes abstract problems.

In brand design the problem is even more complex, because the input is strategy, not a technical drawing. You cannot specify "a feeling of trust" or "a premium position" as a measurable parameter like the diameter of a bolt. That is why the feedback round is the mechanism that translates strategic language into visual form.

In The Brand Gap, Marty Neumeier writes that a brand is what customers feel, not what the business owner decides. That points to an uncomfortable reality: even with a perfect brief, a validation step is still needed. There must still be iteration.

What you design is never the final thing you create. Design is the process of narrowing the gap between intention and outcome.

Don Norman, The Design of Everyday Things

But “unlimited revisions” ruin projects

The issue is not the number of revisions. The issue is revising without criteria.

When a design project has no clear boundary for feedback, this is usually what happens: in round one, the client changes the color because it "feels a bit dark." In round two, new requests appear because the sales director just saw a competitor's logo. In round three, the whole idea is overturned because "my wife thinks it doesn't look upscale enough." Each round of changes comes from a new emotional source, from someone new being asked for an opinion, not from the criteria in the brief. After ten rounds, the result is the average of ten different impressions, not ten steps toward something better.

This is what the design industry calls “design by committee.” Visual decisions get softened again and again until no one objects, but no one is truly convinced either.

The figure above is not about iteration within a project. It is about what happens after the project ends. But the deeper cause often starts here: when there is no boundary during the design process, what gets delivered is a patched-together system. It lacks a strong enough rationale for people in the organization to follow later.

The boundaries in the contract protect whom

A common question from clients is: is the limit on the number of revisions to protect the studio or to protect me? The straightforward answer is: to protect both, but in different ways.

For clients, a feedback boundary creates useful pressure: it requires you to consolidate internal opinions before sending feedback, rather than sending individual comments from different people on different days. It requires feedback to stay anchored to the original criteria rather than shift with the mood of the morning. The result is feedback rounds with more substance. Decisions move faster. The final product is more internally consistent.

For studios, boundaries protect creative energy. A designer cannot maintain the quality of thought in the fifteenth round as they do in the second. This is not a matter of motivation; it is a real cognitive limit.

Distinguishing between on-point feedback and off-topic feedback

Not every revision request is equally valuable. There is a simple way to tell them apart: feedback anchored to criteria in the brief is feedback heading in the right direction. Feedback that comes from personal taste not present in the brief is feedback that needs to be questioned.

• On-target feedback: “This logo is not legible when scaled down to 16px, while the brief says it must be used on a mobile app.”
• On-target feedback: “This color cannot be printed on kraft material, while the packaging is the main touchpoint.”
• Off-target feedback: “I feel it lacks a bit of energy, but I don't know how to describe it.”
• Off-target feedback: “An acquaintance who works in marketing thinks you should add blue.”

A good contract does not just state the number of revision rounds. It also describes which kinds of feedback fall within scope. And it spells out how to handle feedback outside that scope: charge extra, or give a recommendation and record the professional disagreement.

The contract terms need to be clearly stated

Here are the things that should be defined before starting any branding design project:

• The number of feedback rounds included in the fee, and each round is counted from when to when.
• Who is authorized to provide official feedback. Not everyone in the company needs to be a point of contact.
• Feedback deadlines for each round. Feedback sent after two weeks lacks the same context as feedback sent within three days.
• A definition of “in-scope feedback” versus a “scope change request,” which is what incurs additional fees.
• A mechanism for resolving disagreement on direction: who makes the final decision, and based on which criteria.

The loop ends when the criteria are met

The question “how many revisions are enough” is actually the wrong question. The right question is: which criteria show that the design has met its goal?

When the brief is well written, that question can be answered. Is the logo legible at 16px? Does the color print correctly on the intended material? Is the visual language consistent with the defined competitive position? If yes, the project is done, whether it took two rounds or four.

Without criteria, a project never truly ends. It only stops because both sides are exhausted, or because a deadline forces it to. What gets delivered then is the result of fatigue, not yet a brand.