Design feedback becomes difficult when a review moves straight from seeing the work to suggesting changes. One person wants the logo bigger. Another wants a different color. A third says it should feel more premium. The agency receives instructions, but not the problem those instructions are meant to solve.
The framework below is a practical recommendation for applying the cited guidance to a brand project, not a reported client case study or a promise of results.
Useful feedback connects an observation to the project's objective. Personal reactions still matter, but they become more actionable when the team explains what triggered them and what customer-facing outcome is at stake.
Return to the agreed job
Before a review, restate what the work needs to accomplish. A packaging project might need clearer variant recognition. A homepage might need to explain an unfamiliar category. A launch asset might need to make a new size obvious without suggesting the original has been replaced.
These objectives provide a basis for evaluating the design. They also stop the review from becoming a new strategy meeting unless new evidence genuinely requires one. If the objective has changed, acknowledge that change directly rather than disguising it as a small visual revision.
Use observation, consequence, and question
A practical feedback structure has three parts. First, describe what you notice. Second, explain why it matters. Third, ask how the design could address it. This leaves room for the agency to propose a solution you may not have considered.
For example: “The variant name is the smallest text on the front. Customers need to distinguish these two products quickly. Could we explore a clearer hierarchy?” This is more informative than “make everything bigger,” which may produce a crowded package without resolving the priority.
Base the review on agreed objectives
Nielsen Norman Group defines critique around whether design meets its objectives. Its guidance emphasizes a clear discussion scope, shared understanding of the problem, and conversation rather than commands. It also recommends sharing work and setting expectations before the discussion. Nielsen Norman Group: Design Critiques.
Our recommendation: put the agreed objective at the top of the review document. Ask participants to identify what they observed and why it affects that objective before proposing a fix. Keep factual corrections separate from preferences and unresolved strategic decisions. Where comments conflict, record the disagreement and identify who will decide rather than forwarding both instructions without context. Give the agency enough room to propose alternative ways to address the concern. At the next review, return to the agreed issue and assess whether it has been resolved. This recommended process keeps revisions connected to the brief while allowing the designer to use judgment about the best visual solution.
Separate three kinds of comments
- Corrections: inaccurate names, missing content, or conflicts with approved requirements.
- Objective-based concerns: design choices that may interfere with the intended task.
- Preferences: personal reactions that are worth discussing but are not yet linked to a requirement.
Labeling comments does not dismiss taste. It simply prevents a preference from being presented as an established customer fact. If you believe a choice will confuse buyers, explain the reasoning and consider a focused review with people unfamiliar with the product.
Consolidate feedback before sending it
Choose one person to reconcile stakeholder comments into a coherent response. Preserve meaningful disagreements, but do not send contradictory directions as if they were a single instruction. Note where a decision is needed and who will make it.
Anchor comments to the specific version, page, or concept. Give an overall assessment before listing details. If one direction best meets the brief, say so; otherwise the agency may spend time revising a concept the team has already ruled out.
Close the review with a decision
Summarize what is approved, what needs revision, and what remains unresolved. Distinguish essential changes from optional exploration. Agree on the evidence needed to settle the open questions, such as a side-by-side range view or a mobile page mockup.
At the next review, compare the work with those agreed decisions rather than restarting from personal first impressions. A clear review history helps the team improve the design without losing the reasoning behind it.
If you are preparing a coordinated identity, packaging, or website project, explore Benjamin Branding's design services and bring a brief centered on the decisions your customers need to make.
Related reading: How to Evaluate a Brand Moodboard Against Your Creative Brief.