I've been in those companies where "struggling departments" ended up getting all the praises and raise in budgets the following quarter because of the heroic saves they did, and raising awareness on how important they are... For stuff they totally caused on themselves. Meanwhile, my perfectly purring department was struggling to keep the lights on. It's a serious problem in this industry due to the disconnect between…
Nobody ever gets credit for fixing problems that never happened (2001) [pdf]
31–40 of 274 posts
Re: Nobody ever gets credit for fixing problems that never happened (2001) [pdf]
#32Nobody ever gets credit for fixing problems that never happened (2001) [pdf] - https://news.ycombinator.com/item?id=39472693 - Feb 2024 (424 comments)
Nobody Ever Gets Credit for Fixing Problems That Never Happened (2001) [pdf] - https://news.ycombinator.com/item?id=8940820 - Jan 2015 (50 comments)
Re: Nobody ever gets credit for fixing problems that never happened (2001) [pdf]
#33I've been in those companies where "struggling departments" ended up getting all the praises and raise in budgets the following quarter because of the heroic saves they did, and raising awareness on how important they are... For stuff they totally caused on themselves. Meanwhile, my perfectly purring department was struggling to keep the lights on. It's a serious problem in this industry due to the disconnect between…
Re: Nobody ever gets credit for fixing problems that never happened (2001) [pdf]
#34You'll see capability traps everywhere once you learn about them. Sterman, Repenning and other collaborators wrote several papers after this one. All fascinating and almost entirely depressing. Especially since MIT's Sloan school, where system dynamics first became a discipline, is just around the bend from Harvard Business school, where system dynamics first became ignored.
Re: Nobody ever gets credit for fixing problems that never happened (2001) [pdf]
#35There are a lot of things like this. My favorite is how elegant solutions often look simple in retrospect. So if you noodle on a problem for a while and then come up with a clever solution: once you explain it to someone they'll be like, "yeah, of course." Meanwhile the guy next to you that overcomplicates the problem ends up getting kudos for building something so difficult :D
The passage that comes to mind for me whenever this idea comes up, from the Brett version of the Holmes story "The Dancing Men": H: So, Watson. W: Hmm. H: You do not propose to invest in South African securities? W: How on earth do you know that? H: Now, confess, you are utterly taken aback. W: I am! H: I should make you sign a paper to that effect. W: Why? H: Because in a few minutes you will say it is all so absurd…
Re: Nobody ever gets credit for fixing problems that never happened (2001) [pdf]
#36Re: Nobody ever gets credit for fixing problems that never happened (2001) [pdf]
#37Re: Nobody ever gets credit for fixing problems that never happened (2001) [pdf]
#38There are a lot of things like this. My favorite is how elegant solutions often look simple in retrospect. So if you noodle on a problem for a while and then come up with a clever solution: once you explain it to someone they'll be like, "yeah, of course." Meanwhile the guy next to you that overcomplicates the problem ends up getting kudos for building something so difficult :D
("I have made this longer than usual, only because I have not had the time to make it shorter.")
Blaise Pascal
Re: Nobody ever gets credit for fixing problems that never happened (2001) [pdf]
#39Article published in the Summer 2001 edition of California Management Review, yet it never mentioned Y2K, the first thing I thought of when I read the line "fixing problems that never happened". Perhaps it was actually written in 1999 and took a while to get published, because otherwise that seems a very strange omission. The Y2K problem was very much over-hyped by the American news media at the time (no, at no point…
The problem is that a lot of people have a very binary view on life. Either something is a complete success or a complete waste of money, rarely do we accept that most projects fall somewhere in the middle.
So when someone predicts something will happen with a 90% probability, and then the 10% chances happens and the predicted event does not happen, people will talk about what a bad prediction that was and how they were clearly wrong.
It's the same logic that causes people to say vaccines don't work because they don't stop a disease with 100% effectiveness, or that there is no point to wear a seatbelt because people still die while wearing one.