Start with the decision the brief was meant to support
Conflicting feedback can make a project feel like a contest between opinions. A client asks for a more playful identity, while the brief calls for a calm, credible tone. A teammate wants to add information to a campaign graphic, while the brief prioritises a quick read. Before changing the work, return to the decision the brief was designed to guide: what must this piece help its audience understand, feel or do?
Pull out three kinds of information: the intended audience, the project’s main objective and any firm constraints. Separate these from preferences about style or execution. “Make it easy for first-time visitors to find the workshop schedule” is an objective; “use a blue background” may be a proposed solution. A constraint, such as a required format or approved wording, needs different treatment from either one.
If the brief is vague, write a short working interpretation rather than pretending it settles the debate. For example: “This page should help someone unfamiliar with the programme understand its purpose and find the next step.” Share that interpretation with the people making the decision. A usable brief is a reference point for discussion, not a reason to dismiss new information.
Translate comments into concerns
Feedback often arrives as an instruction: “Make the headline bigger,” “Add another image,” or “Use a friendlier colour.” Record the instruction, then ask what problem it is trying to solve. A request for a bigger headline might mean the message is hard to notice, the hierarchy feels unclear or the reviewer is unsure which idea matters most. Those concerns may be valid even when the suggested change is not the best answer.
Sort each comment into one of three groups. Brief-aligned feedback identifies a problem that affects the agreed goal. New-context feedback introduces information the brief may have missed, such as an additional audience or a practical use case. Preference feedback expresses a taste without an obvious link to the project’s purpose. These labels are prompts for conversation, not verdicts on the person giving feedback.
When a comment seems to contradict the brief, ask a neutral question: “What would this change help the audience do?” or “Where do you expect the current version to fall short?” This keeps the discussion focused on outcomes. It also gives the reviewer room to explain knowledge you may not have had when the work began.
Compare the proposed change with the problem it solves
For each substantial revision, write down the concern, the proposed change and its likely effect on the brief. Consider what it would improve, what it might weaken and whether a smaller change could address the concern. You do not need a scoring system; a few plain sentences can make the trade-off visible.
Imagine a poster for an introductory creative workshop. The brief asks for an approachable invitation that someone can understand at a glance. A reviewer wants to add a paragraph describing every activity. The concern may be reasonable: people need to know what they will make. But the proposed solution could make the poster harder to scan. A shorter line naming two representative activities, paired with a clear place to find the full programme, may answer the concern without losing the poster’s purpose.
Try the smallest meaningful revision first when the issue is clear but the solution is uncertain. Changing a label, adjusting hierarchy or replacing an ambiguous image can reveal whether the concern has been addressed. If feedback points to a genuinely new objective, pause before polishing: the team may need to update the brief and agree on new priorities.
Make the decision visible, then check the result
A revision is easier to discuss when you explain it in terms of the shared goal. Try a brief response with three parts: acknowledge the concern, name the decision and explain the trade-off. For example: “The activities need to be clearer. I’ve added two examples near the headline rather than a full paragraph so the poster remains readable at a glance.” This shows that feedback was considered without implying that every suggested solution must be used.
Keep a simple decision record for comments that affect scope or direction: what was raised, what changed and what still needs agreement. This is especially useful when several people review work at different stages. It helps prevent an earlier decision from being reopened merely because its reasoning was not visible.
Finally, look at the revised piece as its intended audience might. Can someone identify the main message? Is the next step clear? Does the work still meet its constraints? If possible, ask a colleague who has not followed the discussion to describe what they understand from it. The goal is not to prove one reviewer wrong. It is to make a defensible choice, test whether it works and keep the project moving toward its agreed purpose.
