When round two undoes round one, don't guess which note wins and don't quietly build a hybrid. Restate both notes back to the client in a short message, ask which one stands, and stop there. That single question reads as competence, not pushback, and it is faster than reverse-engineering what the client meant. Guessing is the costly move: it produces a third version nobody asked for, and a client who now has to explain themselves twice.
Why Contradictory Feedback Happens Even With One Contact
It is tempting to read a contradiction as a sign the client does not know what they want. Usually something more ordinary is going on. The person giving round two feedback may be reacting to the file in a different context than round one, on a phone instead of a monitor, at the end of a long day instead of the start of one, and their read on the same design genuinely shifts. Sometimes round one was a first reaction and round two is a settled one, and the settled one is the real answer, they just never said so.
It also happens because a client's own thinking about the project moves as they see more of it. A brief describes an intention; a finished concept is the first time that intention becomes concrete enough to react to honestly. A note that contradicts an earlier one is often the client learning what they actually want by seeing what they do not want. None of this means the client is disorganized. It means feedback is a process, not a single transmission, and a solo designer working with one contact still has to manage that process without a producer catching the drift.
The Trap: Guessing and Building a Silent Hybrid
The instinct that causes the most damage is trying to satisfy both notes at once without saying anything. It feels efficient in the moment: split the difference, keep everyone happy, avoid an awkward conversation. It rarely works, because a hybrid built to please two contradictory instructions usually pleases neither. The client opens the file, cannot articulate why it still feels off, and the round restarts anyway, except now a full round of billable time has gone into a version built on a guess.
The quieter cost is that guessing hides the contradiction instead of resolving it. If the client never learns that round one and round two disagreed, they have no reason to think more carefully before round three, and the same pattern repeats. Naming it once is what actually breaks the cycle.
The Script for Surfacing It Without Sounding Difficult
The move is short and it works because it is neutral. State both notes as facts, not as an accusation, and ask a single closed question.
"Before I make changes, I want to check something. Round one asked for a bolder, more energetic direction. Round two asks to pull the energy back and read calmer. Which one should I build toward?"
That is the whole script. It does not apologize for asking, and it does not speculate about why the client's mind changed, because that part is not the designer's business to guess at. It restates, then asks, then stops. Most clients answer within a day, because the question is genuinely easy to answer once it is put plainly in front of them. Framing the request this way, one specific thing, one clear criterion, one decision, is the same shape covered in more depth in how to ask clients for design feedback, and it applies just as well to resolving a conflict as it does to gathering a first round.
What "Both" as an Answer Usually Means
Sometimes the client answers "both," meaning they want the boldness of round one and the calm of round two in the same file. That answer is not indecision. It usually means the brief itself never settled on a single goal, and the client has been reacting to drafts because there was no fixed target to react against in the first place. This is the same underlying pattern behind a note like "make it pop": the client's language for what they want is vague because the goal itself was never pinned down, which is why translating that specific phrase gets its own treatment in decoding "make it pop" and other vague client feedback. Two contradictory pieces of feedback rarely coexist honestly; when a client insists they do, the real fix is a short conversation about which goal the project is actually optimizing for, not a cleverer layout.
When the Contradiction Is Scope Creep in Disguise
Not every contradiction is really a contradiction. Sometimes round two is not disagreeing with round one at all, it is asking for a different project wearing the same round number. A request to "make it pop more" that turns into "actually let's try a completely different layout concept" has stopped being a revision of the current direction and started being new creative work. The tell is whether the second note can be satisfied by adjusting what already exists, or whether it requires starting a new concept from a blank page. If it is the second, treat it as its own conversation about scope, not as round two of the current round, before any hours go into it. The signals that separate an ordinary feedback round from scope creep wearing a feedback costume are worth learning on their own, since a contradictory round is one of the more common places they show up.
Logging the Resolution So Round 3 Doesn't Restart the Argument
Once the client answers which note stands, write one line recording it, dated, in whatever system holds the project's notes. "Aug 6: client confirmed calm direction over bold, per round 2 note; round 1 direction dropped." It takes under a minute and it is the only thing standing between you and the same argument resurfacing at round three, when memory has quietly drifted and someone asks why the bold version was dropped. A log entry ends that conversation in one line instead of reopening a decision that was already made. This habit, closing every stage in writing rather than trusting memory, is the same discipline that runs through the whole solo design project process, not a one-off trick for this situation.
FAQ
What should I do if a client's feedback contradicts an earlier round?
Restate both notes in a short message and ask which one stands. Do not guess or quietly build a version that tries to satisfy both, since that usually satisfies neither and restarts the round anyway.
Is it unprofessional to point out that a client's feedback contradicts itself?
No. Naming it plainly, without accusation, reads as attentive rather than difficult. What damages the relationship is guessing wrong and producing a version that misses what the client actually meant.
What if the client says they want both directions at once?
That usually means the underlying goal was never settled. It is worth a short conversation about which goal the project is optimizing for, rather than trying to merge two conflicting directions into one file.
How do I tell a contradiction apart from scope creep?
Ask whether the new note can be satisfied by adjusting the current concept or whether it requires starting a new one. If it is the latter, it is new work, not a revision of the existing round.
What if the same contradiction comes from several different people, not one contact?
That is a related but different problem, since it involves several voices rather than one contact changing their mind. The approach for that case, including how to find one decision-maker, is covered in feedback from too many stakeholders.