The same Eric Evance says that DDD is not reasonable for a simple systems such as user, when creating ubiquitous language just spends time for obvious model.

Evance thinks, also, that in the case of technically complex project DDD is not effective, because lot of technical personnel should understand and learn the ubiquitous language and get domain model. Personally I completely disagree with this, because domain - infrastructure separation solves the problem, when only teams, which specialize in domain logic development must work with the ubiquitous language. Infrastructure developers ( as Kafka events, request routing,database interactions do not have to be perfect in the DDD.

Development of the ubiquitous language takes a time, as well as corresponding learning curve. For the same time a MVP can be build.

However, ubiquitous language helps reduce time for domain description and visualization in a clear and concise form, much better readable than long term demagogy .