Techniques

Turn methods into momentum

Design debates often stall when teams argue opinions. Techniques break that cycle. They are the tactical moves that turn assumptions into signals you can trust.

Most teams already know the names — card sorting, first-click tests, usability studies. The problem is they run them as one-offs, disconnected from UX metrics. Findings sound interesting but rarely change a decision.

Glare fixes this by anchoring each technique to the metrics it produces. That connection is what makes findings credible and decisions traceable. Each technique below links to its own landing page with full guidance, examples, and step-by-step instructions.

How to Choose a Technique

Start with the mode, not the method. The three modes of learning determine which group of techniques to reach for.

<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 516px;"><colgroup><col style="min-width: 25px;"><col style="width: 235px;"><col style="width: 256px;"></colgroup><tbody><tr><td colspan="1" rowspan="1">Mode</td><td colspan="1" rowspan="1" colwidth="235">When</td><td colspan="1" rowspan="1" colwidth="256">Technique Groups to Use</td></tr><tr><td colspan="1" rowspan="1">Exploratory</td><td colspan="1" rowspan="1" colwidth="235">Early discovery, before clear hypotheses.</td><td colspan="1" rowspan="1" colwidth="256">Navigation, Feedback</td></tr><tr><td colspan="1" rowspan="1">Evaluative</td><td colspan="1" rowspan="1" colwidth="235">Mid-cycle, testing ideas or designs.</td><td colspan="1" rowspan="1" colwidth="256">Task, Behavior</td></tr><tr><td colspan="1" rowspan="1">Comparative</td><td colspan="1" rowspan="1" colwidth="235">Choosing between versions or directions.</td><td colspan="1" rowspan="1" colwidth="256">Comparison, Behavior</td></tr></tbody></table>

Once the mode is clear, match the specific question to the technique that is built to answer it.

Five-Step Usage Discipline

Apply this to every technique, regardless of which one you choose:

• Pick the metric. What do you want to measure — completion, comprehension, desirability?

• Choose the technique. Match the method to the metric, not the other way around.

• Run lean. Small samples often surface clear signals. Five users can reveal major friction.

• Pair techniques. Task Success plus Time on Task shows both whether users finish and how hard it felt.

• Share signals. Frame results in terms of the UX metric, not raw output.

Traps to Avoid

• Running without a metric. A card sort is just boxes unless it is tied to comprehension or usability.

• One-and-done. Techniques work best in layers. A single test rarely tells the whole story.

• Overcomplicating sample sizes. More participants do not always mean more signal. Match sample size to the confidence the decision requires.

• Reporting raw counts. A percentage is a signal. A list of observations is not.

Navigation

Navigation techniques reveal how users understand and move through information. Use them when designing or auditing structure, labels, or taxonomy.

<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 472px;"><colgroup><col style="min-width: 25px;"><col style="width: 266px;"><col style="width: 181px;"></colgroup><tbody><tr><td colspan="1" rowspan="1">Technique</td><td colspan="1" rowspan="1" colwidth="266">What It Measures</td><td colspan="1" rowspan="1" colwidth="181">UX Metrics</td></tr><tr><td colspan="1" rowspan="1"><a target="_blank" rel="noopener noreferrer nofollow" href="https://glare.zurb.com/docs/decision-map/define/collecting/techniques/card-sorting">Card Sorting</a></td><td colspan="1" rowspan="1" colwidth="266">How users group and label content. Reveals mental models and expectations about information structure.</td><td colspan="1" rowspan="1" colwidth="181">Comprehension, Expectations</td></tr><tr><td colspan="1" rowspan="1"><a target="_blank" rel="noopener noreferrer nofollow" href="https://glare.zurb.com/docs/decision-map/define/collecting/techniques/tree-testing">Tree Testing</a></td><td colspan="1" rowspan="1" colwidth="266">Whether users can find content within a defined navigation structure, without visual design as a cue.</td><td colspan="1" rowspan="1" colwidth="181">Comprehension, Success Rate, Expectations</td></tr></tbody></table>

Task

