Treat the conflict as information
One stakeholder wants a page to feel bold; another asks for a quieter look. A marketing lead wants more detail, while a product lead wants less. These notes can sound like competing instructions, but they often reveal different concerns about the same work. Before changing the design, ask what each person is trying to protect: clarity, brand consistency, accessibility, conversion, or ease of maintenance.
Avoid resolving a conflict by averaging the requests. A compromise can inherit the weaknesses of both ideas without meeting either goal. Instead, restate each note in neutral terms: “One concern is that the headline may not stand out; the other is that a stronger treatment could overwhelm the rest of the page.” This shows that you have heard both sides without presenting either stakeholder as an obstacle.
Separate requirements from preferences
Collect the feedback in one place and sort it before revising. Mark items that appear to be fixed requirements, such as approved wording, accessibility needs, or a defined scope. Put subjective preferences and open questions in separate groups. If two supposed requirements contradict each other, do not guess which one takes priority; ask the client team to clarify.
It helps to connect each comment to the project brief. Does it address the agreed audience and purpose? Does it introduce a new goal? A request to add more information might be essential for a particular user task, or it might reflect one reviewer’s wish to include everything. Naming that distinction makes the next conversation more useful than debating whether the page is simply “too busy.”
Find out who can make the call
Multiple reviewers do not always have equal responsibility for the final decision. Early in a project, ask your main contact how feedback will be consolidated, who can approve the work, and which stakeholders own specific requirements. If that process was never established, clarify it when the first conflict appears. A simple question works: “Who should make the final call when these two directions compete?”
Give the group a clear view of the decision it needs to make. In a shared feedback document, list the conflicting notes, the choice they affect, and the person or group expected to decide. Ask stakeholders to return one agreed direction where possible. This does not mean excluding people from discussion; it means avoiding a revision cycle in which every new comment reverses the last one.
Offer options with visible tradeoffs
Your role is not just to pass contradictions back to the client. Use your creative judgment to propose a direction and explain why it serves the project goal. For example: “I recommend keeping the shorter introduction and moving the additional detail below the main action. That preserves a clear first impression while making the information available to readers who need it.” A recommendation is easier to evaluate than an open-ended request for more opinions.
When there is no obvious answer, present two focused options rather than a collection of minor variations. Describe what each option prioritizes and what it gives up. You might also suggest testing a small piece of copy or a layout in context, if the project allows it. Be clear about whether exploring options fits the agreed scope and schedule; substantial new directions may need a separate conversation about effort and timing.
Close the loop before revising again
After a decision, summarize it in writing: the chosen direction, the reason for it, any unresolved items, and what you will change next. Keep the summary short enough that stakeholders can confirm or correct it. For example: “We’ll retain the prominent heading, reduce the color intensity, and review the revised page against the original clarity goal.” This gives everyone a shared reference when the next version arrives.
If conflicting feedback continues, pause and revisit the decision process rather than silently absorbing repeated rework. You can say that you are ready to proceed once the team confirms a single direction, and explain how another change may affect the planned revisions. Calm, specific communication protects the work and the relationship. The aim is not to win an argument about taste; it is to help the client make an informed decision that the project can follow.
