Storytelling And Tech
summary
A UX practitioner recounts converting skeptical stakeholders at a 150‑year railroad company by swapping jargon for concise stories and images, winning buy‑in for redesigns. Concrete examples: a legacy command‑line system rejects a new web UI because experts lose mastery (team finds it violates four of five usability qualities), an ERP rollout likened to firefighting captures causes and consequences, and humor uses pauses, callbacks and metaphors to hold attention. Key tactics: write then cut, you can't be a hero if you started the fire, use images, time pauses, and offer a single call to action.
AI-written summary · about
chapters (10)
- 0:00Intro
- 9:00Examples
- 9:14Case Studies
- 13:27Case Study View
- 16:07Humor
- 16:50Timing Delivery
- 18:08Fail Faster
- 19:05Fire Marshal
- 19:34Talk Tips
- 21:11Conclusion
related talks
31mStorytelling for Engineers
45mTelling Your Technical Story
05mTell Your Technical Story
42mSpeaking to Stakeholders and getting your Buy-In as a Designer
39mHow to do half-assed UX
24mBreaking Out of the UX Bubble
31mHow to Effectively Communicate Technical Ideas to Non Technical Audiences
29mChange Management for Humans