Task techniques measure whether users can complete specific goals. They are the most direct signal of whether a design works.

<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 471px;"><colgroup><col style="min-width: 25px;"><col style="width: 265px;"><col style="width: 181px;"></colgroup><tbody><tr><td colspan="1" rowspan="1">Technique</td><td colspan="1" rowspan="1" colwidth="265">What It Measures</td><td colspan="1" rowspan="1" colwidth="181">UX Metrics</td></tr><tr><td colspan="1" rowspan="1"><a target="_blank" rel="noopener noreferrer nofollow" href="https://glare.zurb.com/docs/decision-map/define/collecting/techniques/first-click-testing">First Click Testing</a></td><td colspan="1" rowspan="1" colwidth="265">Whether users instinctively start a task in the right place. Correct first click predicts 87% task completion.</td><td colspan="1" rowspan="1" colwidth="181">Success Rate, Comprehension, Desirability</td></tr><tr><td colspan="1" rowspan="1"><a target="_blank" rel="noopener noreferrer nofollow" href="https://glare.zurb.com/docs/decision-map/define/collecting/techniques/task-success-rate">Task Success Rate</a></td><td colspan="1" rowspan="1" colwidth="265">Whether users complete the intended task. Successful completions divided by total attempts.</td><td colspan="1" rowspan="1" colwidth="181">Completion, Comprehension, Drop-Off</td></tr><tr><td colspan="1" rowspan="1"><a target="_blank" rel="noopener noreferrer nofollow" href="https://glare.zurb.com/docs/decision-map/define/collecting/techniques/time-on-task">Time on Task</a></td><td colspan="1" rowspan="1" colwidth="265">How long users take to complete a task. Paired with Task Success Rate, reveals effort alongside completion.</td><td colspan="1" rowspan="1" colwidth="181">Efficiency, Success Rate</td></tr></tbody></table>

Comparison

Comparison techniques measure which version, message, or direction performs better. Use them when a decision between options needs proof, not preference.

<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 471px;"><colgroup><col style="min-width: 25px;"><col style="width: 265px;"><col style="width: 181px;"></colgroup><tbody><tr><td colspan="1" rowspan="1">Technique</td><td colspan="1" rowspan="1" colwidth="265">What It Measures</td><td colspan="1" rowspan="1" colwidth="181">UX Metrics</td></tr><tr><td colspan="1" rowspan="1"><a target="_blank" rel="noopener noreferrer nofollow" href="https://glare.zurb.com/docs/decision-map/define/collecting/techniques/ab-testing">A/B Testing</a></td><td colspan="1" rowspan="1" colwidth="265">Which of two live versions performs better on a single variable change.</td><td colspan="1" rowspan="1" colwidth="181">Conversion Rate, Bounce Rate, Engagement</td></tr><tr><td colspan="1" rowspan="1"><a target="_blank" rel="noopener noreferrer nofollow" href="https://glare.zurb.com/docs/decision-map/define/collecting/techniques/multivariate-testing">Multivariate Testing</a></td><td colspan="1" rowspan="1" colwidth="265">Which combination of page elements performs best together.</td><td colspan="1" rowspan="1" colwidth="181">CTR, Comprehension, Desirability</td></tr><tr><td colspan="1" rowspan="1"><a target="_blank" rel="noopener noreferrer nofollow" href="https://glare.zurb.com/docs/decision-map/define/collecting/techniques/conversion-rate-analysis">Conversion Rate Analysis</a></td><td colspan="1" rowspan="1" colwidth="265">Whether users complete the goal action at the end of a defined funnel.</td><td colspan="1" rowspan="1" colwidth="181">Success Rate, Drop-Off, Desirability</td></tr></tbody></table>

Behavior

Behavior techniques show what users actually do at scale. They reveal patterns that individual sessions miss but cannot explain the reasoning behind them.

