# Situations

Find recurring behaviors and friction shaping decisions.Most teams collect signals. Few understand the conditions that created them.A metric might show high drop-off, rising effort, or weak retention. But a number alone cannot tell you why. It cannot tell you what was happening around the user when the friction appeared, what they were trying to accomplish, what forces were working against them, or why the same breakdown keeps showing up across different sessions, audiences, and product areas.That is what Situations does.Situations is the fourth block in Define. It sits after User Needs, Audience, and Collecting, and it is where those three converge. User Needs names what people are trying to accomplish. Audience identifies whose signals carry weight. Collecting gathers the evidence and hands over a Source Map: what evidence exists, how far to trust each source, and where the gaps are. Situations reads that evidence for recurring conditions and names them, so teams have stable context to design against.What Situations answersEach facet ends in a block that judges one quality, as people experience it. Situations closes Define, and the quality it judges iscredibility: "this is really what happens to people like me."Question it answersWhat it checksWhat it hands upIs it real, recurring, and seen in behavior?Source spread, lenses that agree, the behavior behind the text, and a rung on the confidence ladderA credible situation, ready for MeasureSituations is accountable forNeedsignals: evidence that a real need shows up in real conditions. A situation is named from recurring Need signals. It is synthesis, not a signal itself. Use, Prefer, and Adopt signals belong to Findings, Bets, and Results.Three checks and a ladderCheckWhat it asksSource spreadDoes the condition show up in more than one kind of source?Lenses that agreeDo at least two of the four lenses point to the same condition?Behavior behind the textIs 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 the situation is played back to people in it, do they recognize it?What This Block CoversSituations is organized into eight sections, each with a specific job:SectionWhat It DoesOverviewExplains what Situations is, the quality it judges, and how it connects to User Needs, Audience, and Collecting.TechniquesCovers the four lenses for reading Need signals for situations: By Type, By Time, By Stage, and By Engagement.PlaybookProvides the process for naming a situation and checking its credibility, with inputs, prompts, and outputs.ReferencesSituation types, signal-to-situation mapping, situations by product context, and the confidence ladder.ExamplesWorked situations with their ladder rung, including near-misses and common traps.DecisionsHelps teams recognize when a situation is credible enough to carry into Measure.Agent OperationsDefines how AI Skills read Need signals, name situations from them, rate confidence, and route the next step.WorksheetA fill-in page for one situation: the four parts, the Need signals by source and lens, the rung, and the credibility check.What Is a Situation?A situation is a specific set of circumstances that gives behavior its meaning. It captures the conditions surrounding what a user does, not just the action itself.Behavior does not happen in isolation. Every action is shaped by what triggered it, what the person is trying to accomplish, what stands in their way, what forces are working around them, and what success or failure means in that moment. Strip those conditions away, and a metric tells you what happened. Keep them, and you begin to understand why.The Four Parts of a SituationElementWhat It CapturesWhat triggered itThe condition, pressure, or goal that set the situation in motion.What they are trying to doThe progress the user is seeking in this specific context.What stands in their wayThe friction, uncertainty, or constraint that shapes behavior.What success means hereHow the user defines resolution, and what failure costs them.When the same four-part pattern shows up across different users, sessions, and audiences, you can name a situation. One data point is an observation. A situation is named from recurring Need signals.Situations and User Needs Are Not the Same ThingUser Needs names what people are trying to accomplish at a category level: Basics, Trust, Personal, Impact, Feelings. Those categories are stable and broadly applicable.Situations are one level more concrete. They capture how a need shows up inside a specific context. The same need can produce different situations depending on who the person is, what they are dealing with, and where they are in the experience.A physician who needs to learn and a product manager who needs to learn share a need. But their situations differ, shaped by different pressures, workflows, relationships, and stakes. Designing for the need alone misses that.User Needs defines the category. Situations define the context inside it.Situations vs Jobs to Be DoneJobs to Be Done focuses on the need itself: the job a person is trying to get done, stated as motivation and intended outcome. It maps closely to the User Needs block.JTBD treats the circumstance as background. Situations inverts that priority. A need is always shaped by the forces around it: environment, relationships, culture, constraints, habits, and pressure. Strip those away and a job statement is true in the abstract but often too thin to design against.In practice, JTBD helps you write User Needs. Situations comes after you collect evidence and see which conditions keep producing the same behaviors. A situation is a job statement made visible through repeated, real Need signals.How Patterns Become SituationsOne user hesitating during onboarding is an observation. Ten users hesitating at the same moment, across different sessions and audience segments, is a situation. The repetition, seen in behavior and across sources, is what makes it credible.This is why Situations sits after Collecting. You cannot name a situation from instinct alone. You need evidence from the right people, and a Source Map that says how far to trust each source. When those signals converge, recurring conditions become visible: the same friction, the same hesitation point, the same place where confidence drops.Patterns are the evidence. Situations are the interpretation.Why Context Shapes What Signals MeanThe same behavior can mean different things depending on the situation around it. Long session duration might signal engagement, confusion, comparison, or overload. A drop in task completion from trial users points toward onboarding clarity. The same drop from habitual users points toward a workflow regression.Without situational context, teams optimize for the wrong thing. They celebrate completion rates while confidence quietly drops. They fix the symptom and leave the condition intact.In PracticeA pharmaceutical company had run the same market research on physicians for seven years. Engagement looked reasonable and the metrics were stable, but nothing was moving.A team took the existing data and mapped the forces shaping how physicians showed up in different moments. Three distinct situations emerged, each with different motivations, friction points, and signals about what physicians valued.One of those situations consumed a third of the commercial budget. Physicians in it had no interest in engaging, and the company had no access. Once the situation was visible, the investment decision changed.The data was always there. What was missing was the situational frame that gave it meaning.Business ImpactShared situation definitions align teams around what is actually happening, reducing debate and speeding decisions.Situational context makes metrics meaningful, connecting what was measured to why it matters.Recurring situations surface earlier, before they scale into product or operational problems.Teams earn more trust when they can explain not just what users did, but the conditions that produced it.Situations is where Define closes. It turns the evidence gathered in User Needs, Audience, and Collecting into credible, shared context. Measure uses that context to test ideas worth testing, and Focus uses it to choose the work worth doing.Where Situations Sits in DefineBlockWhat It Focuses OnUser NeedsThe motivations, goals, and expectations that drive behavior.AudienceThe people and contexts you learn from, and how much to trust each source.CollectingLearning openly before a hunch, through four lenses (Navigation, Task, Behavior, and Feedback), and mapping how far each source can be trusted.SituationsNaming recurring conditions from Need signals, and checking that they are credible.The first three blocks give you the people, the need, and a Source Map of the evidence. Situations interprets it. Without that context, signals remain isolated data points.AI PromptThis prompt helps you turn scattered evidence into one named situation your team can design against.Start with the evidence you collected: analytics, recordings, tickets, interviews, or a Source Map. It guides you to:Read the evidence for conditions that keep coming backName the situation in four parts: what triggered it, what people are trying to do, what stands in their way, and what success meansRun the three checks: source spread, lenses that agree, and behavior behind the textPlace it on the confidence ladder and plan the credibility checkYou'll end with a named situation and its rung on the ladder. At Recurring, it is ready for Measure.Use this at the end of Define, before anyone writes hunches.AI SkillsThe Situations skill file teaches your AI to name recurring conditions from Need signals and check that they are credible.Load it when you have plenty of signals but no clear story, or when the team needs to know whether a belief about users is real. It gives your AI:The four parts of a situationThe three checks and the confidence ladder, from Weak to ValidatedHow Situations differs from User Needs and Jobs to Be DoneWhen a situation is ready to hand to MeasureDownload the skill file below to use the full Situations framework with your AI assistant.