The overlooked part of Jev decision models: defining the decision itself
The author notes that people are busy building with Jev but skip the core step of defining the decision itself, and argues that a bad decision framework makes speed and data volume meaningless.

It's funny to see a gazillion things being built with decision models like JEv, while missing the most important part: how. you define the decision itself. Speed and the amount of information your app can process mean very little if the decision framework is bad. Take a trading bot, it can process millions of signals per second, but that's only useful if it know what makes a trade worth taking and when to take it. If you give it a random or poorly defined decision rule, you just built a fast machine for making bad decisions.