Opportunity

An opportunity is a gap between what users need and how well that need is met today. It points to where better work could make a real difference.

For example, new cardholders need to see what their reward points are worth, but today the dashboard only shows a points balance. That gap between the need and the current experience is the opportunity, and it's why the team has a reason to try something new on the rewards dashboard.

Why it matters

Without a clear opportunity, teams jump straight to solutions. They build features because they're interesting or because a competitor has them, and later struggle to explain what problem the work was meant to solve.

A well-stated opportunity keeps the team honest. It names the need, shows how far today's experience falls short, and gives everyone a shared picture of what "better" would look like before any ideas are on the table. It also makes it easy to compare opportunities and put effort where the gap is widest.

Start from a real user need, describe what happens today in plain terms, and check that the gap is backed by evidence rather than a feeling.

How we write one

Every opportunity is written as one sentence that names who has the need, what the need is, and what happens today:

An audience needs a need, but today the current state.

New cardholders need to see what their points are worth, but today the dashboard only shows a balance.

Writing it this way keeps the need and the shortfall side by side, so anyone can see the size of the gap without a solution getting in the way.

How it differs from similar ideas

  • A user need is one of the 20 standard needs, such as Valuable or Findable. An opportunity is the specific place where that need isn't being met today.

  • A situation describes what's happening, such as cardholders rarely opening the rewards tab. An opportunity names the unmet need behind it.

  • A hunch is a guess about why something is true or what will work, written about a concept. An opportunity is the gap that the concept, and the hunch about it, try to close.

  • A concept is a proposed solution. An opportunity is the problem space that concepts are meant to fill.

A good opportunity

  • Is grounded in one named user need

  • Says whose need it is

  • Describes today's experience in concrete terms

  • Contains no solution

  • Is backed by at least one input or situation

  • Is small enough that a team could act on it

What happens to it

  1. Spotted. Ray finds a gap in research notes, analytics or a test readout, or someone on the team names one.

  2. Grounded. It is linked to a user need and the evidence that shows the shortfall.

  3. Explored. Concepts are proposed to close it, hunches are written about those concepts, and tests begin.

  4. Addressed. A concept or initiative closes the gap, and outcomes show the need is now better met.

  5. Closed or retired. It is closed when the gap is met, or retired when new evidence shows the gap wasn't real.


For Ray

This part tells Ray how to find an opportunity in an input, such as interview notes, a research synthesis, an analytics export, a test readout or a workshop board, and how to store it.

How to find one

  1. Mark statements of shortfall. Read the input and mark every place where users need something and today's experience falls short.

  2. Find the need. Match the shortfall to one of the 20 user needs. If none fits, leave the need blank and flag it.

  3. Find the audience. Identify whose need it is, as specifically as the input allows.

  4. Find the current state. Pull out what happens today, in concrete terms. If the input only names a solution, restate the gap the solution is meant to close.

  5. Find the evidence. Note the situation, input or data that shows the gap is real.

  6. Write the sentence. Use the format: [Audience] needs [need], but today [current state].

  7. Fill the record, score it, link it and store it using the rules below.

Cues to look for

  • Gap language: "users want... but", "there's no way to", "they can't tell", "today it only"

  • Pain points and friction in interview notes and research syntheses

  • Low numbers on something users should be doing, such as 12% visiting the rewards tab

  • "How might we" statements on workshop boards, once the solution is stripped out

What doesn't count

<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>If the statement...</p></th><th colspan="1" rowspan="1"><p>Store it as</p></th></tr><tr><td colspan="1" rowspan="1"><p>Proposes a feature or design, such as "add a points progress bar"</p></td><td colspan="1" rowspan="1"><p>Concept, and restate the gap behind it as the opportunity</p></td></tr><tr><td colspan="1" rowspan="1"><p>Describes behavior without naming a need</p></td><td colspan="1" rowspan="1"><p>Situation</p></td></tr><tr><td colspan="1" rowspan="1"><p>Guesses why users behave a certain way</p></td><td colspan="1" rowspan="1"><p>Hunch</p></td></tr><tr><td colspan="1" rowspan="1"><p>Names a need with no shortfall</p></td><td colspan="1" rowspan="1"><p>User Need</p></td></tr><tr><td colspan="1" rowspan="1"><p>Asks what the team should do</p></td><td colspan="1" rowspan="1"><p>Ask</p></td></tr></tbody></table>

