I find that the agonizing rarely bears as much fruit as doing. In some cases we've deployed, found horrible problems that were completely unexpected and switch

I find that the agonizing rarely bears as much fruit as doing. In some cases we've deployed, found horrible problems that were completely unexpected and switched course. Additional time spent agonizing would just have delayed getting us to the point where we learned those things. The critical information we needed to make that decision wasnt going to reveal itself with additional introspection. This isnt to day when a dev waves a big red flag in the beginning you should ignore them, though (ever). But, I find that waving that red flag doesnt ever inhibit delivery speed whereas multiple people agonizing over decisions where the information to determine the "right" one usually does.