Guide · Test implementation · 2 min read

Done is better than perfect: Quick A/B test variations that still teach you something

Why simple, wireframe-level A/B test variations often beat polished redesigns: faster tests, clearer learnings, and the QA and accessibility rules that still apply.

The short answer

Every week a test idea waits for design is a week you learn nothing. So build the smallest variation that tests the hypothesis, using your existing components and styles, make sure it works and is accessible, and launch it. If it wins, polish it when you roll it out.

This is a practitioner view, one our expert reviewer repeats often: done is better than perfect. It isn’t permission to ship broken things. It’s a push to stop gold-plating ideas nobody has validated yet.

Why small and quick wins

  • More tests, more learnings. Teams that test more learn faster, and most ideas don’t move the metric they were meant to (Kohavi, Tang and Xu, 2020). You want to find that out cheaply.
  • Clearer results. A variation with one change tells you what caused the effect. A redesign with twelve changes tells you only that “something” happened.
  • Less sunk cost. When a team spent a month on a variation, nobody wants it to lose. That pressure leads to peeking and over-reading results.

What “quick” looks like

Polished redesign Quick variation
New layout, new imagery, new copy One change: the copy, or the order, or the element
Custom illustrations and animation Existing components and styles
Three weeks of design reviews A short brief and one review
Built from scratch Built with your testing tool or a feature flag

Example: your hypothesis says shoppers don’t see delivery information. The quick variation adds one line under the price using your existing note style. It doesn’t redesign the product page.

What still applies, always

Quick is about scope, not quality. Every variation still needs:

  • Works everywhere. Checked on mobile and desktop, in the main browsers.
  • Accessible. Text contrast, labels, keyboard use and screen reader announcements meet WCAG 2.2 AA. An inaccessible variation can lose for reasons unrelated to your idea.
  • No flicker. The original shouldn’t flash before the variation appears.
  • Tracking parity. The primary metric fires identically in both versions.
  • Honest content. No fake claims just because it’s “only a test”.

When polish is worth waiting for

  • The hypothesis is about the experience itself, for example “a more premium look increases average order value”. Then the look is the change.
  • Brand or legal standards apply, such as regulated wording.
  • The test is a big bet on a key page with lots of traffic, where you only get a few shots a year.

What to do next

Write the one change into a hypothesis, then plan how long it needs to run with the sample size calculator. If the idea came from a stakeholder, read let the boss’s idea run first.

Frequently asked questions

Do A/B test variations need to be fully designed?

No. A variation needs to change the thing your hypothesis is about, clearly and cleanly. Visual polish can come after the idea has proven itself. It still has to work on every device, be accessible and track correctly.

Won't an unpolished variation lose because it looks worse?

It can, if it looks broken or inconsistent with the site. That's why 'quick' means using existing components and styles, not rough sketches. Users should not be able to tell which version took less time to build.

Sources (2)

  1. Trustworthy Online Controlled Experiments: A Practical Guide to A/B Testing. Cambridge University Press (Kohavi, Tang, Xu, 2020). Accessed 4 November 2026.
  2. Web Content Accessibility Guidelines (WCAG) 2.2. W3C. Accessed 4 November 2026.

Search lessons, guides, case studies and templates. Press Esc to close.