I have a question about the cow path problem. The blog postulates that, when choosing an appropriate approach/framework/technology/tool, I should lay out the op

I have a question about the cow path problem. The blog postulates that, when choosing an appropriate approach/framework/technology/tool, I should lay out the options and choose the best one, taking into account the longterm cost of adopting something new? What if I'm not competent at most of the options? I can spend a few days evaluating each one and getting a beginner's idea of what it can do, but evaluating the long-term costs of more than 2 or 3 choices seems like it would take an inordinate amount of time. Say my team has expertise in our own areas but we need to add a thing in some new domain we have no experience in, for example web development. We're going to need to build our thing on some sort of framework, but, for the sake of argument, we're not familiar with any of them. How do we choose the right one without spending months in analysis paralysis but also not simply following the cow path?