Our client is in the chemical industry. Hence, it was quite difficult for my team to adapt quickly to the corresponding business. To be more precise, in order to build the product, we needed to understand mathematical models, equations and the glossary of chemical terms. BDD was the solution. The management team heard the magic buzzword “BDD” and hoped that it would solve our challenges. However, nobody was following the principles of BDD and BDD became just another “automation tool”. Business users continued to send documents and emails with the requirements, Developers never used the BDD approach, the Analysis team did not follow the patterns to write correct Gherkin syntax as prescribed by the BDD creators etc. The result for the project was just a big mess. In order to address the problems, we had some mini training sessions for all our team regarding the correct principles of BDD. We also trained customers with webinars and showed them how they could write Gherkin files. Also, we have introduced the pre-flight checks concept. Hence, my proposal is this: Do you want to use BDD? Use it as intended or it will just create more complexity.