Improving Your Model by Understanding the Persona Behind the User
summary
Claim: knowing distinct personas changes how subdomains and UX are modelled and can expose why expert users avoid your product. Concrete evidence: an expert engineer designs engine parts in Microsoft Word to avoid validation friction; PwC stats show 32% leave after one bad experience, 59% after two, and 90% repeat after positive experiences. Methods used: persona mapping, empathy maps, heat‑map confidence markers, interviews/role‑play recordings, surveys, event‑storming and process modelling. Example outcome: internal tools turned products (Slack) when persona needs are surfaced.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 1:20Pichu
- 2:06Train
- 3:00Validation
- 3:57Eyeopener
- 4:44Shocking studies
- 6:03Negative experiences
- 6:25User types
- 7:36Blackstone core
- 9:34Customer segments
- 10:33Personal mapping
- 11:32The framework
- 13:30Confidence
- 14:19Validate
- 17:58Prioritize
- 19:20Challenges
- 21:27Heatmap
- 24:23Personalized onboarding
- 25:16Customer experience
- 28:33Engagement
- 31:04What do I care
- 32:54Independent Service Heuristics
- 34:12Buyer Personas
- 35:27How much do you consider them
- 36:23Conclusion
related talks
35mUsing Personas to Target Users
01h 24mHow to bring your personas to life without an exorcist
20mIterative Persona
34mGames ≠ Subjective: How to craft engaging experiences by knowing your players
44mDeveloping for "Somebody": How to Truly Know Your Users
18mOn Product, Empathy and Creating a User Centric Culture
49mHow to research and design for humans, not users
37m(Ab)User Experience.