Build a Says, Thinks, Does, Feels map for one user or segment. Use when sharing user understanding quickly. For a composite archetype with goals and behaviours use `user-persona`; for cross-session themes use `affinity-diagram`.
Build an empathy map to synthesize user research and align the team around user understanding.
Context
You are a senior UX researcher helping a design team build an empathy map for $ARGUMENTS. If the user provides files (interview transcripts, observation notes, survey data), read them first.
Domain Context
Empathy Maps (Dave Gray, XPLANE): A collaborative tool to externalize what we know about a user type.
Four quadrants: Says (direct quotes), Thinks (inferred beliefs), Does (observed actions), Feels (emotional states).
Also capture Goals (what they want to achieve) and Pain Points (barriers and frustrations).
Best created from actual research data, not assumptions.
Instructions
The user will describe their user type and available research data. Work through these steps:
Clarify the user: Confirm who this empathy map is for (persona, segment, or user type).
Map each quadrant:
Says: Direct quotes and statements from research (use actual quotes where available)
Thinks: Beliefs, concerns, and thoughts inferred from behavior and context
Does: Observable actions, behaviors, and workarounds
Feels: Emotional states, anxieties, and motivations
Identify goals: What is this user trying to achieve?
Identify pain points: What barriers, frustrations, or unmet needs exist?
Extract insights: What design implications emerge from this empathy map?
Note gaps: What do we still need to learn?
Think step by step. Present the empathy map in a clear, visual-friendly format.
presentation-deckowl-listenerStructure a design presentation for a specific audience and decision. Use when presenting internally. For a portfolio narrative use `case-study`; for the written argument use `design-rationale`.2,8002,800 instalaciones en skills.sh0
typography-scaleowl-listenerCreate a modular type scale with size, weight, and line-height relationships. Use when establishing typographic structure. For line length only use `readable-measure`; for judging type on an existing screen use `critique-typography` (visual-critique).2,3002,300 instalaciones en skills.sh0
visual-hierarchyowl-listenerEstablish hierarchy through size, weight, colour, spacing, and position so the eye lands in the intended order. Use when composing new work. For judging an existing screen, use `critique-visual-hierarchy` (visual-critique).2,3002,300 instalaciones en skills.sh0
color-systemowl-listenerBuild a product colour system — tonal scales, semantic roles, and contrast compliance. Use when defining or rebuilding colour from scratch. For dark-mode adaptation use `dark-mode-design`; for chart palettes use `data-visualization`; for multi-brand token architecture use `theming-system` (design-systems).2,2002,200 instalaciones en skills.sh0
dark-mode-designowl-listenerAdapt an existing palette to dark mode — surface elevation, contrast rebalancing, and desaturation rules. Use when you already have a light palette to translate. For building the base palette first, use `color-system`.2,2002,200 instalaciones en skills.sh0
