Website Design Feedback: How to Get Revisions Without Chaos

A clinic was redesigning its website, and the first draft came back thin on detail. The team had comments, plenty of them, sometimes contradictory. The designer revised, more comments followed, and the project began to circle. Good designers welcome feedback, but confusion in the feedback slows everyone down and can weaken the result.

Clear design feedback is a skill, and it makes projects faster and better. Here is how to give it.

Why feedback goes wrong

Common problems include many voices giving conflicting comments, vague remarks such as make it pop, feedback on personal taste rather than patient needs and comments arriving in dribs and drabs. Each creates extra rounds. Understanding the causes helps you avoid them.

Appoint one voice

Choose one person to collect comments from the team and give the designer a single, consistent set. That person resolves conflicts before they reach the designer. One voice prevents contradictory instructions, and speeds up every round.

Design feedback should start from the goal

Remind everyone what the site is for and who it serves. Judge each comment against that. Does this change help patients find information, trust the clinic or take action? If not, it may be a matter of taste. Goals keep feedback focused on outcomes.

Be specific

Replace vague comments with clear ones. Instead of it feels cold, say the photographs feel clinical, and suggest warmer, real images. Instead of make it bigger, say the booking button is hard to see on a phone. Specific comments are easier to act on.

Give reasons

Explain why you want a change. A reason helps the designer find the best solution, which may differ from your suggestion. Without a reason, they may follow your words and miss your intent. Reasons turn instructions into shared problem-solving.

Separate must-haves from preferences

Mark comments as essential, important or nice to have. Errors, accuracy problems and patient needs come first. Taste comes last. This helps the designer prioritise, and keeps rounds short. Not everything deserves equal weight.

Give feedback in one round

Collect all comments, and send them together, with a deadline. Sending piecemeal comments creates rework and confusion. A single, organised round is faster and produces better results than five small ones.

Review on real devices

Look at the design on a phone, a tablet and a computer, as patients would. Many problems only appear on small screens. Include screenshots in your feedback where helpful. Reviewing properly avoids surprises after the build.

Keep the content separate from the design

Do not judge the design using placeholder text. Where content is missing, note it separately. Confusing content problems with design problems leads to unnecessary redesigns. Review content and design in the right order, and have real words as early as possible.

Let the designer explain

Ask the designer why they made a choice. There may be a good reason based on usability or accessibility. Listen before you change. A conversation often finds a better answer than either side’s first idea.

Set a limit on rounds

Agree, at the start, how many rounds of feedback are included, and what happens if more are needed. A clear limit encourages careful, organised comments, and prevents projects drifting forever. Reserve later rounds for real problems, not preferences.

Test with real people

Show the design to a few patients or staff who were not involved, and watch how they use it. Fresh eyes reveal what the team no longer sees. Testing gives objective evidence to settle debates, and reassures everyone that the site works.

Prepare before you look

Before opening a design, remind yourself of the goal, the audience and the main pages. Read your notes, and decide what you will check. Going in with a plan produces more useful comments than a first impression alone.

Thank the designer and keep it constructive

Designers respond well to respect and clarity. Say what works as well as what does not. A collaborative tone gets better ideas and faster progress than a list of complaints, and builds the relationship you need for the rest of the project.

Keep a decisions log

Record what was decided at each stage, and why. If a debate returns later, you can point to the record. A short log prevents repeated arguments and helps new team members understand why the design looks as it does.

Give the designer the material they need

Designers work best with real text, real photographs, brand guidance and a clear list of pages. Supply them early. Missing content is the main reason design rounds multiply, because the designer has to guess. Good materials make the first draft closer to what you want.

A quick checklist

1. Appoint one person to collect feedback.
2. Judge comments against the goal.
3. Be specific and give reasons.
4. Mark must-haves and preferences.
5. Send feedback in one round.
6. Review on real devices.

Our companion article on filling spare capacity covers what to promote once the site is live, and our guide to failed website projects explains how to keep projects on track. If you would like help, we are glad at Pulse Digital Health to talk.