Once Upon a Time...How Storytelling Will Improve Your Development and Test Results
summary
Claim: building literal stories uncovers concrete requirements, stakeholders, risks and test scenarios. Tools actually used include mid Journey image prompts, Bard prompts to generate supporters/enemies, Miro and sticky notes, improvisation in three mock living rooms, and a DND-style session with a D20 and story cubes. A prototype idea called set (a bedtime story animation device) surfaces legal and content risks and happy/failure endings. Practical results: e‑commerce living‑room exercises and DND workshops produce testable scenarios and actionable insights that teams then implement.
AI-written summary · about
chapters (15)
- 0:00Storytelling in development
- 4:24Why stories matter
- 7:56Incomplete requirements problems
- 10:24How stories engage the brain
- 12:58Metaphors and shared understanding
- 14:44Building blocks of a good story
- 17:35Q&A
- 19:02Lena’s product story
- 21:07Stakeholders and risks
- 22:11Exploring scenarios
- 23:59Test outcomes with stories
- 24:40Personas for stories
- 26:53Story workshops
- 29:00Dungeons & Dragons storytelling
- 30:44Summary
related talks
48mStorytelling With Software
02h 03mStorytelling For Designers
16mUsing Stories to Lead Product Teams
01h 05mLet Me Tell You A Story: The Power of Storytelling in Product Design
01h 02mDomain Storytelling—Understanding Your Users by Drawing Pictures
56mDesigners, Dungeons and Dragons
49mDomain Storytelling Understanding Your Users by Drawing Pictures
28mCreative Test Reporting Integrating Pixar Storytelling Ideas into SW Quality Assurance