Identify Techniques

Identify techniques help teams get clear on what success looks like before reacting to feedback. Once the problem is understood, the conversation needs direction. Without it, people share opinions, but those opinions do not always point to the same goal.

This step keeps the review focused on what needs to change and what better actually means.

Why this matters

When outcomes are unclear, the review gets subjective. That usually shows up when:

  • Feedback is based on preference

  • People disagree with no clear way to settle it

  • Suggestions pull the conversation in different directions

  • Decisions feel uncertain or get delayed

When outcomes are clear, the conversation is easier to guide. People can judge ideas against the same goal, and decisions get easier to make.

Most feedback starts as a reaction:

  • "This feels better."

  • "I like this more."

  • "This could be clearer."

Those reactions are useful, but they are not enough on their own. The goal is to turn them into something more specific:

  • What should improve

  • What should change for the user

  • How success will show up

A good outcome names a user need, not only a feature. "Users can find their balance without help" is an outcome. "Add a balance widget" is a deliverable.

You are not solving everything yet. You are giving the conversation a clear target.

When to use these techniques

Use Identify techniques when the conversation has a problem but no clear target. That usually happens when:

  • Feedback is based on preference

  • People use words like better, clearer, or easier without defining them

  • The group disagrees but cannot settle the disagreement

  • Suggestions pile up without a shared goal

  • The team has not defined what should change for the user

The goal is to make success clear enough that feedback has something to point toward. Identify is working when the group can explain what success looks like in plain language. By the end of this step, the team should be able to say:

  • What should improve

  • Who it should improve for

  • What the user should be able to do

  • How the team will know the direction is working

This gives the review a shared target. Use the technique that matches what is happening in the room.

  • If success is unclear, define what success looks like.

  • If feedback comes as scattered suggestions, turn feedback into an outcome.

  • If feedback is too broad, ask targeted questions.

  • If too many goals are competing, align on a single priority.


Techniques

1. Define what success looks like

When success is not clearly defined, people rely on their own judgment. That often leads to different opinions and no clear direction. Defining success gives the group something to aim at. It helps everyone understand what should be different if the work succeeds.

What to watch for

  • Feedback like "this feels better" or "I like this"

  • Disagreement that never gets settled

  • Shifting ideas of what success means

What this does

  • Aligns the group on a shared goal

  • Makes feedback easier to judge

  • Supports clearer decisions

Example

"If this works, users should move through this step without hesitation."

2. Turn feedback into an outcome

Feedback often comes as suggestions. Left alone, those suggestions can pull the conversation in different directions. Turning feedback into an outcome ties it back to the goal. It shifts the conversation from what to change to why it matters.

What to watch for

  • Long lists of suggestions

  • Feedback that feels disconnected

  • Competing ideas

What this does

  • Filters noise

  • Keeps the conversation focused

  • Helps prioritize feedback

Example

"So the goal here is to make this easier to understand at first glance?"

3. Ask targeted questions

Open-ended questions tend to get open-ended feedback. People respond with whatever comes to mind. Targeted questions guide the conversation toward specific parts of the work. They help the group focus on what needs to be judged.

What to watch for

  • Broad or unfocused feedback

  • People jumping between topics

  • No clear direction

What this does

  • Improves feedback quality

  • Keeps the conversation focused

  • Reduces noise

Example

"Does this interaction make sense on mobile?"

"Would you expect to use this here?"

4. Align on a single priority

When too many things are discussed at once, the conversation spreads out and slows down. Aligning on a single priority helps the group focus on what matters most right now. It gives the conversation a clear direction.

What to watch for

  • Too many topics being discussed

  • Focus shifting during the call

  • Trouble making decisions

What this does

  • Creates focus

  • Simplifies decisions

  • Improves momentum

Example

"What's the one thing we need to get right here?"


Define what better means before you debate the work.

When success is clear, feedback has a target, disagreements are easier to settle, and decisions come faster.

Related links

Jagna Birecka

The article argues that outcomes alone don’t create direction, and that teams mistake outcome statements for strategy when they lack intent, tradeoffs, and decision logic. Use this when clarifying why outcome-driven language isn’t improving execution and when deciding how to pair outcomes with real strategic choices.

Jaime Diaz Beltran

The article explains why outcomes should not be treated as goals, arguing that outcomes are signals that inform decisions, while goals represent intent and direction. Use this when clarifying how to frame goals, outcomes, and metrics so teams don’t confuse measurement with strategy.

Tim Kastelle

Tim Kastelle says designing for outcomes means keeping target outcomes front and center through the whole project. Useful when teams stay inspired by an idea but lose sight of the result they need.

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