Indexwriting
Writing indexNote / Nov 22, 2025

Field note / logo design / process / branding

What Clients Don't Understand About Logo Revisions

How to manage logo revision rounds professionally and why unlimited revisions is a trap for everyone.

Published
Nov 22, 2025
Length
3 min read / 587 words
Topics
logo design, process, branding

The Revision Spiral

Every designer knows the revision spiral. You present a concept. The client has feedback. You revise. They have more feedback. You revise again. By round five you're making changes that contradict changes you made in round two, the design has lost all coherence, and everyone is frustrated.

The revision spiral isn't a client problem. It's a process problem. And the process is the designer's responsibility.

Why Unlimited Revisions Hurts Everyone

Offering unlimited revisions seems generous. It communicates confidence and customer service. In practice, it removes the incentive for clients to make clear decisions. If there's always another round available, there's never urgency to commit.

Unlimited revisions also devalues the design work. When clients know they can request any change indefinitely, they treat the design as infinitely malleable — a canvas for their real-time preferences rather than a professional recommendation based on expertise.

I use a structured revision process with clearly defined rounds. Typically two concept rounds (where we explore directions) and two refinement rounds (where we develop the chosen direction). This structure creates clarity about what each round is for and when decisions need to be made.

Distinguishing Feedback From Preference

Client feedback falls into two categories: legitimate concerns and personal preferences. Legitimate concerns include unclear hierarchy, reproduction problems, legal issues, factual errors, and functional failures. Personal preferences include "I don't know why, I just don't love it" or "my wife doesn't like the blue."

I take legitimate concerns seriously and address them directly. I engage with personal preferences differently — by asking what specific functional or strategic problem the preference is trying to solve. Sometimes a preference points to a real design issue that the client can't quite articulate. More often it's a taste difference that has no strategic basis.

My job is to explain why my recommendations serve the brief, not to agree with everything the client says. If the client's preference contradicts the strategic direction we agreed on in the brief, I say so respectfully and clearly.

Presenting to Decision Makers

Many revision spirals happen because the person reviewing the design isn't the person who has to approve it. I present to decision makers directly whenever possible. When I can't, I ask the day-to-day contact to share the presentation with decision makers before the feedback meeting and to consolidate all feedback into a single, unified response.

Consolidated feedback is cleaner, more actionable, and represents actual organizational consensus. Fragmented feedback from multiple reviewers who haven't aligned is impossible to act on coherently.

Documenting Approved Directions

After each approval checkpoint, I document what was approved in writing and confirm it with the client. This creates a record that protects both of us. If someone wants to revisit an approved decision in a later round, I can point to the documented approval and reopen the discussion explicitly rather than absorbing the change silently.

This documentation habit has saved me dozens of hours and several client relationships.

When to Stop Revising

There comes a point when further revision won't improve the work — it will only change it. When I reach that point, I say so. I explain that the current version addresses all the brief's requirements, solves the stated problems, and is the strongest version of this direction.

Clients respect this clarity. They hired a professional for a reason. Acting like one — including knowing when to stop — is what they're paying for.