<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 470px;"><colgroup><col style="min-width: 25px;"><col style="width: 265px;"><col style="width: 180px;"></colgroup><tbody><tr><td colspan="1" rowspan="1">Technique</td><td colspan="1" rowspan="1" colwidth="265">What It Measures</td><td colspan="1" rowspan="1" colwidth="180">UX Metrics</td></tr><tr><td colspan="1" rowspan="1"><a target="_blank" rel="noopener noreferrer nofollow" href="https://glare.zurb.com/docs/decision-map/define/collecting/techniques/heatmaps">Heatmaps</a></td><td colspan="1" rowspan="1" colwidth="265">Where users focus attention and click on a page. Reveals what draws engagement and what gets missed.</td><td colspan="1" rowspan="1" colwidth="180">Desirability, CTR, Comprehension</td></tr><tr><td colspan="1" rowspan="1"><a target="_blank" rel="noopener noreferrer nofollow" href="https://glare.zurb.com/docs/decision-map/define/collecting/techniques/clickstream-analysis">Clickstream Analysis</a></td><td colspan="1" rowspan="1" colwidth="265">How users navigate through a multi-step flow, including where they detour, backtrack, or drop off.</td><td colspan="1" rowspan="1" colwidth="180">Drop-Off, Efficiency, Frequency</td></tr><tr><td colspan="1" rowspan="1"><a target="_blank" rel="noopener noreferrer nofollow" href="https://glare.zurb.com/docs/decision-map/define/collecting/techniques/web-analytics">Web Analytics</a></td><td colspan="1" rowspan="1" colwidth="265">Site-wide health and trends at scale. Reveals what is happening across the full experience over time.</td><td colspan="1" rowspan="1" colwidth="180">Session Duration, Bounce Rate, Conversion Rate</td></tr></tbody></table>

Feedback

Feedback techniques capture what users say, feel, and perceive. They are the attitudinal layer that behavioral data alone cannot provide.

<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 467px;"><colgroup><col style="min-width: 25px;"><col style="width: 262px;"><col style="width: 180px;"></colgroup><tbody><tr><td colspan="1" rowspan="1"><h4>Technique</h4></td><td colspan="1" rowspan="1" colwidth="262"><h4>What It Measures</h4></td><td colspan="1" rowspan="1" colwidth="180"><h4>UX Metrics</h4></td></tr><tr><td colspan="1" rowspan="1"><a target="_blank" rel="noopener noreferrer nofollow" href="https://glare.zurb.com/docs/decision-map/define/collecting/techniques/surveys">Surveys & Questionnaires</a></td><td colspan="1" rowspan="1" colwidth="262">What users think, feel, and expect at scale. Works across discovery, post-task, and longitudinal tracking.</td><td colspan="1" rowspan="1" colwidth="180">Usefulness, Satisfaction, Loyalty</td></tr><tr><td colspan="1" rowspan="1"><a target="_blank" rel="noopener noreferrer nofollow" href="https://glare.zurb.com/docs/decision-map/define/collecting/techniques/eye-tracking">Eye Tracking</a></td><td colspan="1" rowspan="1" colwidth="262">Where users look, what they see first, and what they miss entirely. Reveals visual attention that click data cannot.</td><td colspan="1" rowspan="1" colwidth="180">Comprehension, Efficiency, Visual Attention</td></tr></tbody></table>

Proof in Practice

A university team was split on a navigation redesign. Meetings stalled. Everyone had a different opinion and no one had data.

They ran a First Click Test using Helio, measuring comprehension. Within hours, they saw a 14 percent usability improvement with a hamburger menu. The technique did not just produce a number — it ended the argument and put the project back in motion.

One test replaced weeks of debate. That is what a technique does when it is connected to the right metric.

Business Impact

• Techniques produce signals in days, not months, keeping projects moving.

• Metric-anchored findings give leadership something measurable to act on.

• Paired techniques surface both what happened and why, making decisions defensible.

• Lean testing prevents wasted cycles before problems compound downstream.

Quick Checklist

• Did you start with a metric, not just a method?

• Did you choose the technique that matches your mode?

• Did you pair techniques where one alone is not enough?

• Did you run lean to keep speed?

• Did you report results as signals tied to a UX metric, not raw data?

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