How to Compare Two Website Design Concepts Without Guessing

When a client is shown two design concepts, the review can turn into a vote on personal taste. One person prefers the color in A; another likes the layout in B. A better comparison starts with the brief and asks which concept supports the intended audience and task more clearly.

Agree on criteria before comparing

Choose a short set of criteria that follows the project goal. For a small business homepage, useful criteria might include:

1. Audience fit: Does the concept speak to the people the website needs to reach?
2. Message clarity: Can a visitor tell what is offered and why it is relevant?
3. Next step: Is the primary action visible and understandable?
4. Content fit: Does the concept accommodate the real copy, imagery and proof points?
5. Brand fit: Does it use the supplied identity in a way the client recognizes?
6. Practicality: Can the direction support the required pages and device layouts?

Score evidence, not taste

Use a simple table with three columns: criterion, concept A evidence, concept B evidence. Add a score only if it helps focus discussion, and define the scale. For example, 1 means “not demonstrated,” 2 means “partly demonstrated,” and 3 means “clearly demonstrated.” A score is a discussion aid, not user research or proof of future performance.

Ask each reviewer to point to visible evidence. “B feels more premium” is a starting reaction. Follow up with: which element creates that impression, does the brief ask for it, and will the target audience understand the offer? This moves the conversation from preference to rationale.

Keep concept selection separate from refinement

Do not combine the best pieces of every concept before choosing a direction. First decide which overall approach best answers the brief. Then list specific elements to refine. Otherwise, the result can become a compromise that no longer has a clear hierarchy.

Ask the same questions about both concepts

• What does a first-time visitor think this organization offers?
• Where would they go to complete the primary task?
• Which content is missing or difficult to scan?
• Does the concept still make sense with the actual copy and imagery?
• What assumptions should be tested in a prototype or built page?

Document the decision

Record the selected concept, the criteria used, any unanswered questions, and which elements are approved versus still open. Name one approval owner. If important stakeholders disagree, ask the owner to resolve the conflict against the brief rather than blending contradictory preferences.

Share both concepts at the same size and with the same context. A long-page preview can help reviewers compare page flow; Swelik’s client presentation checklist covers how to frame that review.

Make the comparison fair

Show both concepts with the same content, viewport, crop and project context. If one design contains finished copy and the other uses placeholders, the comparison is not balanced. Give reviewers the same goal and the same criteria before they inspect either direction. For a group review, ask people to write their evidence independently before discussion so the first speaker does not set the answer for everyone.

Use a lightweight decision matrix

Criterion	Concept A evidence	Concept B evidence	Decision
Offer clarity	What can a new visitor explain?	What can a new visitor explain?	[A / B / test]
Primary action	Can it be found?	Can it be found?	[A / B / test]
Content fit	Does real copy fit?	Does real copy fit?	[A / B / test]
Brand fit	Which approved rule supports it?	Which approved rule supports it?	[A / B / test]

Use “test” when the evidence is insufficient. That may mean creating a prototype or asking representative users what they understand. Do not frame a stakeholder vote as user validation.

Separate selection from iteration

First choose a direction against the brief. Next, list refinements that strengthen that direction. If the client asks to combine parts from both, discuss the effect on hierarchy and coherence. A mix can work, but it should be reviewed as a new concept rather than assumed to be the best of both automatically.

Record the rationale, not only the winner

Write down the chosen concept, the criteria that mattered most, the reviewer who owns the decision and any test still required. If a concept is rejected because a requirement is missing, record that requirement. It may be useful later if scope or audience changes. This short decision note reduces the chance that an old concept returns without its original context.

Frequently asked questions

Should a client choose the design they personally like most?

Personal response matters, but it is one input. Compare each direction against audience, message, project goals and the content that must fit.

Can a score choose the winning concept automatically?

No. Scores help make reasoning visible. The decision owner should interpret the evidence and resolve tradeoffs.