No UI, Still a Journey: Mapping UX for the Unseen
summary
Software systems fail because back-end naming, APIs and logic ignore the user's path, not because the UI looks bad. The talk claims mapping muddled map (consistent naming), the ghostly waiter (clear API contracts and status codes instead of “internal server error”), and the hidden logic (transparent backend flows) reduces bugs, delays and AI failures. Practical tools: developer journey maps, empathy-driven documentation that explains purpose and examples, and naming standards; expected outcome is fewer surprising spinner/failure incidents and more reliable agentic-AI behavior.
AI-written summary · about
chapters (13)
- 0:00Unseen UX mystery
- 1:27Invisible UX crime symptoms
- 2:29Red herrings suspects
- 2:51Muddled map clue
- 4:15Ghostly waiter clue
- 5:59Hidden logic clue
- 6:43AI as invisible user
- 8:27Empathy gap villain
- 9:30Shadow defeated by empathy
- 10:33Narrative for system
- 11:35Empathy-driven design tools
- 13:39Solving mystery next steps
- 14:43Q&A
related talks
30mBringing UX to Your Code
38mWhy Journey Mapping is Essential for Digital Products
37mHow customer journey mapping can improve your docs and customer experience
56mProgrammers Don't Have to Suck at UX and UI
32mLet's put U in UX!
28mDesigning for Success: UX Principles for Internal Developer Platforms
23mFantastic UI and where it lives - creating and implementing UI without the pain
37mLearning UX Design & Visual Design Basics To Improve Web Developer and Designer Collaboration