Domain Storytelling—Understanding Your Users by Drawing Pictures
summary
Domain Storytelling presents a low‑barrier pictographic method (stick figures for actors, work objects, one arrow for activities) used in a live workshop demo to elicit a coarse‑grained “travel by train” happy path of about nine steps and claim that typical domain stories stay 10–20 steps. It uses whiteboard or browser tools (digital whiteboards like miro or an open‑source .o canvas) to find service boundaries, derive a domain model and follow the rule work objects → classes, activities → methods, aiming to split monoliths into modules.
AI-written summary · about
chapters (14)
- 0:00Domain Storytelling intro
- 3:45Why Domain Storytelling matters
- 8:44What is Domain Storytelling
- 13:01Roles and active listening
- 16:57Pictographic notation basics
- 21:18Happy path scenarios
- 23:24Scope factors in modeling
- 27:18Live train modeling exercise
- 49:01Tools and applications
- 51:11Stories to requirements
- 53:16Modular system boundaries
- 55:03Building domain models
- 59:26Ubiquitous language & OOP
- 1:00:32Conclusion
related talks
49mDomain Storytelling Understanding Your Users by Drawing Pictures
14mDomain Storytelling
02h 03mStorytelling For Designers
31mOnce Upon a Time...How Storytelling Will Improve Your Development and Test Results
48mStorytelling With Software
43mBeyond Discovery: A Service Designer's Guide to Agile Delivery
33mVisual thinking - simplify complex
23mThe Power of Visual Storytelling