The design stage is the cheapest point in a project to change your mind. Moving a button in a design file takes minutes; moving it after development can take days. Good feedback at this stage leads to a better product, fewer revision rounds and a smoother build. This guide shows you what to look for and how to say it.
Know which stage you are reviewing
Design usually happens in steps, and each step needs a different kind of feedback.
Wireframes
Simple grey layouts that show structure: what goes on each page and in what order. Ignore colours and fonts here. Ask:
- Is everything we need on this page?
- Is the most important information near the top?
- Does the order match how customers make decisions?
- Is anything missing from the navigation?
Visual direction
A first look at colours, fonts, imagery and style, often on one or two key pages. Ask:
- Does this feel like our brand?
- Would our customers trust this?
- Is it distinct from our competitors?
High-fidelity screens
The near-final design of every page, on desktop and mobile. Now details matter: wording, spacing, images, states such as errors and empty lists.
Clickable prototype
Linked screens you can tap through like a real site. Use it to test journeys: can you complete a booking, find a price or send an enquiry without help?
Principles of useful feedback
Focus on goals, not personal taste
"I do not like blue" is hard to act on. "Our customers are mostly doctors, and this feels too playful for them" gives the designer a goal to design towards.
Describe the problem, not the solution
"Make the button bigger" may not fix the real issue. "I did not notice how to book until I scrolled down" lets the designer choose the best fix, which might be position, wording or contrast rather than size.
Be specific
Point to the page, section and element. Screenshots with notes are far clearer than long messages.
Consolidate your team's feedback
If several people review, collect their comments into one list and resolve contradictions before sending. Conflicting notes from different people lead to wasted rounds.
Prioritise
Mark each point as must fix, should fix or suggestion. It helps the designer focus on what matters within the agreed revision rounds.
Review on the right device
If most of your customers use phones, review the mobile design on a phone, not just on a large monitor.
Use real content
Placeholder text hides problems. A heading that fits in the design might wrap to three lines with your real wording. Provide real text and images as early as you can.
Feedback that works, and feedback that does not
- Instead of "It feels off", try "The homepage feels crowded; I am not sure where to look first."
- Instead of "Make it pop", try "The call to action does not stand out from the other buttons."
- Instead of "Change the font", try "The body text is hard to read on my phone."
- Instead of "Copy what our competitor did", try "I like how their pricing page compares plans side by side; could ours do that?"
- Instead of "Looks good" when unsure, try "I have not checked the mobile pages yet; I will send notes by Thursday."
A review checklist
Message and structure
- Does the first screen say clearly what we do and for whom?
- Is there one obvious main action on each page?
- Can visitors find prices, contact details and key information quickly?
Content
- Is all the wording accurate, including prices, phone numbers and addresses?
- Are headings clear and short?
- Are images real and relevant to our business?
Brand and consistency
- Are the logo, colours and fonts used consistently?
- Do similar elements, such as buttons and cards, look and behave the same everywhere?
Mobile
- Is text readable without zooming?
- Are buttons easy to tap with a thumb?
- Is the menu easy to open and use?
Forms and states
- Are forms as short as possible?
- Are there designs for errors, success messages and empty states?
Accessibility
- Is there enough contrast between text and background?
- Is information shown by more than colour alone?
Trust
- Are reviews, guarantees, policies and secure payment signals visible where decisions happen?
Managing revision rounds
Most design plans include a set number of revision rounds. DIGITECHIE's UI/UX Basic plan includes two, and Growth and Enterprise include unlimited rounds. To get the most from each:
- Send all feedback for a round together, not in pieces over several days.
- Wait for the revised version before adding new requests.
- Keep new feature ideas separate from design feedback. They may affect scope and are best discussed on their own.
What approval means
Approving the final screens tells the development team to build exactly what is shown. Changes after this point are still possible, but they cost more time than changes in the design file. Before you approve, click through the prototype once more on a phone, check every price and contact detail, and make sure the people who need to agree have seen it.
Next steps
Design is one stage of our seven-step process. If you are preparing for a project, our guide on writing a project brief helps you set the goals that your design feedback will be measured against.