The record

<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 75px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Field</p></th><th colspan="1" rowspan="1"><p>What to fill in</p></th><th colspan="1" rowspan="1"><p>Values</p></th></tr><tr><td colspan="1" rowspan="1"><p>Statement</p></td><td colspan="1" rowspan="1"><p>The one-sentence opportunity</p></td><td colspan="1" rowspan="1"><p>[Audience] needs [need], but today [current state].</p></td></tr><tr><td colspan="1" rowspan="1"><p>Audience</p></td><td colspan="1" rowspan="1"><p>Whose need it is</p></td><td colspan="1" rowspan="1"><p>Link to Audience</p></td></tr><tr><td colspan="1" rowspan="1"><p>User need</p></td><td colspan="1" rowspan="1"><p>The need that grounds it</p></td><td colspan="1" rowspan="1"><p>One of the 20 user needs, linked</p></td></tr><tr><td colspan="1" rowspan="1"><p>Current state</p></td><td colspan="1" rowspan="1"><p>What happens today</p></td><td colspan="1" rowspan="1"><p>Short text</p></td></tr><tr><td colspan="1" rowspan="1"><p>Evidence</p></td><td colspan="1" rowspan="1"><p>The situation, input or data that shows the gap</p></td><td colspan="1" rowspan="1"><p>Link to Situation or Input</p></td></tr><tr><td colspan="1" rowspan="1"><p>Gap size</p></td><td colspan="1" rowspan="1"><p>How far today falls short, if measured</p></td><td colspan="1" rowspan="1"><p>Metric and value, or blank</p></td></tr><tr><td colspan="1" rowspan="1"><p>Raised by</p></td><td colspan="1" rowspan="1"><p>The person, role or skill area that named it</p></td><td colspan="1" rowspan="1"><p>Name, role or skill area</p></td></tr><tr><td colspan="1" rowspan="1"><p>Source</p></td><td colspan="1" rowspan="1"><p>The input and exact passage</p></td><td colspan="1" rowspan="1"><p>Link to Input</p></td></tr><tr><td colspan="1" rowspan="1"><p>Status</p></td><td colspan="1" rowspan="1"><p>Where it stands</p></td><td colspan="1" rowspan="1"><p>Spotted, Grounded, Explored, Addressed, Closed, Retired</p></td></tr><tr><td colspan="1" rowspan="1"><p>Confidence</p></td><td colspan="1" rowspan="1"><p>How well the gap is supported</p></td><td colspan="1" rowspan="1"><p>High, medium, low</p></td></tr></tbody></table>

New opportunities start as Spotted. An opportunity moves to Grounded only when it links to a user need and at least one piece of evidence.

Scoring confidence

Confidence measures how well the gap is supported by evidence, not how big or exciting it seems.

<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Level</p></th><th colspan="1" rowspan="1"><p>When to use it</p></th></tr><tr><td colspan="1" rowspan="1"><p>High</p></td><td colspan="1" rowspan="1"><p>Tied to a named user need, with data or repeated observations showing the shortfall</p></td></tr><tr><td colspan="1" rowspan="1"><p>Medium</p></td><td colspan="1" rowspan="1"><p>Tied to a user need, but the shortfall rests on one source or anecdotal evidence</p></td></tr><tr><td colspan="1" rowspan="1"><p>Low</p></td><td colspan="1" rowspan="1"><p>Inferred from a solution or remark, or no clear user need behind it</p></td></tr></tbody></table>

If any part of the record can't be filled from the source, leave it blank and lower confidence by one level.

