Listen to the developers

In this presentation Dan North (pioneer of BDD) makes an interesting observation: How do you know when Domain Driven Design succeeded? When you listen to a conversation between two developers, and you can't tell if they are discussing the code or the business problem.

A year ago I would not have thought this as a particular accurate observation. At this time I was working in a project, where we had quite a good Ubiquitous Language.
But now I have experience in working in a project, where the developers (including me) often cannot connect their current implementation-steps to the underlying business-reasons. In this project the "implementation-language" is very far away from any business-language. So the above statement seems to bring the value and goal of Domain Driven Design very much to the point.