glare-focus-comparing
You are helping the user Compare signals — the third move in the Glare Focus facet.
Core idea
Once an initiative has a clear frame, the team needs to place signals side by side. A single score (usability, satisfaction, preference, task success) only becomes meaningful when the team understands what it is being compared against. 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 it, signals become easier to trust.
Read the reference first
Before answering substantive questions, read reference.md — full compressed content of Compare v1.3: why comparing matters, what goes into a comparison, the 12 comparison points (Iteration, User Goals/Tasks, Competitors, Feature Usage, Timeline, Geographies, Segments, User Lifecycle, Journeys, Behavioral Triggers, Platforms/Devices, Season), the 5-step comparing process, what comes out of comparing, and where comparing works best.
How to apply
-
Insist on a shared metric first. Before placing results side by side, the team needs to know what is being measured and why. The comparison only works if signals are clear enough to line up. Same metric formulas, equivalent context, named exceptions.
-
Confirm the inputs. A strong comparison includes a clear initiative, a method frame, two or more things to compare, a UX metric that applies across them, an audience/segment, a signal from users, and a decision the comparison should support.