Comparing repeats the measurementComparing means repeating the same measurement while one variable changes, then reading the difference. Measure designs one test to get an answer. Comparing runs that test again across versions, competitors, segments, time periods, or another variable, with the same UX metric, the same technique, and the same kind of audience every time.This is benchmarking. A usability score, satisfaction rating, preference result, or task success rate only becomes meaningful against what it is compared with. Because only one thing changes, the team can see what changed, what improved, what fell behind, and which direction creates the strongest signal.Without comparison, results stay isolated. With comparison, signals become easier to trust.SectionPurposeOverviewExplains what Comparing is and its role inside FocusTechniquesCovers the comparison designs that set up the repeat, and what each one can provePlaybookProvides the six-step workflow, inputs, outputs, and execution guidanceReferenceContains comparison structures, tools, and per-variable lookup materialExamplesProvides worked comparisons and a pattern library for practitioners and AI-assisted workflowsAgent OperationsDefines how AI Skills behave when working with the Comparing blockWhy Comparing MattersMost decisions stall when teams look at results by themselves.A concept might score well, but is it stronger than the current version? A page might feel clear, but does it work better for new users than returning users? A competitor might look stronger, but where exactly are they winning? A design change might improve usability, but did it also weaken trust, desire, or comprehension?Comparing cuts through that uncertainty. It helps teams:• see what is stronger or weaker• understand change over time• compare concepts fairly• reveal tradeoffs between options• show where an audience responds differently• explain why a direction should move forwardA strong comparison gives the team a reason to choose.What Comparing collects, its techniques, and its toolsLike every act in Glare, Comparing has three parts:What it collects:differences across a variable, chosen in Variables.Techniques:the comparison designs below. This is where A/B tests, visual iterations, before-and-after tests, competitor benchmarks, and segment cuts now live.Tools:Helio test variations and rounds, A/B platforms such as Optimizely or VWO, analytics comparisons, and a benchmark tracker.The collection techniques themselves, such as first click, task success, surveys, and SUS, live in Define → Collecting → Techniques. A comparison reuses one of them and repeats it.Comparison designsEach design sets up the repeat differently, and each one says what the result can prove.DesignHow it worksWhat the result can proveFits these variablesRandomized A/BTwo versions shown to matched, randomly split audiencesThe design caused the difference, when significantIteration, Feature UsageRandomized multivariateSeveral combinations of elements tested at onceWhich combination works best, when significant and the sample is largeIterationWithin subjectsThe same people see every optionA real difference for the same people; vary the orderIteration, User Goals / TasksSeparate samplesDifferent people see each optionA real difference between options; cause not shownIteration, CompetitorsBefore and afterThe same measure taken again after a changeAn observed change, not proof of causeTimeline, SeasonBenchmarkYour experience measured alongside others or a standardRelative standing onlyCompetitorsSegment splitOne study, with results split by groupGroups differ; observationalSegments, Platforms / Devices, Geographies, User LifecycleWhat Goes Into ComparingComparing starts with a shared measurement. Before running the repeat, the team needs to know what is being measured, what changes, and what stays fixed.A strong comparison usually includes:a clear initiativeone named variablethe same UX metric on every sidethe same collection techniquethe same kind of audience and sourcea baseline and a cadence for the repeata sense of what size of difference counts as reala decision the comparison should supportThe point is not to compare everything. The point is to compare the things that will make the next decision clearer.How to CompareName the decision:what the comparison needs to support.Name the variable:the one thing that changes, with everything else held fixed.Choose the design:the comparison design that fits the variable and the claim the team needs to make.Set the baseline and cadence:the first run, and when the repeats happen.Read the signal and the tradeoff:what each option strengthens and what it weakens.Turn it into a finding:what was compared, which signal was stronger, what the design can and can’t prove, and what to do next.What Comes Out of ComparingThe output of Comparing is a clearer reason to choose. A strong comparison gives the team:• a side-by-side view of the work• the same measurement on every side• a clearer understanding of what changed• a tradeoff the team can explain• a finding that says what the design can and can’t prove• a next step for the initiativeThe value is not just knowing which option performed better. It is understanding why it performed better, where it creates value, and what the team should do with that signal.Where Comparing Works BestComparing works best when the team can repeat the same measurement at least twice, or has one measurement and a meaningful baseline. Use Comparing when the team needs to choose between ideas, understand improvement, review competitors, compare audiences, explain behavior, or show why one direction is stronger than another.Comparing works less well when the team has not defined the metric or decision. If the team does not know what matters, everything can look comparable. Go back to the initiative, the variable, or the UX metric before forcing a comparison.Where Comparing Fits in GlareComparing sits inside the Focus facet of Glare. Initiatives define the area of work that needs attention. Variables name what changes. Comparing repeats the measurement across the variable. Bets turn the evidence into action.In the Focus flow:•Initiativesdefine what needs attention.•Variablesname what changes.•Comparingrepeats the measurement and shows what is stronger.•Betsmove the work forward.Comparing is how Focus creates context. By repeating the same measurement while one thing changes, it helps teams see the difference between options, explain tradeoffs, and choose the direction most likely to create value.AI PromptThis prompt helps you place your signals side by side so they produce a finding rather than a data display.Start with a set of results, scores, or signals from a completed round of research or testing. It guides you to:Choose the comparison point that best fits the decision in front of youConfirm a shared metric so the comparison is fairLook for the strongest signal and the tradeoff, not just the highest scoreTurn the comparison into a finding with a named next stepYou'll end with a clear comparison backed by a shared metric and a finding that tells the team what to do next.Use this after a research round is complete and before a decision is made about whether to advance, refine, or change direction.AI SkillThe Comparing skill file teaches your AI the full 12 comparison points and five-step comparing process so it can help you turn isolated signals into a clear direction.Load it when you need to go deeper on choosing between comparison points, ensuring the metric is shared before signals are placed side by side, or interpreting what a tradeoff means for the decision. It gives your AI:The 12 comparison points with guidance on when each one fits the decisionThe five-step process from naming the decision through turning the comparison into a findingThe shared metric rule and guidance for naming tradeoffs explicitlyThe guidance for knowing when to route back to methods if the comparison won't produce a usable signalDownload the skill file below to use the full Comparing framework with your AI assistant.
Comparing
Related links
Cheat sheet comparing empathy maps, journey maps, experience maps, and service blueprints, with notes on when each is best. Useful when picking a map type for a project and you need a quick side-by-side reference.
Walks through eight ways to analyze a customer journey — from funnel and cohort views to path, sentiment, and drop-off analysis — with notes on when each one earns its keep. Useful when a team has journey data but is not sure which lens will surface the friction that matters most.
Step-by-step guide to UX benchmarking using metrics to evaluate your product against itself or competitors over time. Useful when a team wants to track progress on UX or compare against rivals.
Identify where decision quality breaks down
The Glare Design Assessment helps teams spot weak validation, stakeholder friction, alignment gaps, and assumptions that scale without measurable learning—so you have a clearer starting point for improvement.
About 5 minutes · Team-based · Diagnostic snapshot you can act on
Take the Design Assessment
