Domain-Driven Design: What Domain?
The main misconception about Domain-Driven Design (DDD) is "thinking that it is just a handful of implementation patterns as many articles and blogs focus on the modelling patterns. It is much easier for developers to see tactical patterns of DDD implemented in code rather than conversations between business users and teams on a domain that they do not care about or do not understand".
Note
Scott Millett and Nick Tune, Patterns, Principles, and Practices of Domain-Driven Design, https://www.goodreads.com/book/show/25531393-patterns-principles-and-practices-of-domain-driven-design.
So, the Domain of the first D is not the Domain Model. It is the Business Domain.
Furthermore, DDD is not advocating Big Design Upfront. "Driven" doesn't necessarily mean "build the full domain model first." What it means is, since the business domain is so important, the domain model is the heart of the system; thus, it must...