Focus

Focus is where design work gets sharper.

The Measure facet helps teams turn hunches into questions and findings. Focus takes those findings and helps teams decide what deserves more attention, what should be compared, and what direction is strong enough to move forward.

This is where teams stop treating every idea the same. A design may be understandable, but that does not mean it is the best option. A concept may test well on its own, but that does not mean it beats another direction, works across audiences, or creates enough pull to justify the investment.

Focus helps teams look at the work in context.

It brings structure to how teams run initiatives, name what changes, compare results, and place bets. The goal is not to test everything. The goal is to learn enough to put energy behind the right work.

[Image]

The third facet of the Glare framework is Focus. This is where teams narrow the work, not by guessing, but by comparing what creates the strongest signal. Teams repeat the same UX metrics while one thing changes, then use that side-by-side evidence to see which direction deserves more energy. A signal on its own can point to a problem. Focus shows which option gives the team the clearest path forward.

Every initiative needs a way to choose. Improving onboarding is not the same as testing a campaign, comparing competitors, or deciding between two product flows. Glare keeps that flexibility while giving teams a consistent way to evaluate direction, compare fairly, and make decisions with less debate.

Measure runs one test to get an answer. Focus repeats that measurement while one thing changes, so the team can see what is stronger and bet on it. Focus works through four moves:

  • Initiatives → Define the area of work that needs attention. Without a clear initiative, signals scatter across too many ideas.

  • Variables → Name the one thing that changes between measurements, like a version, an audience, a competitor, or a time period. Everything else stays the same, so the comparison is fair.

  • Comparing → Repeat the same measurement across the variable and read the difference. A/B tests, visual iterations, before-and-after tests, and benchmarks show what is stronger, weaker, or worth changing.

  • Bets → Turn evidence into action. Rank the options, size the bet to the evidence, explain the tradeoff, and move the work forward with confidence.

Focus is more than picking a winner. It sharpens design direction, tests desirability, and turns scattered signals into bets your team can act on.

What goes into Focus

Focus works best when the team has something real to evaluate. It usually starts with:

  • an initiative that needs direction

  • a concept, flow, page, or experience to test

  • a UX metric that shows what matters

  • a signal from users

  • a variable to compare across, like another version, audience, competitor, or time period

Without those inputs, Focus turns into preference. With them, the team can compare the work fairly and choose with more confidence.


Initiatives

Define the Work That Needs Focus

Most design work gets messy when the team does not agree on what is actually being improved. That’s how signals lose force: feedback spreads across too many problems, priorities compete, and no one knows what the work is meant to change. Initiatives cut through.

[Image]

They give the team a clear area of focus, like a product flow, page, feature, campaign, or journey. A strong initiative connects user needs to business goals so the team knows where to look, what to measure, and why the work matters.

  • Anchor the work in a clear opportunity.

  • Connect the initiative to user and business needs.

  • Keep the scope tight enough to learn quickly.

  • Decide what improvement would make the work stronger.

Explore the design initiatives


Variables

Name What Changes

Most comparisons go wrong when more than one thing changes. That’s how results get muddy: a new version is tested on a new audience, a redesign launches in a busy season, and no one can say what caused the difference. Variables cut through.

[Image]

They name the one thing that changes between measurements, like a version, a competitor, a segment, or a time period. Everything else stays the same, so the difference can be trusted.

  • Name one variable for each comparison.

  • Keep the metric, technique, and audience fixed.

  • Pick from the 12 variables, from Iteration to Season.

  • Use mapping methods when the variable isn’t obvious.

Explore the variables


Comparing

See What Performs Better

Most decisions stall when teams look at results in isolation. That’s how opinion returns: one score feels useful, but no one knows if it is strong, weak, or better than the alternative. Comparing cuts through.

[Image]

It repeats the same measurement across the variable so teams can see what changed, what improved, and what direction creates more pull. A strong comparison holds everything else fixed, which makes the difference easier to trust and the tradeoffs easier to explain.

  • Repeat the same metric, technique, and audience.

  • Use A/B tests, visual iterations, and before-and-after tests.

  • Benchmark against competitors and over time.

  • Find the direction with the strongest signal.

Explore design comparing


Bets

Turn Evidence Into Action

Most teams do not struggle because they lack ideas. They struggle because they do not know when to commit. That’s how momentum slips: findings sit in decks, options stay open, and meetings keep circling the same debate. Bets cut through.

[Image]

They turn signals into a clear choice the team can act on. Bets judge desirability and own Prefer signals: which option people want more, read beside how well each one works. A strong bet ranks the options, sizes the commitment to the evidence, and explains what was chosen and what was traded off.

  • Name the choice clearly.

  • Rank options with prioritizing techniques like RICE or ICE.

  • Explain the tradeoff behind the direction.

  • Move the work forward with confidence.

Explore design bets.


How Focus works

Focus moves teams from learning to choosing. It starts with an initiative. The team names the area of work where a better decision would create value. That might be a product flow, a campaign, a feature, or a key moment in the journey.

Then the team moves through four simple steps:

  • Name the initiative

  • Name the variable

  • Repeat and compare the signal

  • Place the bet

The goal is not to over-test everything. It is to take one trustworthy measurement and repeat it while one thing changes. Once the signal is captured, the team compares it across one variable at a time:

  • Versions

  • Audiences

  • Competitors

  • Time periods

That comparison shows what is stronger, what is weaker, and where the work is losing force. Then the team places the bet. They commit to a direction, explain the tradeoff, and move the work forward. Focus does not make the process heavier. It makes the decision easier to trust.

What Focus improves

When Focus is working well, teams know which work deserves attention. Research is tied to real choices, not just general learning. Comparisons become easier to explain because the team can show why one direction is stronger than another.

Focus helps teams:

  • See where to put energy

  • Compare options with the same metrics

  • Explain why one direction is stronger

  • Reduce second-guessing

  • Connect design work to measurable progress

That clarity helps decisions move faster. Stakeholders spend less time circling the same debate, and design feels more connected to progress the team can see. Focus helps teams narrow the work without narrowing the thinking. It keeps teams open while learning, then decisive when the signal is clear.

What comes out of Focus is a clear bet. A strong bet explains:

  • what the team chose

  • which signal supported the choice

  • what tradeoff was made

  • what should happen next

That keeps the work from stalling after the research is done. The team does not just learn something. It moves.


Where Focus fits in Glare

Focus sits between Measure and Lead.

Measure shows what is working. Focus helps teams decide what to do with that learning. Lead connects those bets to business goals, workflows, maps, and results.

In the full Glare system:

  • Define clarifies what matters.

  • Measure tests what works.

  • Focus decides what to do.

  • Lead shows what it drives.

Focus is the turning point where signals become choices, and choices become momentum.

Related links

Ilse Blom

Suggests using stakeholder willingness to pivot, clarity on insight use, and team alignment as filters to skip research that won't change anything. Useful when triaging incoming requests and you want to avoid spending weeks on a study that nobody will act on.

Figma

Figma's resource on what a decision matrix is and how teams use it for product and design picks. Useful when a team wants a tool for picking between options without endless meetings.

Tom Greever

Tom Greever's IDEAL framework (Identify, Describe, Empathize, Lock) for responding to design feedback, paired with four categories: business, design, research, limitations. Useful when a designer wants a script for hard stakeholder questions.

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