Domain Storytelling Understanding Your Users by Drawing Pictures
summary
Domain Storytelling uses a tiny pictographic language and a workshop format to turn spoken procedures into verified diagrams so domain experts immediately confirm understanding. It records actors/work objects/activities with sequence numbers on a canvas, omits if/else in favor of scenario-based modeling, and uses whiteboards, tablets or egan.io live tooling. Examples include a leasing flow and a train trip exercise; outcomes are user stories, classes/methods for a domain model, and clearer service boundaries—misunderstandings drop and agreement happens in minutes.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 0:30Story
- 1:35Scratch
- 2:35Main Storytelling
- 4:55The Story of Bob
- 5:50Car Leasing
- 6:40Monoliths
- 9:10Domain Storytelling explained
- 11:40Who are the right people
- 13:20Storytelling
- 14:45misunderstandings
- 15:45simple rule
- 18:00active listening
- 19:05pictographic language
- 24:15scenariobased modeling
- 25:50travel by train
- 26:25story name
- 27:20story example
- 32:55Variants
- 35:15Domain Storytelling
- 42:50Scope Factors
related talks
01h 02mDomain Storytelling—Understanding Your Users by Drawing Pictures
14mDomain Storytelling
39mFinding System Boundaries with Domain Storytelling
52mCarving Microservices out of the Monolith with Domain Storytelling
50mIt's All About the Domain, Honey - Domain-Focused Architecture with DDD
31mOnce Upon a Time...How Storytelling Will Improve Your Development and Test Results
02h 03mStorytelling For Designers
48mStorytelling With Software