Good design feedback tells your designer what needs to work better, where the problem appears, and why it matters to your customers. You do not need design vocabulary to do that. You need a clear goal and a specific observation.
If you are reviewing a logo, packaging concept or website for your small business, “I don’t love it” can be an honest starting point. The useful next step is to explain what feels wrong in a way your designer can investigate.
This guide includes examples, a simple review process and a feedback template you can copy. The business scenarios are illustrative.
Start with the brief, before you start with opinions
Open the agreed brief beside the design. Remind yourself who it is for, what it should communicate and what the customer needs to do next. If those decisions were never recorded, use our free creative brief template to establish a shared reference before requesting another round.
For a local florist, the goal might be to make weekly flower subscriptions feel easy to order. For a ceramic studio, it might be to communicate the character of handmade pieces while keeping product information easy to read. Those projects need different kinds of feedback.
Nielsen Norman Group’s guide to design critiques frames the exercise around whether a design meets its objectives. Apply that principle by asking, “What should this design help someone understand or do?”
Check what stage you are reviewing
Ask your designer what is ready for feedback. A first concept, a developed layout and a production proof each need a different review.
- Concept stage: Review the overall direction, audience fit and message. Check whether wording and images are placeholders.
- Development stage: Review the chosen direction in real formats, including the balance of text, images and calls to action.
- Final proof: Check approved wording, contact details, sizes, links, image quality and agreed deliverables. A new creative direction at this point may need a revised scope.
You can still flag a serious problem late in the process. Explain whether you have spotted an error or changed your mind about an earlier decision; your designer needs that distinction to plan the response.
Use location, observation, impact and a question
A useful feedback note can follow four parts:
- Location: Identify the page, concept, panel or element.
- Observation: Describe what you see, without guessing the designer’s intention.
- Impact: Explain the consequence for the agreed goal or audience.
- Question: Invite the designer to recommend a response.
For example: “On the mobile homepage, the workshop date sits below the large image. Someone checking availability has to scroll to find it. Could we explore a layout that makes the next date visible earlier?”
You have identified the problem without prescribing the font size, image crop and spacing. If you already have a possible fix, offer it as an option rather than presenting it as the only acceptable answer.
For help describing what draws attention first, see our guide to visual hierarchy for small business design.
Design feedback examples: turn a reaction into a useful note
| First reaction | A more useful version |
|---|---|
| “Make it pop.” | “On the market poster, the booking link blends into the background. We need readers to find it after noticing the event name. What would give it clearer emphasis?” |
| “The logo is too small.” | “On the sample shipping label, I struggle to read the business name at actual size. Could you check legibility and suggest an appropriate version?” |
| “This feels too corporate.” | “The formal stock photography feels distant from our hands-on workshops. Could we explore imagery that shows the making process?” |
| “Use this competitor’s design.” | “Their product details are easy to scan because the size and material are grouped together. Could we achieve that clarity in our own visual style?” |
| “I hate that colour.” | “This bright orange feels more energetic than the calm direction we agreed. Is there a reason for the change? I’d like to compare it with an option closer to the approved palette.” |
| “Can we add more?” | “Customers often ask whether the class suits beginners. Could we make that answer easier to find without overcrowding the layout?” |
Personal preference is allowed. If you dislike a colour but cannot identify a customer problem, say so plainly: “This is my preference rather than an issue we have tested.” That gives the designer accurate information instead of an invented business rationale.
Separate requirements, concerns and preferences
These three labels can help a small team agree what matters:
- Required correction: A factual error or a missed agreed requirement, such as an incorrect phone number or omitted approved wording.
- Concern to investigate: A possible audience or usability problem, such as unclear navigation or text that appears difficult to read.
- Preference to explore: A subjective choice, such as wanting a warmer photograph or a less decorative typeface.
A concern deserves attention without being treated as proven. “I couldn’t find the delivery information” describes your experience. “No customer will find this” claims more than you know.
If readability or navigation is involved, use our accessible design checklist to make the discussion more specific. A visual review alone cannot establish that a website is accessible.
Show what should stay
Record the successful decisions as well as the problems. This helps the next revision preserve what is working.
For example: “Keep the spacious layout and the close-up product photographs. The change we need is a clearer distinction between the starter kit and refill pack.” That is more useful than a vague compliment followed by an unrelated list of changes.
When sharing references, identify the particular feature you want to discuss. Our guide to building a swipe file without copying explains how to study a design decision while developing an original result.
Review the design in the places it will be used
A large presentation slide can conceal practical problems. Ask to see relevant applications before approving a direction: a logo on a small label, packaging printed at actual size, or a website layout on a phone.
Check against the agreed brand rules too. If you have documented logo versions, typography and colour use, bring your brand style guide into the review.
Where possible, ask a few intended customers to attempt a relevant task. For a workshop page, ask them to find the date and explain how they would book. Record what they do and where they hesitate. Avoid relying only on “Which one do you like?” A small informal check can uncover a problem, but it is not proof of how every customer will behave.
In Adobe Design’s reflections on critique, brand designers discuss considering both client and audience perspectives. Your knowledge of the business and the customer’s experience each have a role.
Send one coordinated round of feedback
Agree who collects comments and who makes the final decision. Let each reviewer record observations before discussing them together, then resolve contradictions before sending the designer a single set of priorities.
Figma describes silent and other review formats in its account of how its design team runs critiques. For a small business, a simple shared document can be enough; you do not need a formal workshop.
Name the exact file or version you reviewed. Keep comments in the agreed place rather than splitting them between email, messages and verbal instructions. If the project uses Figma, its commenting tools let you attach notes to specific locations in the design.
A design feedback template you can copy
Project and version: [Name, file link and date]
Review stage: [Concept / development / final proof]
Agreed goal: [Audience, main message and intended action]
Please keep: [Specific successful decisions]
Required corrections: [Location, error and correct information]
Main concern: [Location → observation → impact → question]
Preferences to explore: [Clearly identified personal preferences]
Questions for the designer: [Anything you need explained before deciding]
Decision owner and next step: [Who approves; what the next revision should address]
Lead with the changes that affect the project’s purpose. A wrong booking link should be easier to spot in your notes than a preference about a decorative border.
What if you dislike the whole direction?
Say so before requesting dozens of small changes. Identify whether the problem is the underlying idea, the execution or a brief that no longer reflects the business.
A useful message might be: “The layout is clear, but the playful illustration direction doesn’t fit the audience we described. Before refining it, could we revisit the concept against the brief?” Ask the designer to explain their reasoning too; the presentation may have left an important decision unexplained.
If your audience, offer or requirements have changed, acknowledge the new scope and ask about its effect on the fee and timeline.
Check the next revision against your original notes
When the updated design arrives, compare it with the agreed priorities. Confirm which issues are resolved, ask about anything still open and record decisions before moving towards approval.
You can be direct without making the review personal. Clear feedback gives the designer enough information to make a thoughtful next move, and gives you a better basis for deciding whether the work is ready.
Featured photograph: Theme Photos on Unsplash.