Glare Docs

Glare is a decision framework for product and design teams

It helps product and design teams shape decisions, validate direction, align teams, and improve how decisions get made over time.

AI now makes it easy to generate more concepts, experiments, flows, prototypes, and product variations than ever before. The challenge is no longer generating ideas, but figuring out what is actually worth moving forward.

This documentation helps teams understand how Glare works, where decisions break down, and which part of the system can help create clearer direction.

Start with an idea.

Glare helps teams:

  • Drive product and design decisions

  • Validate direction with users

  • Align decisions across teams

  • Improve team decision-making over time


Framework Components

Glare is organized into six connected parts that help teams move from ideas to clearer decisions and measurable outcomes.

UX Metrics

Create measurable evidence for decisions.  Measure how people experience products, workflows, services, and interfaces.

UX Metrics help teams understand what users feel, do, complete, avoid, trust, and struggle with across products, workflows, and services.

[Image]

Most teams already have analytics and feedback. The harder part is understanding what the experience actually feels like while work is still moving. UX Metrics help teams compare ideas earlier, expose friction, and create clearer evidence before weak decisions gain momentum.

Use this section to:

  • Understand core UX metric types

  • Measure user behavior and perception

  • Compare concepts and workflows

  • Identify friction before launch

  • Build UX Metric Stacks

  • Connect UX metrics to business outcomes

πŸ‘‰ Go to UX Metrics β†’

Design Signals

Turn user response into direction. Teams often have plenty of data, feedback, and opinions, but still struggle to decide what to do next. Design Signals close that gap by connecting user behavior, UX metrics, context, and direction.

[Image]

Design signals help teams move from scattered feedback to clearer decisions.

Use this section to:

  • Define what a signal is

  • Build stronger signals from user input

  • Connect metrics to decisions

  • Evaluate signal quality

  • Create repeatable signal patterns

πŸ‘‰ Go to Design Signals β†’

AI Skills

Shape product and design decisions with AI. AI makes it easy to generate more concepts, screens, workflows, and recommendations. But evaluation, alignment, and decision-making have not sped up at the same pace.

[Image]

AI Skills give teams reusable workflows for shaping AI output into clearer decisions. They help teams move from prompts to workflows, feedback to signals, and signals to decisions.

Use this section to:

  • Install reusable Glare Skills

  • Structure workflows

  • Evaluate concepts and findings

  • Compare directions

  • Generate stronger Design Signals

  • Support decisions across the Decision Map

πŸ‘‰ Go to AI Skills β†’

Decision Map

Connect decisions to measurable outcomes.

The Decision Map is the operational core of Glare and shows how design work moves through Glare: Define, Measure, Focus, and Lead. It connects user needs, signals, decisions, and outcomes into one clear path.

[Image]

The system is organized into four connected areas:

The Decision Map helps teams keep decisions connected as work moves from exploration to measurable impact.

Use this section to:

  • Trace decisions from need to outcome

  • Connect signals to metrics

  • Show how decisions were formed

  • Connect product direction to business goals

  • Keep learning connected over time

πŸ‘‰ Go to Decision Map β†’

Design Review

Align decisions across teams. Design reviews are where teams compare ideas, discuss feedback, and shape direction. But many reviews still end with scattered opinions, unclear ownership, or decisions that reopen later.

[Image]

The Design Review section helps teams use the SIGNAL model to make reviews clearer and more useful. It shows how to move from an unclear problem to a clear next step through Surface, Identify, Ground, Navigate, Align, and Lock.

Use this section to:

  • Run stronger design reviews

  • Evaluate review conversations

  • Improve feedback quality

  • Score decision quality

  • Turn discussion into action

πŸ‘‰ Go to Design Review β†’

Design Assessment

Improve how teams make decisions. The Design Assessment helps teams understand where decision quality weakens across the organization. It looks across five dimensions: Organizing Work, Managing Complexity, Building Proof, Guiding Decisions, and Scaling Influence.

[Image]

This section helps teams see where the system is strong, where work slows down, and where small improvements could create more movement.

Use this section to:

  • Measure design maturity

  • Find where decisions slow down

  • Identify proof gaps

  • Understand where influence breaks

  • Choose what to improve next

πŸ‘‰ Go to Design Assessment β†’


Get Started

Where to Start

Start with the part of the system that feels weakest right now.

  • If your team has data but struggles to interpret direction, start with UX Metrics.

  • If your team has feedback but no clear next step, start with Design Signals.

  • If AI output is creating more noise than clarity, start with AI Skills.

  • If meetings feel productive but decisions keep reopening, start with Design Review.

  • If decisions become hard to explain later, start with Decision Map.

  • If you need to understand where organizational decision quality is breaking down, start with Design Assessment.

How the System Fits Together

Each component supports a different part of decision-making.

Together, they help teams move from scattered feedback, fast output, and slow decisions to a clearer system for making design work matter.

Next step

Not sure where to begin? Use the Get Started guide to walk through Glare with one real decision.

πŸ‘‰ Go to Getting Started β†’

Related links

Lia Garvin

Practical guide from Google Design on running design reviews that end in clear decisions. Useful when reviews drift and the team leaves without a call.

Jared Spool

Jared Spool maps five styles of design decisions - unintentional, self, genius, activity-focused, experience-focused - and argues great designers know which they're using. Useful when teams need a vocabulary for how decisions are actually getting made.

Charis Liang

Charis Liang shares a method for product designers facing competing solutions: align on the problem, then evaluate options through business needs, user needs, and tech constraints. Useful when designers, PMs, and devs disagree and the choice keeps drifting.

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