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 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. They spark exploration and give signals something to confirm or kill.
-
Questioning → Ask sharper questions that uncover what matters. The right framing turns noise into usable answers.
-
Findings → Translate raw data into signals. 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.
-
Balance instinct with signals as proof.
[Image]
Questioning
Question Gains Deeper Signals
Weak questions cloud decisions. They sound fine in a meeting but leave teams stuck in indecision.
Strong questions reveal the truth: does this make sense, help users finish, and move the business forward? Every sharp question is a cut through confusion, turning feedback into signals leaders can act on now—not months later.
-
Avoid biased framing.
-
Tie questions to outcomes.
-
Uncover the “why” behind behavior.
-
Refine questions with each round.
Here’s how to ask the right questions
[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. One strong finding can save weeks of wasted work. Ten stacked together can reset a roadmap. Findings are where noise ends and momentum begins.
-
Spot patterns that reveal blockers.
-
Translate data into actionable signals.
-
Align user and business needs.
-
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.
