Big DDD is a fallacy. DDD was never meant to be used everywhere. You can apply some principles of DDD more broadly, such a strategic design, but the primary application is to address a new Core Domain and whatever is used to support it. That's generally a relatively small footprint, especially in comparison with the entire enterprise. The biggest mistake I see is clients trying to spray a can of "DDD Magic" (R) over everything. They are lost because it's impossible. You can't understand everything before *doing* something. That's Waterfall with teams masquerading as agile. Just as with Agile (Manifesto), the mischaracterization and misapplication of DDD is everywhere. And, the reason that I always place strategic design ahead of tactical in my books and training is that it's the most important and most applicable. I've never attempted to give more attention to tactical design, but the tactical tools are more plentiful and require more pages. That's treatment, not emphasis.