A situation is the team's agreed reading of what's happening. It's built from inputs, and it describes how people are behaving and what that leads to.
For example, the analytics export shows only 12% of new SecondBank cardholders visit the rewards tab in their first month. The situation is: new cardholders rarely open the rewards tab, so earned points go unused. That reading sets the context for who the team studies and which user needs matter.
Why it matters
When the situation isn't written down, every person in the room carries a different version of the problem. Design thinks it's a layout issue, marketing thinks it's awareness, and leadership thinks it's the rewards program itself. Work splits before it starts.
A written situation gives everyone the same starting point. It says what's happening and what it costs, so the team can agree on the audience to study, the need to address, and whether the problem is worth solving at all.
Describe the behavior and its effect in plain words, tie it to the inputs it came from, and get the team to accept it as the working reading.
How we write one
Every situation is written as one sentence that names who, what they're doing, and what it leads to:
An audience is a behavior, which has an effect.
New cardholders are rarely opening the rewards tab, which leaves earned points unused.
Pairing the behavior with its effect keeps the situation grounded in what people actually do, and shows why it matters without jumping to a cause or a fix.
How it differs from similar ideas
-
An input is the raw material, such as an analytics export. A situation is the reading built from it.
-
An observation is one thing seen or heard during a test. A situation is a broader reading of what's happening, usually built from several inputs.
-
An assumption is a conclusion drawn from data and treated as true before anyone checks it. A situation describes the behavior itself, which the team has accepted as the working reading.
-
A hunch explains why something is happening. A situation describes what is happening and leaves the why open.
A good situation
-
Names a specific audience
-
Describes behavior, not a cause
-
States the effect
-
Rests on at least one input
-
Avoids proposing a solution
-
Has been accepted by the team as the working reading
What happens to it
-
Proposed. Ray drafts it from an input, or someone describes it in a meeting or ask.
-
Accepted. The team agrees it's an accurate reading, and it becomes the working context.
-
Active. It shapes the audience, user needs and asks the team works on.
-
Changed. New inputs show the behavior has shifted, so a new situation is stored and linked.
-
Resolved or retired. Outcomes show the behavior has changed, or the situation no longer matters.
For Ray
This part tells Ray how to build a situation from inputs, such as an analytics export, a research report, a support ticket summary or a meeting transcript, and how to store it.
How to find one
-
Mark descriptions of behavior. Read the input and mark statements about what people are doing, or not doing, and what follows from it.
-
Find the audience. Identify whose behavior it is. Use the narrowest group the input supports.
-
Find the behavior. State what people do in plain words. If the input gives a cause, set the cause aside as a possible Hunch or Assumption.
-
Find the effect. Look for what the behavior leads to, such as lost value, cost or missed goals. If no effect is given, leave it blank.
-
Gather supporting inputs. Link every input that backs the reading, and note any input that contradicts it.
-
Check whether it's accepted. If the team has agreed on this reading, mark it Accepted. Otherwise mark it Proposed.
-
Write the sentence. Use the format: [Audience] is [behavior], which [effect].
-
Fill the record, score it, link it and store it using the rules below.
Cues to look for
-
Behavior language: "users rarely", "most people don't", "customers keep", "drop-off at"
-
Rates and counts tied to an action, such as visits, completions or abandonment
-
Problem statements in briefs and kickoff decks
-
Effects: "which means", "so we lose", "leaving", "as a result"
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>Explains why the behavior happens, based on data</p></td><td colspan="1" rowspan="1"><p>Assumption</p></td></tr><tr><td colspan="1" rowspan="1"><p>Explains why the behavior happens, based on intuition</p></td><td colspan="1" rowspan="1"><p>Hunch</p></td></tr><tr><td colspan="1" rowspan="1"><p>Reports one thing seen or heard in a test session</p></td><td colspan="1" rowspan="1"><p>Observation</p></td></tr><tr><td colspan="1" rowspan="1"><p>Is a raw number with no reading attached</p></td><td colspan="1" rowspan="1"><p>Benchmark or UX Metric, and propose a situation from it</p></td></tr><tr><td colspan="1" rowspan="1"><p>Says what users need</p></td><td colspan="1" rowspan="1"><p>User Need</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 situation</p></td><td colspan="1" rowspan="1"><p>[Audience] is [behavior], which [effect].</p></td></tr><tr><td colspan="1" rowspan="1"><p>Audience</p></td><td colspan="1" rowspan="1"><p>Whose behavior it is</p></td><td colspan="1" rowspan="1"><p>Link to Audience</p></td></tr><tr><td colspan="1" rowspan="1"><p>Behavior</p></td><td colspan="1" rowspan="1"><p>What people are doing or not doing</p></td><td colspan="1" rowspan="1"><p>Short text</p></td></tr><tr><td colspan="1" rowspan="1"><p>Effect</p></td><td colspan="1" rowspan="1"><p>What the behavior leads to</p></td><td colspan="1" rowspan="1"><p>Short text, or blank</p></td></tr><tr><td colspan="1" rowspan="1"><p>Supporting inputs</p></td><td colspan="1" rowspan="1"><p>Inputs that back the reading</p></td><td colspan="1" rowspan="1"><p>Links to Input</p></td></tr><tr><td colspan="1" rowspan="1"><p>Contradicting inputs</p></td><td colspan="1" rowspan="1"><p>Inputs that cut against it</p></td><td colspan="1" rowspan="1"><p>Links to Input, or blank</p></td></tr><tr><td colspan="1" rowspan="1"><p>User needs</p></td><td colspan="1" rowspan="1"><p>Needs this situation points to</p></td><td colspan="1" rowspan="1"><p>Links to User Need</p></td></tr><tr><td colspan="1" rowspan="1"><p>Raised by</p></td><td colspan="1" rowspan="1"><p>The person, role or Ray, and skill area</p></td><td colspan="1" rowspan="1"><p>Name or role, skill area</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, Accepted, Active, Changed, Resolved, Retired</p></td></tr><tr><td colspan="1" rowspan="1"><p>Confidence</p></td><td colspan="1" rowspan="1"><p>How well the inputs support it</p></td><td colspan="1" rowspan="1"><p>High, medium, low</p></td></tr></tbody></table>
New situations start as Proposed. Only the team can move one to Accepted; Ray never accepts its own reading.
Scoring confidence
Confidence measures how well the inputs support the reading, not how serious the situation sounds.
<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>Backed by behavioral data from customers or participants, with no contradicting inputs</p></td></tr><tr><td colspan="1" rowspan="1"><p>Medium</p></td><td colspan="1" rowspan="1"><p>Backed by one input, or by opinion from the team or stakeholders, or with minor contradictions</p></td></tr><tr><td colspan="1" rowspan="1"><p>Low</p></td><td colspan="1" rowspan="1"><p>Described in a meeting or ask with no input behind it, or contradicted by other inputs</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 situation describes the same behavior for the same audience, add the new input to it instead of creating another.
-
Link to every input that supports or contradicts it.
-
Link to the audience whose behavior it describes, and to the user needs it points to.
-
Link to the asks that point to it.
-
Note changes. When new inputs show the behavior has shifted, store a new situation, link the two, and mark the old one Changed.
When to store and when to ask
-
Store automatically as Proposed when confidence is high.
-
Add to the review digest when confidence is medium or low, when it contradicts an accepted situation, or when it's ready for the team to accept.
When to flag
-
An ask is routed past Define with no accepted situation
-
A situation rests only on internal voices
-
A situation has contradicting inputs that nobody has reviewed
-
A situation has been Proposed for 30 days without being accepted or rejected
-
A situation has no user need linked to it
Worked example
Input: a research readout deck, slide 3, from the product researcher.
"Engagement gap: only 12% of new cardholders visit the rewards tab in their first month. Most new cardholders end their first quarter with points they've never looked at. We think they don't realize what points are worth."
What Ray finds:
-
"New cardholders" is the audience.
-
"Only 12%... visit the rewards tab" is the behavior: they rarely open it.
-
"Points they've never looked at" is the effect: earned points go unused.
-
"We think they don't realize what points are worth" is a cause based on intuition, so it becomes a separate Hunch, linked to this situation.
-
The deck cites the October analytics export, so Ray links it as a supporting input.
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 are rarely opening the rewards tab, which leaves earned points unused.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Audience</p></td><td colspan="1" rowspan="1"><p>Customers: new cardholders, first 30 days</p></td></tr><tr><td colspan="1" rowspan="1"><p>Behavior</p></td><td colspan="1" rowspan="1"><p>Rarely open the rewards tab (12% in first month)</p></td></tr><tr><td colspan="1" rowspan="1"><p>Effect</p></td><td colspan="1" rowspan="1"><p>Earned points go unused</p></td></tr><tr><td colspan="1" rowspan="1"><p>Supporting inputs</p></td><td colspan="1" rowspan="1"><p>Research readout deck, slide 3; analytics export, October 2026</p></td></tr><tr><td colspan="1" rowspan="1"><p>Contradicting inputs</p></td><td colspan="1" rowspan="1"><p>None</p></td></tr><tr><td colspan="1" rowspan="1"><p>User needs</p></td><td colspan="1" rowspan="1"><p>Findable (Basics); Valuable (Impact)</p></td></tr><tr><td colspan="1" rowspan="1"><p>Raised by</p></td><td colspan="1" rowspan="1"><p>Product researcher, Research</p></td></tr><tr><td colspan="1" rowspan="1"><p>Status</p></td><td colspan="1" rowspan="1"><p>Proposed</p></td></tr><tr><td colspan="1" rowspan="1"><p>Confidence</p></td><td colspan="1" rowspan="1"><p>High: backed by behavioral analytics from customers, no contradictions</p></td></tr></tbody></table>
Next step: stored automatically as Proposed and added to the digest for the team to accept; once accepted, it answers the Define ask.
Edge cases
-
Cause dressed as behavior. "Cardholders don't know rewards exist" sounds like a situation but explains why. Store it as an Assumption and keep the situation to what people do.
-
Several audiences. If behavior differs by group, such as new versus long-time cardholders, store separate situations.
-
Only internal voices. A situation described only by the team stays at medium confidence or lower until customer or participant data backs it.
-
Behavior shifts. Don't edit an accepted situation. Store the new reading, link it as a change, and flag decisions still tied to the old one.