Example 1 — Homepage hero
Question: “Which hero communicates what we do more clearly?” Show two or three homepage directions (static mocks are enough). What to look for: whether people can describe the product back accurately, and which layout feels trustworthy at a glance. A common pattern is a clear winner on clarity even when internal taste preferred a more “creative” option. CTA after: create the same test with your audience.
Example 2 — Headline / value proposition
Question: “Which headline explains the product better?” Present three short lines with the same supporting context. Reasons usually cluster around clarity, specificity, and tone (“professional,” “too vague,” “sounds like everyone else”). This is one of the fastest preference tests to run because the options are cheap to produce.
Example 3 — Pricing presentation
Question: “Which pricing layout is easier to understand?” Compare plan cards, feature tables, or packaging. You are not measuring willingness to pay yet — you are learning which presentation people can parse. Watch for comments about overwhelm, hidden costs, and which plan they think is “for them.”
Example 4 — Logo or brand mark
Question: “Which logo feels more trustworthy for this brand?” Keep the question tied to a job (trust, modernity, fit for the category) rather than pure aesthetics. Minority opinions matter here: a small group strongly rejecting a mark can be as important as a mild majority preference.
Example 5 — Landing-page direction
Question: “Which landing page direction would you be more likely to explore?” Useful before a build or a rewrite. Prefer asking about understanding and next-step intent over “which is prettier.” Pair with a follow-up reason so you know whether people grasped the offer.
Example 6 — Ad or campaign creative
Question: “Which ad makes the offer clearest?” Show image-led or copy-led variants. Preference testing will not replace platform A/B tests on spend, but it helps you kill weak concepts before you buy traffic — especially when stakeholders disagree in the review.
Example 7 — Client creative directions
Question: “Which direction should we take forward for [client / project]?” Send the link to the client’s customers or community, not only the internal team. Presenting a preference split with themes changes the conversation from competing opinions to evidence. Share the results page as part of your recommendation.
How to read an example result
Start with the split, then read the reasons. If 65% chose B because it was “clearer what the product does,” protect that clarity as you refine. If the split is 52/48 with contradictory reasons, the options may be too close — or the decision may not be about design at all. Thin or joke responses should be filtered so they do not distort the themes.
Run your own version
Pick one decision, write one focused question, and put the options in front of the people who matter. Wingral turns the responses into a preference split, themes, and a recommendation you can share. Your first preference test is free with the full product.
What you get
- Homepage heroes and landing-page directions
- Headlines and value propositions
- Pricing layouts and packaging
- Logos and brand marks
- Ads and campaign creative
- Client-facing creative recommendations