Pitching DDD to the management
summary
Practical script and evidence for pitching Domain‑Driven Design to senior management: cite the Accelerate study linking loosely coupled architecture and org structure to delivery performance, show how DDD aligns with agile, DevOps and continuous delivery, use concrete workshops like event storming or domain storytelling (one‑hour demo wins skeptical business stakeholders), point to subdomain mapping, context maps and procurement/HR levers, and tell the car‑test story where business buy‑in led to co‑location and measurable process change rather than abstract principles.
AI-written summary · about
chapters (11)
- 0:00Introduction and context
- 5:09Common pitching mistakes
- 7:02The architect elevator
- 9:51Understanding stakeholders
- 12:03Current business drivers
- 17:17Addressing resistance
- 19:51DDD as a strategic connector
- 27:27Evidence-based arguments
- 32:29DDD and agile alignment
- 37:05Solving organizational puzzles
- 42:17Conclusion and case study
related talks
30mHow to Successfully Introduce DDD in an Organization
01h 00mFrom Domain Driven Design DDD to Delivery
55mHigh-speed DDD
58mDDD really matters!
47mDomain-Driven Design: A Complete Example
45mDon't Overdose on Domain-Driven Design
38mWhat I talk about when I talk about Domain Driven design
44mStrategic Domain-Driven Design for dummies
