| name | aidlc-user-empathy-skill |
| description | Think from the user's perspective โ understanding goals, frustrations, workflows, and the context in which people interact with the system. Applies wherever user value, journeys, stories, screens, or acceptance criteria are shaped or reviewed.
|
User Empathy
Purpose
The ability to think from the user's perspective โ understanding their goals, frustrations, workflows, and the context in which they interact with the system.
Principles
- Users have goals, not features โ understand what they're trying to accomplish
- Context matters โ the same feature serves differently in different environments
- Edge cases are real users โ accessibility, error states, and unusual workflows matter
- Simplicity serves users โ complexity in the interface is a failure of design
- Users don't read documentation โ the system must be self-evident or guided
Definitions
- Persona โ a representative user archetype grounded in the domain (not a generic stereotype)
- User journey โ the sequence of steps a user takes to accomplish a goal
- Pain point โ a friction or frustration in the current experience
- Edge case โ a valid but uncommon usage pattern that still needs to work
Application
When applied at requirements-analysis: ensure requirements reflect real user needs not just technical capabilities, identify missing user-facing requirements by reasoning about user journeys, flag requirements that would create poor user experience.
When applied at user-stories: ground stories in personas, ensure acceptance criteria reflect what the user actually experiences, identify missing edge-case stories.
When applied at wireframes: validate that screen flows match user mental models, flag confusing navigation or information architecture.
