Sometimes it's already a compromise between too many people who questioned it, and nobody wants to discuss it any more. Sometimes the questioning is more work than actually doing it. Sometimes you get a reputation of only being in the way.
Make sure the work has been questioned thoroughly, but that doesn't necessarily mean by you.
I love that last line. I think sometimes developers can feel like they can be the hero, stopping the business from going down the wrong path simply because nobody else asked the question. They may even be right! But question your motives. Are you asking questions and throwing up roadblocks to make yourself look and feel important? Or is it purely to make the best business decision?
That's not a leading question. Honestly, both of those goals can be important and effective. But if your goal is to actually effect business change, you'll probably have better luck talking to a product person offline and having the idea come from them.
I agree with this to an extent but I feel you should always ask yourself 'why'. 'why is this feature valuable to the user?', 'why has this functionality been chosen over another?' etc.
At the end of the day the work you are doing has an impact on opportunity cost - if you at least internally question the work you are doing, you can potentially lower the opportunity cost and therefore help the business.
However, if you are part of a team of people who consider these things before the work gets to you, I agree it can be counter-productive to question it.
Sometimes it's already a compromise between too many people who questioned it, and nobody wants to discuss it any more. Sometimes the questioning is more work than actually doing it. Sometimes you get a reputation of only being in the way.
Make sure the work has been questioned thoroughly, but that doesn't necessarily mean by you.