> Being proactive instead of reactive is very difficult if your product managers don't know what your customers find useful. They can't know what your customers

> Being proactive instead of reactive is very difficult if your product managers don't know what your customers find useful. They can't know what your customers actually use your product for without metrics. So MDD is an office politics tool? TDD and BDD are development tools that help you write better more maintainable code. If all MDD is saying "put in metrics to help you win arguments with your PM", then I already am a MDD master. I'm not saying measuring and testing aren't important. I'm saying it's not a design paradigm. I don't know of an engineer who doesn't run tests before diving in to solve a problem on an existing system. If you start from scratch, how does MDD help you build a restful API? What about an authentication microservice? Adding a new feature - what metrics can we measure? TDD and BDD BOTH help you with the process of engineering stronger solutions. Saying "measure things and use analytics to make decisions" doesn't really qualify as a paradigm.