You could be right, but in the hypothetical world where he's 100% right, and the current path the project or feature is taking is heading towards a dead end or is broken in some way. I feel there is a real cost that can be more easily ignored, e.g. working on a dead end or slowly failing thing that isn't set on the right trajectory is ultimately demoralizing and ends up in hindsight having been an opportunity cost and waste of your time vs. working on something else. And conversely if he's right about something like this, there should be positive feedback when it is turned around and starts performing better for the team involved?