Website Design

How to Review a Website Design and Give Feedback That Leads to a Decision

Turn website design comments into clear decisions by identifying the visitor task, separating corrections from preferences and checking the revised concept.

Published

How to Review a Website Design and Give Feedback That Leads to a Decision

Useful website design feedback helps the team make a decision. It identifies a visitor's task, points to something in the proposed layout and explains what needs to change or be checked. Comments such as “make it more modern” leave the designer guessing about both the problem and the expected result.

This guide concerns visual and content concepts before development. The aim is to agree a direction that serves the brief, then verify the revision. A static design can show proposed wording and hierarchy; it cannot demonstrate that a finished enquiry form delivers a message or that an account's permissions work.

Agree what the design must help someone do

Begin the review with the intended visitor and one important task. A prospective customer might need to distinguish two services, compare relevant information and understand the next step. Keep that task beside the design rather than assessing each element as an isolated decoration.

Use the agreed website project brief to identify essential information, constraints and decisions already made. Confirm which content is real and which is a placeholder. A layout approved around a short sample heading may need another review when the actual service name arrives.

Point to the screen and explain the consequence

Record the design version, page, desktop or mobile view and the precise section. Annotate the relevant area or quote the affected wording. If you are reviewing a desktop capture, request the corresponding mobile concept where the arrangement matters; do not assume the smaller layout is established by the larger one.

Connect the comment to a consequence. “The enquiry action appears before the service boundary is explained” gives the designer a specific relationship to examine. Say whether this is an observed difficulty or a concern to test. Your prediction about a visitor's reaction is a useful hypothesis, not evidence that visitors have already struggled.

Separate corrections, concerns and preferences

A factual correction identifies information the business must confirm or change. A usability concern questions whether the proposed presentation supports the task. A visual preference expresses a choice between treatments. These can all deserve discussion, but they need different decisions.

For a preference, explain its connection to the agreed brand or reader need. If several treatments meet the brief, let the accountable approver choose. If the discussion reveals a new feature or audience, record it as a scope decision instead of disguising it as a small visual amendment.

Use a review record that leads to a next step

The published Pups N’ Walks case study includes a service and pricing capture. It shows dog walking, training, pop-ins and care, and pet sitting as distinct groups. The table below uses those visible features to illustrate how a concept review could be recorded. These are hypothetical review notes, not Pups N’ Walks feedback, client approval records or evidence of conversion results.

Illustrative concept review based on Pups N’ Walks’ published service capture
LocationVisible evidenceIllustrative decisionRevision check
Service headingsFour named groups separate different kinds of care.Retain the distinctions and check that the wording matches the business's offer.The revised concept keeps each service identifiable using approved copy.
Pricing rowsService options and amounts sit within their relevant groups.Have the business confirm the labels and figures; keep each amount connected to its option.Review the approved information in both desktop and mobile concepts.
Pet sitting panelA dark panel distinguishes this group from the neighbouring light panels.Ask whether visitors can identify all four choices; assess the concern rather than assuming the contrast causes confusion.Record what a representative visitor understood and decide whether a revision is needed.

The record distinguishes what the capture establishes from what still needs a decision. It does not prescribe the same layout for another business. For opening-page orientation, the separate homepage guide examines how visitors understand an offer and find a useful route.

Return one consolidated response

Let the relevant people check their areas, then give one person responsibility for the response. A service owner can confirm facts while the nominated approver resolves conflicting preferences. Send the designer one current record rather than several contradictory messages.

For each item, include the requested outcome and its status: correction required, question awaiting an answer, or decision agreed. Name the person who can resolve missing information. Ask the designer to explain the proposed response when a change affects another section or device view.

Check the revision before approving it

Compare the revised concept with the review record. Confirm that required changes are present, factual questions are resolved and neighbouring content still makes sense. Record the version being approved and any remaining conditions, including who will close them.

Keep later checks visible. Working links, form handling and other implemented behaviour require their own verification. The user acceptance testing guide addresses functioning software; concept approval does not replace that work.

Giraffe Digital's website design service connects page structure, content and enquiry journeys. For an existing site, website redesign provides a route to discuss which decisions a replacement needs to resolve.

Frequently asked questions

Who should give the final design approval?

Choose an accountable person who understands the brief and can resolve competing views. They can gather specialist checks without asking every contributor to approve every visual choice. Record the agreed decision rather than relying on silence after a group email.

What if we simply dislike part of the design?

Identify the element and explain the preference honestly. Try to connect it to the agreed identity or intended impression. Ask the designer to explain its purpose, then compare alternatives against the brief. A preference can inform a decision without being presented as a proven usability problem.

Should the concept use finished content?

Use approved or representative material for important decisions. Mark placeholders clearly and identify what must be reviewed again. Long service names, realistic descriptions and actual image proportions can expose constraints that neat sample content conceals.

How do we handle a new idea during review?

Describe the need, then ask whether it changes the agreed scope. Establish its effect on other pages, responsibilities and delivery before accepting it. Keep useful later ideas in a separate list so that approving the current direction does not depend on resolving every possible addition.

Does approving the concept mean the website is ready to launch?

No. It records agreement about a particular visual and content version. Development, content completion and checks of the implemented experience still follow. Keep the concept decision and the later release decision identifiable so that neither is mistaken for the other.

Website Design