When we design software for a complex domain, it helps to have a deep understanding of that domain, and reflect it in the system’s model. That’s the central premise of DDD. Many interesting business domains are temporal; they involve many interconnected processes and behaviours happening over time.
This is where traditional ways of understanding our domains fall short: they look at the artifacts of those processes, but not enough at the processes themselves.