Define: User Needs

Try the User Needs skill on a mobile banking dashboard update.

Prompt
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.
Sample output
**User Needs output: mobile banking dashboard**

When used correctly, the skill produces a needs brief.

| Field | Output |
|---|---|
| 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 |