How to give design feedback that leads to a clear revision
Give designers specific, prioritised feedback that connects changes to the campaign objective and avoids conflicting revision instructions.
Begin with the purpose of the review
Design feedback is most useful when everyone understands what is being reviewed. A first concept invites discussion about the overall direction, while a final proof may need precise checks of copy, spacing and output. Tell reviewers which stage they are seeing. Otherwise, one person may debate the central idea while another assumes the idea is settled and focuses only on small details.
Restate the campaign objective before collecting opinions. The question is not simply whether each reviewer likes the artwork. It is whether the design communicates the intended message to the intended audience in the intended setting. That shared frame makes it easier to distinguish a useful concern from a preference that does not affect the campaign's purpose.
Give the designer the relevant context when asking for a review. Include the brief, the current version, the intended placement and any known limitations. If the copy is provisional or an image is a placeholder, identify it explicitly. Reviewers can then spend their attention on decisions that are ready to be made rather than correcting temporary material that will be replaced anyway.
Describe what you see before prescribing a solution
Start with an observable issue. “The registration date is smaller than the supporting paragraph” is more precise than “the layout has no impact.” Then explain why it matters: the deadline is the information the audience needs to act. This gives the designer a problem to solve and a reason for solving it, while leaving room for their expertise in choosing the best visual response.
A proposed solution can still be helpful, especially when the requirement is factual. “Replace the date with 18 October” is a clear correction. For design problems, avoid treating the first suggested fix as the only possible answer unless there is a real constraint. Increasing the headline, reducing competing text or changing the composition may all address the same hierarchy problem in different ways.
Ask a question when you are unsure. For example, ask how a layout will read on a phone instead of assuming that the screen preview reflects the final size. A designer may have context that changes the discussion. Productive feedback allows that explanation while still requiring the team to resolve a genuine communication issue.
Use a simple comment structure
A practical feedback comment has three parts: the location, the concern and the desired outcome. Identify the headline, image, footer or variant. Describe the problem in plain language. Then explain what a successful revision should accomplish. This structure works in a review tool, a campaign comment or a short document without requiring a specialised vocabulary.
For example: “On the portrait social image, the call to action sits over a busy part of the photograph. It is difficult to read at phone size. Please make the registration instruction clearly legible while preserving the main image.” The designer can act on this without guessing which asset or text the reviewer means.
Keep one issue per comment when possible. A single message that combines a date correction, a colour preference and a request for another format is hard to track. Separate comments allow the team to assign responsibility, resolve conflicts and confirm completion. They also make it easier to see whether a new request changes the original scope.
- Point to the exact asset and version.
- Identify the text or area involved.
- Explain the communication problem.
- State the required outcome or factual correction.
- Mark whether it blocks approval.
- Link the source when a claim or detail needs verification.
Separate requirements, questions and preferences
Not all comments carry the same weight. A wrong event time requires correction. A question about whether the image is licensed requires an answer from the appropriate owner. A preference for a different illustration style may be optional if the current approach meets the brief. Label these differences so the designer can plan the revision intelligently.
Use priority labels sparingly and consistently. If every comment is urgent, the label provides no information. Explain which issues must be resolved before the next review and which can be discussed if time allows. The campaign owner should make these tradeoffs rather than leaving the designer to infer them from the seniority or tone of individual reviewers.
Be careful with apparently small requests that have broad consequences. Changing a headline may affect translation, layout and every size adaptation. Adding a new logo can alter the visual hierarchy and require another brand check. A useful feedback process considers the effect of a change across the campaign, not just how easy it sounds in a comment.
Review in the order that prevents wasted effort
Address the largest decisions first: message, audience fit, overall concept and hierarchy. Once those are settled, examine details such as spacing, image crop and alignment. Polishing a layout before the team agrees on its central message creates work that may be discarded. A staged review helps the designer focus on the decisions that are most expensive to change later.
For a first concept, limit the number of detailed production comments unless they affect feasibility. For a final proof, avoid reopening settled creative preferences without explaining why the brief has changed or a material problem has been discovered. This does not mean ignoring errors. It means recognising that different review stages have different purposes and that late changes have consequences.
When an important new fact appears, update the brief as well as the comment thread. A revised audience or offer is not merely a visual adjustment. Recording the change helps later reviewers understand why the work moved in a new direction and prevents the same disagreement from resurfacing in the next round.
Consolidate feedback from several people
Multiple reviewers can reveal problems one person misses, but their comments need coordination. Choose one person to collect responses, identify contradictions and issue the agreed revision list. The designer should not receive separate mandatory instructions to both increase and reduce the same element. Resolve that conflict with the campaign objective in view.
Keep the original contributions accessible while recording the final decision. If a suggestion is not adopted, a short explanation helps the reviewer understand the tradeoff. For example, a team may move background information to a landing page because the poster's primary job is to communicate a date and registration action. The decision can be clear without dismissing the original concern.
Set a feedback deadline and communicate when consolidation is complete. Late comments can be handled according to their importance, but the team should avoid silently adding optional changes after the designer has started the revision. A stable revision list protects concentration and makes the next review more meaningful because everyone knows what was requested.
Avoid subjective shorthand that hides the problem
Phrases such as “make it pop,” “more premium” or “less corporate” may express a real reaction, but they need translation into observable qualities. Ask what the audience should notice or feel, and which part of the current work prevents that. Is the issue colour contrast, density, photography, language, hierarchy or a mismatch with the organisation's established identity?
References can help if the reason is explicit. Point to the generous spacing in one example or the clear information hierarchy in another. Do not send a collection of unrelated images and expect the designer to infer which features matter. A reference should clarify the intended outcome without becoming a demand to reproduce another organisation's work.
Avoid personal language about the designer. Discuss the work and its effect on the campaign. “The supporting copy is competing with the main action” creates a solvable problem. A judgement about someone's taste or ability does not. Respectful specificity makes it easier for both sides to challenge assumptions and improve the result.
Check the revision against the agreed list
When the revised artwork arrives, compare it with the consolidated feedback. Confirm that factual corrections are accurate, required changes are addressed and no unintended issues were introduced. Do not assume that a marked comment means the resulting file is correct. Open the actual version and inspect the relevant areas at a useful size.
If a designer chose a different solution from the one suggested, evaluate whether it achieves the agreed outcome. The purpose of feedback is to improve the communication, not to prove that the reviewer can direct every pixel. If the issue remains unresolved, explain the remaining problem specifically rather than repeating the original instruction with more emphasis.
Record which comments are resolved and which still need a decision. If new feedback concerns a different issue, label it as a new request rather than implying that the earlier revision failed to address something it was never asked to change. This creates a fair and understandable history of the work.
Example: simplifying a crowded event graphic
Imagine a first draft containing an event title, five speaker biographies, a venue description and a registration instruction. Reviewers say it feels crowded. A useful consolidated response identifies the primary audience action, asks the designer to prioritise the title, date and registration, and moves full biographies to the event page. It also confirms which speaker names must remain on the graphic.
The designer can then propose a cleaner layout with a clear relationship to the campaign objective. In the next review, the team checks whether the main information is readable and whether the landing page contains the removed detail. The improvement comes from clarifying the message and destination, not from repeatedly requesting a more attractive arrangement of the same excessive content.
Frequently asked questions
Should I tell the designer exactly how to fix a problem?
Give exact instructions for factual corrections and genuine constraints. For visual problems, explain the issue and desired outcome, then allow the designer to propose a solution. If you suggest an approach, make clear whether it is a requirement or an idea to consider. This preserves useful expertise on both sides.
How many revision rounds should a campaign have?
There is no universal number that fits every campaign. Agree a practical review plan based on the scope, dependencies and deadline. More useful than counting rounds is preventing avoidable rounds caused by missing context, conflicting comments or late changes to the brief. Review the causes of repeated revisions after the campaign closes.
Where should feedback be recorded?
Keep it close to the campaign, artwork version and decision history. Campaign Bay brings briefs, design partners, artwork reviews and final deliveries into a shared workspace. Whatever process your team uses, avoid splitting the authoritative revision list across private messages and unrelated attachments that the designer cannot reliably reconcile.