Navigate Techniques

Navigate techniques help teams move from discussion to a clear direction.

By this point, the group should understand the problem, know what success looks like, and have signals that show what is actually happening. The risk is that the conversation stays open. People keep exploring ideas, reacting to details, and adding input, but no clear path forms.

This step brings structure to that moment. It helps the group turn what has been discussed into a direction people can understand and support.

Why this matters

When decisions are not guided, the review can stall. That usually shows up when:

  • Conversations stay open too long

  • Ideas compete without resolution

  • Tradeoffs are unclear

  • People hesitate to commit

  • The group leaves without a clear direction

When decisions are guided well, the conversation gets more focused. The group understands what direction to take and why. At this stage, the conversation has enough information. The goal is not to gather more input. The goal is to bring the input you have together into a direction.

You are helping the group:

  • Connect what has been discussed

  • Understand what matters most

  • Make tradeoffs visible

  • Move toward a clear path

If the team already compared these options in Focus, start from that Bet. Its Use and Prefer results show which option worked and which one people chose.

You are making it easier for the right decision to form.

When to use these techniques

Use Navigate techniques when the conversation has enough information but no clear direction. That usually happens when:

  • The group keeps exploring without choosing

  • Several ideas are treated as equal

  • People hesitate after a recommendation

  • Tradeoffs are unclear

  • No one wants to close the discussion

  • The call is almost over and the direction is still soft

The goal is to help the group move from open discussion to a clear path forward. Navigate is working when the group can explain the direction and why it makes sense. By the end of this step, the team should be able to say:

  • What direction is recommended

  • What tradeoffs are being made

  • Which options are no longer being considered

  • Why this path fits the problem, outcome, and signals

  • Whether the group agrees enough to move forward

This gives the review a clear decision path. Use the technique that matches what is happening in the room.

  • If the conversation is staying open, state a clear recommendation.

  • If people hesitate, frame the tradeoffs.

  • If too many ideas are competing, narrow the options.

  • If agreement is assumed, check for agreement.


Techniques

1. State a clear recommendation

Without a recommendation, conversations tend to stay open. People keep exploring ideas without moving toward a decision.

A recommendation gives the group something to respond to. It becomes the focal point of the discussion. This shifts the conversation from reacting to many ideas to reacting to one direction.

What to watch for

  • Long discussions without a clear path

  • Several ideas being treated as equal

  • Uncertainty at the end of the call

What this does

  • Creates direction

  • Focuses the group

  • Makes decisions easier to form

Example

"Based on what we've seen, we recommend moving forward with this approach."

2. Frame the tradeoffs

Every decision involves tradeoffs, even when no one says them out loud. When tradeoffs are not clear, people may hesitate or raise concerns later. This can slow progress or reopen the conversation.

Framing the tradeoffs makes the decision more transparent. It shows what is being prioritized and what is being given up.

What to watch for

  • Hesitation after a recommendation

  • Concerns raised late

  • Unclear priorities

What this does

  • Builds trust

  • Clarifies priorities

  • Supports stronger decisions

Example

"This simplifies the experience, but reduces flexibility here. That's the trade we're making."

3. Narrow the options

Too many options slow decision-making. When everything is still on the table, it gets harder to judge and compare. The conversation spreads out and loses focus.

Narrowing the options helps the group concentrate on the strongest directions and move toward a choice.

What to watch for

  • Too many ideas being discussed

  • Trouble comparing options

  • Stalled decisions

What this does

  • Simplifies the conversation

  • Improves focus

  • Speeds up decisions

Example

"Between these two directions, which better solves the problem we outlined?"

4. Check for agreement

Agreement is often assumed but not confirmed. People may leave with different ideas of what was decided. This leads to confusion or rework later.

Checking for agreement makes alignment visible. It makes sure the group is moving forward together.

What to watch for

  • Silence after a recommendation

  • Unclear reactions from the group

  • Decisions being revisited later

What this does

  • Confirms alignment

  • Prevents rework

  • Strengthens decisions

Example

"Does this direction make sense to move forward with?"


Help the conversation move toward a clear direction.

When decisions are guided well, the group stops exploring and starts aligning. The work gets clearer, and the next step gets easier to define.

Related links

Mike Zawitkowski

Mike Zawitkowski warns that picking one metric can become a trap and cause bad decisions. Useful when a team is rallying around a single metric and ignoring tradeoffs.

Ioana Teleanu

Podcast and post on when teams really should skip UX research, and why pressure or budget alone is not a good reason. Useful when a team is debating whether to skip research and needs a balanced view from a UX leader.

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.

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