Learning Pathway · Principle 01
Empathy First trained in 12 steps Empathy First means starting from real user problems, not from the technology. And it is trainable. I built this pathway with Built for Mars, Peter Ramsey's UX research library: twelve pieces of fieldwork on trust, clarity, and real human needs. Work through them in order. Then watch the same principle running in shipped AI products, recorded by aiverse.design. Pathways for all HAX Principles will be shared in our Courses and Workshops.
12 Steps 4 Case Studies · 4 UX Bites · 4 Cheatsheets Curated with Built for Mars
01 Empathy First 🔒 02 Automation vs. Augmentation 🔒 03 Transparency & Confidence 🔒 04 Real Control & Editability 🔒 05 Graceful Failure 🔒 06 Mental Model Shaping Locked pathways open with a Learner Materials login .
The pathway01 02 UX BITE What our AI can do → Learn how honest expectations can build trust and reduce disappointment with AI products.
03 04 05 UX BITE We're learning from you → See how transparency around personalisation can make data collection feel more respectful and valuable.
06 07 08 UX BITE You're not alone → Learn how empathy and reassurance can make onboarding feel supportive instead of judgmental.
09 10 11 UX BITE Don't tell, show → See why showing real outcomes builds stronger understanding than talking about AI capabilities.
12 The principle in the wild Empathy First maps to three interaction patterns in the aiverse.design library: here is each pattern, and the products doing it today.
ONBOARDING Suggested prompts "Jumpstart user engagement with smart and context-aware preset actions."
The blank prompt box is a terrible host. Context-aware starting points lower the activation barrier and meet users where they already are.
Pattern guide: 38 recorded examples → INPUT Voice input "Enabling users to interact with their voice, have a conversation or take actions."
People speak faster than they type. Voice lets users express intent the way humans naturally communicate, before syntax gets in the way.
Pattern guide: 12 recorded examples → INPUT Visual input "Let users attach images, screenshots, or other visuals as part of the input."
Pointing at the problem beats describing it. Screenshots and sketches carry the user's context without forcing them to translate it into words.
Pattern guide: 19 recorded examples → Sources: pathway content from Built for Mars (UX research by Peter Ramsey) · product recordings from aiverse.design