How to review a website design concept

Agree on evaluation criteria before the presentation

Reviewers should know the concept’s job before they see it. Revisit the approved audience, positioning, page goals, content hierarchy, brand principles, and technical constraints. If those foundations are unresolved, visual feedback will become a proxy argument about strategy.

Ask the studio what the concept is intended to prove. An early direction may demonstrate visual language and hierarchy rather than every page or interaction. Match the feedback to the maturity of the work.

Follow a real visitor journey

Choose a priority scenario and trace it from entry to action. Can a visitor understand the offer, see who it is for, find credible detail, answer a likely objection, and know what to do next? Review the words and their order as part of the design rather than as decoration to add later.

Check whether navigation labels, calls to action, forms, and supporting links are specific enough to make the path predictable. Use the broader guide to business website requirements when a concept reveals missing content or functions.

Judge the system, not one polished screen

A strong concept should extend beyond a hero section. Ask to see representative content types, long and short headings, proof, forms, lists, error states, and a page with ordinary information density. Look for reusable rules that keep the site coherent as content changes.

Review at relevant desktop and mobile widths. Confirm what happens when text wraps, images crop, navigation collapses, controls are touched rather than clicked, and optional content is absent. Mobile is not a smaller screenshot; it is a different layout condition.

Turn reactions into useful feedback

Separate observations from solutions. “The main action is hard to find” gives the studio a problem to solve; “make this button red” skips the reasoning. Explain which agreed criterion is not being met and what the business or user consequence would be.

Collect comments through one decision owner, resolve contradictions internally, and rank feedback as required, important, or exploratory. Avoid anonymous voting. Design is accountable to the brief and customer journey, not the average of personal taste.

Approve a direction with explicit conditions

• Strategy: the concept expresses the positioning and page priorities.
• Content: hierarchy works with realistic approved material.
• Journey: priority visitors can reach a meaningful next step.
• System: components can support the full planned page set.
• Responsive: key layouts and interactions work across widths.
• Accessibility: contrast, focus, semantics, and states are accounted for.