Ideas rarely collapse because they’re bad.
They collapse because proof comes too late. Meetings drag on, debates stall, and momentum disappears.
Measure cuts through the Fog. It turns intuition into signals—evidence teams can act on in the moment. This is where muddled concepts get exposed, usefulness gets tested, and ideas either earn clarity or fall away before wasting cycles.
At its core, Measure makes design intent visible and tied to real problems. It keeps momentum alive by showing if the work connects with users and delivers value leaders can trust.
[Image]
The second facet of the Glare framework is Measure. This is where ideas get tested, not just discussed. Teams use UX metrics and feedback to show if a concept truly makes sense. Data on its own is noise. Design signals, captured through sharp questions in the moment, turn it into clarity.
Every concept demands its own lens. Measuring onboarding isn’t the same as testing an ad or refining an app. Glare keeps that flexibility while holding consistency across projects, so teams compare fairly and move with confidence.
Measure runs one test to get an answer, and Focus repeats it while one thing changes. Measure works through four moves:
-
Concepts → Define clear goals that connect design work to user and business challenges. Without them, effort scatters.
-
Hunches → Start with informed guesses, each written with the questions that would prove or kill it.
-
Testing → Put the hunch against real evidence: a study, a standard instrument, or data the team already has.
-
Findings → Call the hunch, then turn the evidence into a design signal. Each one reduces doubt and keeps ideas alive long enough to prove their value.
Measure is more than collecting data. It sharpens design intent, tests usefulness, and turns assumptions into clarity.
Concepts
Define Clear Design Objectives
Most design stalls because teams chase too many ideas without a clear anchor. That’s how the indecision creeps in: effort scatters, intent blurs, and momentum dies. Concepts cut through.
They tie design work to real user challenges and business priorities, so every step drives toward outcomes that matter. A strong concept is the first signal of clarity.
-
Anchor in real user problems.
-
Focus on one challenge at a time.
-
Align teams around shared goals.
-
Decide which signals matter most.
[Image]
Hunches
Explore Early Ideas
The danger isn’t having hunches, it’s mistaking them for facts.
Left untested, they turn into opinion battles that drain confidence. Signals flip the script. A hunch becomes a hypothesis, quickly confirmed or killed. Instead of guessing in the dark, teams move forward with clarity, stacking small wins into momentum.
-
Treat hunches as testable hypotheses.
-
Act without waiting for perfect data.
-
Spark creative exploration.
-
Write the questions that would prove each one.
[Image]
Testing
Put Hunches to the Test
Untested beliefs cloud decisions. They sound fine in a meeting but leave teams stuck in indecision.
A good test reveals the truth: does this make sense, help users finish, and move the business forward? Testing puts each hunch in front of real evidence, from a quick first-click study to a presale, and records how strong that evidence is, so leaders can act now, not months later.
-
Match the technique to the hunch.
-
Run standard instruments as written.
-
Give the evidence a rating: weaker, moderate, or stronger.
-
Record every result with its source.
[Image]
Findings
Turn Data into Design Signals
Data doesn’t kill indecision, design signals do. Raw numbers are too slow, too abstract.
Findings bridge the gap, turning patterns into clarity that drives the next decision. Findings judges usefulness and owns Use signals. Each finding opens with the verdict on the hunch, then states the design signal and the next move. One strong finding can save weeks of wasted work. Ten stacked together can reset a roadmap.
-
Call the hunch: Supported, Challenged, Refuted, or No call.
-
Turn the evidence into a Use signal, and say who it holds for.
-
Pick the next move from the five decision types: Implement, Refine Design, Test Iteration, Revisit Later, or Do Not Pursue.
-
Share findings to build trust.
Here’s what to consider when analyzing findings
[Image]
Measure connects intent to usefulness. It transforms hunches into tested evidence, questions into clarity, and findings into signals leaders can trust. Without it, teams stall. With it, they move forward with confidence.