# User Needs AI Skill Define Area · User Needs Block · Decision Map · Oct 23, 2026 (v1.1) --- ## 1. What the Skill Does The User Needs skill helps teams name what users are actually trying to accomplish, and where the experience starts to break down, before anyone proposes a solution. It is the first block in the Define area of Glare's Decision Map, followed by Audience, Collecting, and Situations. Needs are rarely stated outright. They show up in repeated behavior, hesitation, confusion, workarounds, and recurring friction. The skill sorts what the team is seeing into five layers and 20 needs. | Layer | Focus | User Needs | |---|---|---| | Basics | Foundational usability and access | Useful, Usable, Findable, Accessible | | Trust | Reliability and confidence | Credible, Secure, Reliable, Intuitive | | Personal | Relevance and context | Inclusive, Adaptable, Connected, Insightful | | Impact | Progress and meaningful outcomes | Valuable, Sustainable, Efficient, Scalable | | Feelings | Emotion and long-term connection | Desirable, Delightful, Engaging, Empowering | The layers build on each other: foundational needs usually come before emotional ones. They are not a rigid sequence, though. Most experiences have several overlapping needs at once. ### The Say-Do Rule What users say is not always what they need. If users ask for something but don't act on it, it is probably a want, not a need. Check every stated need against what people do. For example, users say they want a simpler layout, but recordings show they leave when they can't find their balance. The need is Findable, not a new look. ## 2. Business Benefit Teams often have interviews, tickets, analytics, and opinions, but no shared way to read them. Named needs give everyone the same reference point, so the team fixes the real problem instead of the loudest one. This helps teams: - turn scattered feedback into a few clear needs - separate needs from wants before building - spot foundational gaps before polishing higher layers - tie each need to the UX metrics that would show it improving - give Measure, Focus, and Lead the same starting point ## 3. Skill Output When used correctly, the skill produces a needs brief. The example below shows how this works for a mobile banking dashboard. | Field | Example Output (Mobile Banking Dashboard) | |---|---| | Layer and Need | Basics: Findable (primary); Trust: Credible (watch) | | Need Statement | Habitual users need to see their balance and recent transactions at a glance, so they can check their money without hunting for it | | Evidence | Session recordings show users scrolling past promo cards; support tickets ask where the balance went after the last update | | Say vs. Do | Users ask for a "simpler layout"; behavior shows the gap is finding the balance, not the look | | UX Metrics | Success and Comprehension (leading); sessions ending without an action (lagging) | | Failure Mode to Watch | Jumping to Feelings, such as animations or delight, while a Basics need is still failing | | Next Step Handoff | → glare-define-audience to name whose experience this need comes from and how far to trust each source | ## 4. Prompt Strategies The prompts below show different ways to use this skill. Each example uses a mobile banking dashboard update. ### Prompt 1: Symptom Entry: Start from a problem in the data *"Users of our mobile banking dashboard leave within 30 seconds without doing anything. Using the glare-define-user-needs skill, look across the five layers, name the needs most likely failing, and tell us what behavior would confirm each one."* **Why this works:** Starting from behavior keeps the team from redesigning the look when the real problem is finding or trusting something. **Best for:** - post-launch problems - redesign debates with no evidence ### Prompt 2: Validation Entry: Check a stated need *"Users say they want the mobile banking app to remember their preferences. Using glare-define-user-needs, apply the say-do rule, tell us whether this is a need or a want, and which foundational needs must hold first."* **Why this works:** It checks a feature request against behavior before the team invests in it. **Best for:** - roadmap planning - feature requests without user evidence ### Prompt 3: Metric Entry: Tie needs to measures *"We've named Findable and Credible as the needs on our mobile banking dashboard. Using glare-define-user-needs, tie each one to its UX metrics, say which are leading and which are lagging, and flag the failure mode to watch."* **Why this works:** The needs are already named, so the prompt focuses on how the team will know they are improving. **Best for:** - test planning - handoffs to Measure --- *Glare Framework · glare-define-user-needs · Define Area. Handoffs: glare-define-audience · glare-define-collecting · glare-define-situations · glare-ux-metrics · glare-measure-concepts*