Define: Situations

# Situations AI Skill Define Area · Situations Block · Decision Map · Oct 23, 2026 (v1.0) --- ## 1. What the Skill Does The Situations skill helps teams name the recurring conditions behind what users do. It is the last block in the Define area of Glare's Decision Map, where User Needs, Audience, and Collecting come together. Situations judge **credibility**: is this really what happens to people like them? They own **Need** signals, which show that a real need shows up in real conditions. A situation is named from recurring Need signals; it is synthesis, not a signal on its own. Every situation has four parts. | Part | What it captures | |---|---| | What triggered it | The condition, pressure, or goal that set the situation in motion | | What they are trying to do | The progress the user wants in this context | | What stands in their way | The friction, uncertainty, or constraint that shapes behavior | | What success means here | How the user defines success, and what failure costs them | User Needs names the category, such as Findable. A situation is one level more concrete: how that need shows up for specific people, in a specific moment. ### The Three Checks and the Ladder | Check | What it asks | |---|---| | Source spread | Does the condition show up in more than one kind of source? | | Lenses that agree | Do at least two of the four lenses point to the same condition? | | Behavior behind the text | Is there something people did, not only something they said? | The checks place a situation on the confidence ladder: Weak, Possible, Emerging, Recurring, or Validated. A situation goes to Measure at Recurring. The last check is credibility itself: when you play the situation back to people in it, do they recognize it? One data point is an observation; never name a situation from a single lens or source. ## 2. Business Benefit A metric says what happened; a situation says why. The same drop in completion means one thing for trial users and another for habitual users. Without the situation, teams fix the symptom and leave the condition in place. This helps teams: - give metrics the context that makes them meaningful - align teams on what is actually happening, with less debate - spot recurring problems before they scale - hand Measure a credible problem worth writing hunches about ## 3. Skill Output When used correctly, the skill produces a named situation with its rung on the ladder. The example below shows how this works for a mobile banking dashboard. | Field | Example Output (Mobile Banking Dashboard) | |---|---| | Situation | The quick balance check | | What Triggered It | About to make a purchase or pay a bill, often between other tasks | | What They Are Trying to Do | Confirm how much money they have, in seconds | | What Stands in Their Way | Promo cards above the balance; extra scrolling on a small screen | | What Success Means Here | Seeing the balance at a glance. Failure means leaving the app, guessing, or calling support. | | Need Signals | Analytics: 38% of home screen sessions end without an action (behavior). Recordings: scrolling past promos (behavior). Tickets: "where did my balance go?" (said). All tagged Need | | Checks | Three kinds of source; two lenses agree; behavior behind the text | | Rung | Recurring: ready for Measure | | Credibility Check | Play it back to five habitual users before writing hunches | | Failure Mode to Watch | Naming the situation from support tickets alone. That is one source and only what people said. | | Next Step Handoff | → glare-measure-hunches to write hunches about concepts that address this situation | ## 4. Prompt Strategies The prompts below show different ways to use this skill. Each example uses a mobile banking dashboard update. ### Prompt 1: Pattern Entry: Name the situation *"We have analytics, session recordings, and support tickets about our mobile banking home screen. Using the glare-define-situations skill, read them for recurring conditions, name the situation with its four parts, and place it on the confidence ladder."* **Why this works:** It turns scattered evidence into one named condition the team can design against. **Best for:** - teams with lots of signals and no clear story - closing out Define ### Prompt 2: Credibility Entry: Is this situation real? *"Our team believes habitual mobile banking users struggle to find their balance. Using glare-define-situations, run the three checks, tell us which rung this is on, and what evidence would move it to Recurring."* **Why this works:** It tests a belief about users against source spread, lenses, and behavior before Measure builds on it. **Best for:** - stakeholder beliefs about users - deciding whether Define is done ### Prompt 3: Split Entry: Same need, different situations *"Both habitual users and new users struggle with our mobile banking home screen. Using glare-define-situations, tell us whether this is one situation or two, and how the four parts differ for each group."* **Why this works:** The same need can produce different situations. Splitting them keeps Measure from testing one fix for two problems. **Best for:** - products with very different user groups - mixed results across segments --- *Glare Framework · glare-define-situations · Define Area. Handoffs: glare-define-collecting (more evidence) · glare-define-user-needs · glare-define-audience · glare-measure-hunches · glare-measure-concepts · glare-design-signals*