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

Iteration, or continuous improvement loops, is the true mechanism of design. No product is right on the first try, and no concept is complete before undergoing feedback. However, there is a paradox that causes many branding projects to end worse than they began: people confuse "more revisions" with "higher quality," when in reality, it is the opposite.

Iteration is essential, not a mistake

Don Norman in his book The Design of Everyday Things describes design as a parallel exploration process: you do not know what you really need until you see something that is not it. This is not a weakness of the method. This is how the human brain processes abstract problems.

In brand design, the issue is even more complex because the input is strategy, not technical drawings. You cannot specify "a sense of trust" or "a premium position" as measurable parameters like bolt diameter. Therefore, feedback rounds are not a sign of a flawed process. They are the mechanism for transforming strategic language into visual form.

Marty Neumeier in The Brand Gap writes that a brand is the gut feeling of the customer, not the decision of the business owner. This means facing an uncomfortable reality: even with a perfect brief, there still needs to be a validation step. Iteration is still necessary."

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 fixes" ruin projects

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

When a design project lacks clear boundaries for feedback, what often happens is this: in the first round, the client adjusts the color because "it feels a bit dark." In the second round, additional requests come in because the sales director just saw a competitor's logo. In the third round, the entire concept is overturned because "my wife thinks it doesn't look premium enough." Each round of revisions does not stem from the criteria in the brief but from a new emotional source, from someone newly consulted. The result after ten revisions is not ten times better. It is an average of ten different perceptions.

This is what the design industry refers to as "design by committee": visual decisions are continuously softened until no one objects, but no one is truly convinced either.

The above figure does not refer to iteration within the project. It speaks to what happens after the project ends. But the deeper cause often stems from here: when there are no boundaries in the design process, the deliverable is a patchwork system, lacking a solid enough rationale for those within 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, feedback boundaries create useful pressure: they force you to consolidate internal opinions before sending feedback, rather than sending individual comments from each person day by day. They compel feedback to adhere to the original criteria instead of changing with the morning mood. The result is that feedback rounds are of higher quality, decisions are made faster, and the final product has greater internal consistency.

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 all revision requests hold equal value. There is a simple way to distinguish: feedback that is anchored to the criteria in the brief is on the right track. Feedback that stems from personal preferences not included in the brief is feedback that needs to be questioned.

• Constructive feedback: "This logo is not legible when scaled down to 16px, while the brief states it must be used on the mobile app."
• Constructive feedback: "This color cannot be printed on kraft material, while packaging is the main touchpoint."
• Off-topic feedback: "I feel it's a bit lacking in energy, but I'm not sure how to express it."
• Off-topic feedback: "My friend in marketing thinks we should add some green."

A good contract does not just state the number of revision rounds. It describes what type of feedback is within scope, and what the mechanism is for handling feedback that falls outside that scope: additional charges, or providing recommendations and noting professional disagreements.

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.
• Defining "feedback within scope" versus "scope change requests" incurs additional charges.
• The mechanism for resolving disagreements: who has the deciding voice and based on what criteria.

The loop ends when criteria are met

The question "how many revisions are enough" is actually the wrong question. The right question is: what criteria indicate that the design has met its goals?

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

Without criteria, a project never truly ends. It only stops because both parties are exhausted, or due to a deadline that forces a halt. What is delivered at that point is not a brand; it is the result of fatigue.