Domain-Driven Design in ProductLand
summary
Domain-Driven Design often fails in product companies because it assumes one contained organization; the actual lever is feedback loops are oxygen — design requires owning and shortening user signals ( examples: intercept social channels, Loom screencasts, reduce a 1,000‑bug backlog). Use context mapping and selective EventStorming to find boundaries, build a surface model that translates to internal bounded contexts, visualize fear (a “fear map”), and treat design integrity as the primary strategic constraint.
AI-written summary · about
chapters (9)
- 0:00Introduction and rabbit hole
- 3:20Language and secret ingredient
- 8:35Feedback loops in product land
- 16:20Surface language and models
- 23:00Model dilemma and user mental models
- 30:24Architecture and coupling issues
- 43:38Strategy and core domain
- 55:00Design integrity and road mapping
- 1:00:00Q&A and closing
related talks
47mDomain-Driven Design: A Complete Example
44mStrategic Domain-Driven Design for dummies
38mWhat I talk about when I talk about Domain Driven design
41mDomain-Driven Design: Hidden Lessons from the Big Blue Book
48mDomain-Driven Design tactically and practically
55mDomain-Driven Design: back to the roots
56mMicroservices and Domain-Driven Design — The Strategic Parts
59mDomain-Driven Design - Where Rubber Meets the Road