Comparing

Comparing shows what performs better.Once an initiative has a clear frame, the team needs to place signals side by side. A single score can be useful, but it rarely tells the whole story. A usability score, satisfaction rating, preference result, or task success rate only becomes meaningful when the team understands what it is being compared against.That is the job of Comparing. Comparing helps teams see what changed, what improved, what fell behind, and which direction creates the strongest signal. It gives context to the data so teams can explain why one option deserves more energy than another.Without comparison, results stay isolated. With comparison, signals become easier to trust.Why 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 weakerunderstand change over timecompare concepts fairlyreveal tradeoffs between optionsshow where an audience responds differentlyexplain why a direction should move forwardA strong comparison gives the team a reason to choose.What goes into ComparingComparing starts with a shared metric.Before placing results side by side, the team needs to know what is being measured and why it matters. The comparison only works if the signals are clear enough to line up.A strong comparison usually includes:a clear initiativea method frametwo or more things to comparea UX metric that applies across the comparisonan audience or segmenta signal from usersa decision the comparison should supportThe team might compare two concepts, two versions, two audiences, two competitors, two moments in a journey, or the same experience over time.The point is not to compare everything.The point is to compare the things that will make the next decision clearer.What teams compareComparing can happen across many parts of the work.The right comparison depends on the initiative, the method frame, and the decision the team needs to make. A team may compare versions, audiences, moments, behaviors, competitors, or time periods. Each comparison gives the signal more context.The goal is not to compare everything. The goal is to compare the parts of the work that will make the next decision clearer.IterationCompare iterations when the team needs to understand whether the work is getting stronger across versions.This helps teams see if changes are improving the signal or just creating more activity. One version may be clearer. Another may create more trust. A third may reduce friction but weaken desire.Use this to answer:Did the new version improve the signal?Which change created the most lift?What got stronger or weaker between versions?Is the design ready to move forward, or does it need another pass?Iteration comparisons help teams avoid endless refinement. They show when the work is actually improving.User Goals / TasksCompare user goals and tasks when the team needs to understand how well the experience supports what people are trying to do.Some tasks may be easy while others create friction. Some goals may feel valuable but be hard to complete. Comparing tasks helps the team see where the experience supports progress and where it breaks down.Use this to answer:Which task is easiest or hardest to complete?Which goal matters most to users?Where does effort increase?Which task should the team improve first?User goal and task comparisons help teams focus on what people are actually trying to accomplish.CompetitorsCompare competitors when the team needs market context.A design may perform well on its own but still fall behind user expectations shaped by other products. Competitor comparisons help teams see where the experience feels stronger, weaker, clearer, slower, or less trusted.Use this to answer:Where do competitors create more clarity?Where does our experience create more value?What expectations are users bringing from the market?Which competitor gap should shape the next decision?Competitor comparisons help teams make design choices with outside context, not just internal opinion.Feature UsageCompare feature usage when the team needs to understand which parts of the product create value.Some features get used often but do not create much satisfaction. Others may be used less often but matter deeply to a smaller group. Comparing feature usage helps teams see what to improve, promote, simplify, or remove.Use this to answer:Which features create the most value?Which features are ignored or misunderstood?Which features support retention or adoption?What should be built, improved, reduced, or removed?Feature usage comparisons help teams focus product energy on the parts that matter most.TimelineCompare across a timeline when the team needs to understand change, order, or priority.Some decisions depend on what should happen now, next, or later. Others depend on whether the experience is improving over time. Timeline comparisons help teams see progress, urgency, and sequence.Use this to answer:What needs attention first?Are signals improving over time?What changed after a design update?Which decision is blocking the next step?Timeline comparisons help teams move in the right order instead of treating every problem as equally urgent.GeographiesCompare geographies when the experience needs to work across regions, markets, or cultures.A message that feels clear in one market may feel confusing in another. A workflow that fits one region may run into language, trust, behavior, or compliance differences elsewhere.Use this to answer:Where does the experience perform better or worse by region?Do users in different markets understand the message the same way?What local expectations affect trust or action?Which region needs a different approach?Geography comparisons help teams avoid assuming one experience works the same everywhere.SegmentsCompare segments when different groups may respond differently to the same experience.Averages can hide the real story. New users may struggle while power users move easily. Buyers may care about different proof than admins. Comparing segments helps the team see which audience needs more support.Use this to answer:Which segment sees the most value?Which group struggles more?Where do needs differ?Which direction works across groups, and which needs to be tailored?Segment comparisons help teams make better decisions for the right audience instead of designing for a vague average.User LifecycleCompare lifecycle stages when the initiative affects users at different points in their relationship with the product.What matters during awareness may be different from what matters during onboarding, adoption, retention, or expansion. Lifecycle comparisons help teams see how needs shift over time.Use this to answer:What does a new user need compared to an existing user?Where does the experience lose momentum in the lifecycle?Which stage needs more support?What signal shows users are ready to move to the next stage?Lifecycle comparisons help teams design for where users are, not where the business wishes they were.JourneysCompare journeys when the work spans multiple steps, touchpoints, or channels.A single screen may test well while the full journey still feels broken. Journey comparisons help teams see how signals connect across the experience and where momentum drops.Use this to answer:Which journey moment creates the most friction?Where does the user lose confidence?Which touchpoint needs more support?What part of the journey should be improved first?Journey comparisons help teams solve the experience, not just the screen.Behavioral TriggersCompare behavioral triggers when the team needs to understand what causes users to act.A user may understand the experience but still not move. Behavioral trigger comparisons help teams see what prompts action, what creates hesitation, and what conditions need to be in place for behavior to change.Use this to answer:What makes users start?What helps users continue?What causes hesitation or drop-off?Which prompt, message, or moment creates stronger action?Behavioral trigger comparisons help teams move from passive interest to real behavior.Platforms / DevicesCompare platforms and devices when the experience changes across context.The same design may work well on desktop but break on mobile. A flow may feel simple on one platform and frustrating on another. Platform and device comparisons help teams see where the experience holds up and where it needs adjustment.Use this to answer:Does the experience work across mobile, desktop, tablet, or other devices?Where does usability drop by platform?Which context changes the user’s behavior?What needs to be adapted for the device or channel?Platform and device comparisons help teams design for how people actually experience the work.SeasonCompare seasonality when timing changes user needs, expectations, or behavior.Some products, campaigns, and workflows behave differently depending on the time of year, budget cycles, enrollment periods, holidays, renewal windows, launches, or market events. Season comparisons help teams see whether a signal is stable or tied to a specific moment.Use this to answer:Does behavior change by season or cycle?Are users more motivated at certain times?Does the message work better during one period than another?Is the signal durable, or is it tied to timing?Season comparisons help teams avoid mistaking a temporary spike or dip for a permanent pattern.How to compare designStart with the decision the team needs to make. Comparing is not just placing charts next to each other. It is choosing the comparison that will make the decision easier.Use five steps.1. Name the decisionClarify what the comparison needs to support.The decision might be which concept to move forward, which version to refine, which audience to prioritize, which competitor gap matters most, or which part of the journey needs attention.If the decision is unclear, the comparison will feel like a report instead of a guide.2. Choose the comparison pointDecide what should be placed side by side.The team might compare:one iteration against anothertask performance across user goalsyour experience against competitorsfeature usage across product areasperformance across a timelineresults across geographiesresponses across segmentsneeds across the user lifecyclemoments across a journeybehavioral triggers across contextsexperiences across platforms or devicesbehavior across seasons or cyclesThe comparison point should connect directly to the decision.3. Use the same metricUse a shared UX metric so the comparison is fair.If one version is measured by comprehension and another is measured by satisfaction, the team may be comparing different kinds of signals. That can still be useful, but it needs to be named clearly.A shared metric makes the difference easier to understand.4. Look for the strongest signal and the tradeoffDo not only ask which option wins.Ask what each option strengthens and what it weakens. A version may improve clarity but reduce appeal. A competitor may create more trust but less speed. A journey moment may be useful but hard to complete.The strongest direction is not always the one with the highest score.It is the one with the best signal for the decision the team needs to make.5. Turn the comparison into a findingA comparison should end with a clear finding.That finding should explain:what was comparedwhich signal was strongerwhat tradeoff showed upwhat the team should do nextThis keeps the comparison from becoming a data display. It turns the evidence into direction.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 worka shared metric for judging optionsa clearer understanding of what changeda tradeoff the team can explaina finding that supports a decisiona next step for the initiativeThe value is not just knowing which option performed better. The value 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 has at least two signals or one signal and a meaningful reference point. 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, method, or 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. Methods frame the data. Comparing places signals side by side. Decisions turn the evidence into action.In the Focus flow:Initiatives define what needs attention.Methods frame the data.Comparing shows what is stronger.Decisions move the work forward.Comparing is how Focus creates context.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.