I've found having a cascade of things helps. Trying to split things into "decision at this later, or pass on to the next" with increasingly complicated models/a

I've found having a cascade of things helps. Trying to split things into "decision at this later, or pass on to the next" with increasingly complicated models/approaches. Start with ifs, then svms then something else for example. This has some technical benefits, like speed, and gives you a place to put important hard coded fixes for where a better model makes a small but key mistake. But the bigger benefit imo is getting something to solve the bulk of the problem quicker, and a organisationally it means not saying no to an approach - just where it fits and at what level of improvement it's worth it.