empathy-map
The empathy-map skill guides teams through building a structured four-quadrant empathy map (Says, Thinks, Does, Feels) from user research data like interviews and surveys. Use this when synthesizing qualitative research into shared team understanding, identifying user goals and pain points, and extracting design implications that inform product decisions.
git clone --depth 1 https://github.com/Owl-Listener/designer-skills /tmp/empathy-map && cp -r /tmp/empathy-map/design-research/skills/empathy-map ~/.claude/skills/empathy-mapSKILL.md
# Empathy Map 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: 1. **Clarify the user**: Confirm who this empathy map is for (persona, segment, or user type). 2. **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 3. **Identify goals**: What is this user trying to achieve? 4. **Identify pain points**: What barriers, frustrations, or unmet needs exist? 5. **Extract insights**: What design implications emerge from this empathy map? 6. **Note gaps**: What do we still need to learn? 7. Think step by step. Present the empathy map in a clear, visual-friendly format. ## Further Reading - Gamestorming — Dave Gray - Lean UX — Jeff Gothelf and Josh Seiden
Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.
Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).
Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction. Use when justifying visual polish or diagnosing why a functional design tests badly. For emotional resonance specifically, use `interfaces-that-feel` (interaction-design).
Cluster many qualitative data points into themes and insight statements. Use when synthesising across multiple sessions or sources. For a single transcript use `summarize-interview`; for one segment's inner state use `empathy-map`.
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use `motion-system` (design-systems); for a full interaction spec use `micro-interaction-spec`.
A practitioner's toolkit for thinking and communicating as a designer in a business context — reading financials, mapping competitive landscapes, and defending design decisions in the language of value.
Analyse open or closed card sort results into a proposed grouping and label set. Use after running a sort study. For turning that evidence into a full structure, use `information-architecture` (ux-strategy).