Behavior Driven Development is "Test–Driven Development done right", but in practice, it often ends up being the same old Test–Driven development done with new tools and more verbose test names. The goal of writing executable specifications is the writing; learning what to specify, what to write about, what to leave out, and the right level of specificity. BDD doesn't guarantee specification done right, but getting specification right will have a profound effect not only on how useful the specifications are, but also on test design itself, as well as on your software development process and personal and team productivity. This talk will help you leverage all that BDD has to offer while helping you avoid the common traps that can be obscured by the new generation of tools.