Linking

  • Check for duplicates first. If an existing opportunity names the same need for the same audience, add the new source to it instead of creating another.

  • Link to the user need that grounds it and to the situation or input that shows the gap.

  • Link to the concepts proposed to close it, the hunches written about them, and the initiatives that address it.

  • Note related gaps. If two opportunities share a need but differ by audience, link them as related.

  • Note when a gap closes. Link the outcome that shows the need is met and mark the opportunity Closed.

When to store and when to ask

  • Store automatically when confidence is high.

  • Add to the review digest when confidence is medium or low, when no user need can be matched, or when it contradicts an existing opportunity.

When to flag

  • An opportunity has no user need behind it, which is a solution looking for a problem

  • An opportunity is written as a solution rather than a gap

  • A grounded opportunity has no concepts or tests linked to it after 30 days

  • A concept or initiative has no opportunity behind it

  • An opportunity is marked Closed without an outcome showing the need is met

Worked example

Input: a research synthesis deck from five new cardholder interviews, slide 7.

"Every participant could find their points balance. None could tell us what 5,000 points would get them. One said, 'It's just a number, I have no idea if that's a lot.' The dashboard shows the balance and nothing else."

What Ray finds:

  • "None could tell us what 5,000 points would get them" shows the need: seeing what points are worth, which matches Valuable (Impact).

  • "New cardholder interviews" names the audience.

  • "The dashboard shows the balance and nothing else" is the current state.

  • "It's just a number" is a clue about why, so it supports a separate Hunch that points feel abstract, linked to this opportunity.

Stored record:

<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Field</p></th><th colspan="1" rowspan="1"><p>Value</p></th></tr><tr><td colspan="1" rowspan="1"><p>Statement</p></td><td colspan="1" rowspan="1"><p>New cardholders need to see what their points are worth, but today the dashboard only shows a balance.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Audience</p></td><td colspan="1" rowspan="1"><p>Customers: new cardholders, first 90 days</p></td></tr><tr><td colspan="1" rowspan="1"><p>User need</p></td><td colspan="1" rowspan="1"><p>Valuable (Impact)</p></td></tr><tr><td colspan="1" rowspan="1"><p>Current state</p></td><td colspan="1" rowspan="1"><p>Dashboard shows a points balance only</p></td></tr><tr><td colspan="1" rowspan="1"><p>Evidence</p></td><td colspan="1" rowspan="1"><p>Situation: new cardholders rarely open the rewards tab; interview synthesis</p></td></tr><tr><td colspan="1" rowspan="1"><p>Gap size</p></td><td colspan="1" rowspan="1"><p>0 of 5 participants could say what 5,000 points buys</p></td></tr><tr><td colspan="1" rowspan="1"><p>Raised by</p></td><td colspan="1" rowspan="1"><p>Research lead (Collecting)</p></td></tr><tr><td colspan="1" rowspan="1"><p>Source</p></td><td colspan="1" rowspan="1"><p>Research synthesis deck, slide 7, October 2026</p></td></tr><tr><td colspan="1" rowspan="1"><p>Status</p></td><td colspan="1" rowspan="1"><p>Grounded</p></td></tr><tr><td colspan="1" rowspan="1"><p>Confidence</p></td><td colspan="1" rowspan="1"><p>Medium: clear need and shortfall, but from five interviews only</p></td></tr></tbody></table>

Next step: added to the review digest at medium confidence, with a prompt to link the rewards tab analytics to raise it to high.

Edge cases

  • Stated as a solution. "We need a points calculator" names a solution. Store the calculator as a Concept and ask what gap it's meant to close.

  • No need behind it. "Competitors have a rewards map, so we should too" has no user need. Store it at low confidence and flag it as a solution looking for a problem.

  • Several needs in one gap. "They can't find rewards and don't know what points are worth" is two opportunities, Findable and Valuable. Split them and link them as related.

  • The gap closes. Don't delete the opportunity. Link the outcome that shows the need is met and mark it Closed, so the history stays visible.

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
Opportunity | Glare