A concept is a proposed idea the team can show and test. It's the first block in Measure: something concrete enough that people can react to it, which hunches are then written about and tests are run against.
For example, new cardholders can't see what their points are worth. The team proposes a concept: a progress bar on the home screen that shows how close each cardholder is to their next reward. The hunch that points feel abstract is written about this concept, and now there's something to put in front of people and measure.
Why it matters
Ideas are cheap, and teams usually have more of them than they can test. Without a clear record, concepts pile up in Figma files and slide decks, nobody remembers which hunch each one came from, and the team ends up arguing about taste instead of evidence.
Writing concepts down keeps them connected. Each one traces back to an opportunity, carries the hunches written about it, fits within known constraints, and moves forward based on what tests show. When findings come in, the concept gets refined rather than replaced on a whim.
Name the concept in plain words, say what it does and for whom, and check that a real opportunity sits behind it and at least one hunch is written about it before testing begins.
How we write one
Every concept is written as one sentence that names it, says what it does, and who it's for:
A name**:** what it does for an audience.
Points progress bar: shows how close each cardholder is to their next reward on the home screen, for new cardholders.
Writing it this way keeps the concept short enough to compare against others, and naming the audience makes it clear who should test it.
How it differs from similar ideas
-
A recommendation is a suggested next action that comes out of testing, such as showing point value in dollars. A concept is the idea being tested.
-
An initiative is a larger body of work in Focus, started from signals. A concept is a single idea shaped and tested during Measure.
-
A hunch is a belief written about a concept, with the questions that would prove or kill it. The concept comes first, in the first block of Measure; the hunch says what the team expects people to do with it.
-
An opportunity is the gap. A concept is one proposed way to close it.
A good concept
-
Has a short, clear name
-
Says what it does in plain words
-
Names who it's for
-
Traces back to an opportunity, with at least one hunch written about it
-
Fits within every active constraint
-
Can be shown to people and tested
What happens to it
-
Proposed. Someone sketches or describes it, or Ray finds it in a design file, deck or critique note.
-
Shaped. Hunches are written about it, constraints give it form, and it's ready to put in front of people.
-
In test. It's being evaluated through a test and its test questions.
-
Refined. Findings feed back into it through component building in Figma, and it's tested again if needed.
-
Advanced or shelved. It moves forward into an initiative or bet, or it's shelved with the findings that explain why.
For Ray
This part tells Ray how to find a concept in an input, such as a Figma file, a design critique transcript, a concept deck, a workshop board or a test readout, and how to store it.
How to find one
-
Mark proposed ideas. Read the input and mark every specific idea for something to build, show or change.
-
Name it. Use the team's name if one is given; otherwise write a short, descriptive name.
-
Find what it does. Describe what it does for the user in one plain phrase.
-
Find the audience. Identify who it's for.
-
Trace its origin. Link the opportunity behind it and any hunches written about it. If neither exists, flag the concept.
-
Check constraints. Check it against every active constraint and note any it breaks.
-
Write the sentence. Use the format: [Name]: [what it does] for [audience].
-
Fill the record, score it, link it and store it using the rules below.
Cues to look for
-
Idea language: "what if we", "one option is", "here's a direction", "we mocked up"
-
Named frames, prototypes and variants in Figma files
-
Concept slides with a sketch and a short description
-
Sticky notes grouped as solutions on workshop boards
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>Suggests a next action based on test results</p></td><td colspan="1" rowspan="1"><p>Recommendation</p></td></tr><tr><td colspan="1" rowspan="1"><p>Describes a broad body of work with a timeframe</p></td><td colspan="1" rowspan="1"><p>Initiative</p></td></tr><tr><td colspan="1" rowspan="1"><p>States a belief about 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>Describes the gap without proposing anything</p></td><td colspan="1" rowspan="1"><p>Opportunity</p></td></tr><tr><td colspan="1" rowspan="1"><p>Commits product or marketing to a change across workflows</p></td><td colspan="1" rowspan="1"><p>Bet</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 concept</p></td><td colspan="1" rowspan="1"><p>[Name]: [what it does] for [audience].</p></td></tr><tr><td colspan="1" rowspan="1"><p>Name</p></td><td colspan="1" rowspan="1"><p>The short name</p></td><td colspan="1" rowspan="1"><p>Short text</p></td></tr><tr><td colspan="1" rowspan="1"><p>What it does</p></td><td colspan="1" rowspan="1"><p>What it does for the user</p></td><td colspan="1" rowspan="1"><p>Short text</p></td></tr><tr><td colspan="1" rowspan="1"><p>Audience</p></td><td colspan="1" rowspan="1"><p>Who it's for</p></td><td colspan="1" rowspan="1"><p>Link to Audience</p></td></tr><tr><td colspan="1" rowspan="1"><p>Hunch</p></td><td colspan="1" rowspan="1"><p>The hunches written about it</p></td><td colspan="1" rowspan="1"><p>Links to Hunch</p></td></tr><tr><td colspan="1" rowspan="1"><p>Opportunity</p></td><td colspan="1" rowspan="1"><p>The gap it tries to close</p></td><td colspan="1" rowspan="1"><p>Link to Opportunity</p></td></tr><tr><td colspan="1" rowspan="1"><p>Constraints</p></td><td colspan="1" rowspan="1"><p>Limits it must fit within</p></td><td colspan="1" rowspan="1"><p>Links to Constraint</p></td></tr><tr><td colspan="1" rowspan="1"><p>Tests</p></td><td colspan="1" rowspan="1"><p>Tests that shape or evaluate it</p></td><td colspan="1" rowspan="1"><p>Links to Test</p></td></tr><tr><td colspan="1" rowspan="1"><p>Design file</p></td><td colspan="1" rowspan="1"><p>Where it lives</p></td><td colspan="1" rowspan="1"><p>Figma link, or blank</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>Proposed, Shaped, In test, Refined, Advanced, Shelved</p></td></tr><tr><td colspan="1" rowspan="1"><p>Confidence</p></td><td colspan="1" rowspan="1"><p>How clearly it was described and traced</p></td><td colspan="1" rowspan="1"><p>High, medium, low</p></td></tr></tbody></table>
New concepts start as Proposed. A concept moves to Shaped only when it links to a hunch or opportunity and has been checked against active constraints.
Scoring confidence
Confidence measures how clearly the concept was described and how well it traces back to a hunch and opportunity, not how promising it looks.
<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>Clearly described or shown, with a named audience and a linked hunch and opportunity</p></td></tr><tr><td colspan="1" rowspan="1"><p>Medium</p></td><td colspan="1" rowspan="1"><p>Clearly described, but the audience, hunch or opportunity is missing</p></td></tr><tr><td colspan="1" rowspan="1"><p>Low</p></td><td colspan="1" rowspan="1"><p>Mentioned in passing, or Ray had to infer what it does</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 concept does the same thing for the same audience, add the new source to it instead of creating another, even if the name differs.
-
Link to the opportunity behind it and the hunches written about it, and its source input.
-
Link to the constraints that limit it and the tests that shape and evaluate it.
-
Link to findings. When a round of testing ends, link the findings and note how they refined the concept.
-
Note variants. If a concept splits into versions, such as two progress bar designs, store each as its own concept and link them as variants.
When to store and when to ask
-
Store automatically when confidence is high and it breaks no active constraint.
-
Add to the review digest when confidence is medium or low, when no hunch or opportunity is behind it, or when it breaks a constraint.
When to flag
-
A concept has no hunch or opportunity behind it
-
A concept breaks an active constraint
-
A concept is In test but its test has no expected result
-
A concept was advanced without findings to support it
-
A concept still depends on a hunch that was contradicted
Worked example
Input: a concept review deck from the rewards design team, slide 4.
"Direction B: Points progress bar. A bar on the home screen shows how close you are to your next reward, like '3,200 of 5,000 points to a $50 statement credit.' Built inside the existing card component. Aimed at cardholders in their first 90 days. Responds to our hunch that points feel abstract."
What Ray finds:
-
"Points progress bar" is the name, and "shows how close you are to your next reward" is what it does.
-
"Cardholders in their first 90 days" is the audience.
-
"Responds to our hunch that points feel abstract" links the abstract-points hunch to it, and the concept to the point value opportunity it tries to close.
-
"Built inside the existing card component" shows it fits the Q1 release freeze constraint.
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>Points progress bar: shows how close each cardholder is to their next reward on the home screen, for new cardholders.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Name</p></td><td colspan="1" rowspan="1"><p>Points progress bar</p></td></tr><tr><td colspan="1" rowspan="1"><p>What it does</p></td><td colspan="1" rowspan="1"><p>Shows progress toward the next reward on the home screen</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>Hunch</p></td><td colspan="1" rowspan="1"><p>We think people ignore rewards because points feel abstract.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Opportunity</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>Constraints</p></td><td colspan="1" rowspan="1"><p>Concepts must reuse the existing card component because of the Q1 release freeze.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Tests</p></td><td colspan="1" rowspan="1"><p>Abstract-points concept test</p></td></tr><tr><td colspan="1" rowspan="1"><p>Design file</p></td><td colspan="1" rowspan="1"><p>Figma: Rewards / Direction B</p></td></tr><tr><td colspan="1" rowspan="1"><p>Source</p></td><td colspan="1" rowspan="1"><p>Concept review deck, slide 4, October 2026</p></td></tr><tr><td colspan="1" rowspan="1"><p>Status</p></td><td colspan="1" rowspan="1"><p>Shaped</p></td></tr><tr><td colspan="1" rowspan="1"><p>Confidence</p></td><td colspan="1" rowspan="1"><p>High: clearly described, with audience, hunch and opportunity linked</p></td></tr></tbody></table>
Next step: stored automatically and linked to the planned concept test; it moves to In test when sessions begin.
Edge cases
-
No hunch behind it. "Let's add confetti when people redeem" has no hunch or opportunity. Store it at low confidence, flag it, and ask what belief it rests on.
-
Called a recommendation. "We recommend a progress bar" before any test has run is a concept. It only counts as a Recommendation when it comes out of test evidence.
-
Too big to test. "Rebuild the whole rewards experience" is closer to an Initiative. Store it as one and ask for the concepts inside it.
-
Refined after findings. Don't overwrite the concept. Update its status to Refined, link the findings, and keep the earlier version in the design file history.