> I've also heard this topic referred to as "results-oriented thinking," which is generally what you don't want: you shouldn't judge a decision based on its res

> I've also heard this topic referred to as "results-oriented thinking," which is generally what you don't want: you shouldn't judge a decision based on its result, but on the information you had at the time. Had this happen at work recently and shapes why I was ok with the outcome even though it wasn't what we wanted. I was building an integration and got it working and trying to push to Prod when I realized the integration with the 3rd party required a security audit... Given the information at the time, it was the right thing to build but didn't do deep enough research. Lesson learned.