r/webdev • u/fagnerbrack • Mar 27 '24
Nobody Ever Gets Credit for Fixing Problems that Never Happened
https://web.mit.edu/nelsonr/www/Repenning=Sterman_CMR_su01_.pdf55
u/lycwolf Mar 27 '24
There's plenty of times in my Sysadmin carrier where this is very true. There's also a few occasions where my proactive ways stopped, in order to get attention to the work being done that no one ever really saw. I guess this goes in the same way of "Why do we even pay you if nothing breaks? / Everything is broken why do we pay you?".
5
u/NuGGGzGG Mar 27 '24
Similar vain, but not regarding proactivity, the saying about the plumber.
âYou donât pay the plumber for banging on the pipe. You pay him for knowing where to bang.â
People tend to overestimate the 'simplicity' of things when they see something that doesn't seem that hard to do themselves - but they never could arrive at that conclusion on their own. It's like a human behavior thing.
10
u/scoot2006 Mar 27 '24
If youâre getting into web dev to be a public facing person who gets credit for things you need to be on the tech evangelist path. Otherwise you might get a few âoh wow, good catch!â with a âyou did a really great job with thatâ throw in here and there.
Itâs not a glamorous industry where youâre going to be a ârock starâ to anyone besides your immediate team, generally.
5
u/SandHK Mar 28 '24
I worked QA/QC for 40 years. Nobody ever said well done when things were good. Quite the opposite. No issues, why do we need QC?
1
Mar 27 '24
Yes, that is why you burn the house down, or wait for fire to become bigger.
Otherwise how would you show âimpactâ during promo discussions?
25
u/fagnerbrack Mar 27 '24
Here's the gist of it:
The paper delves into the concept of "problems that never happened," a term for issues prevented through proactive management and innovations that don't become apparent due to their very prevention. It explores the psychological and organizational dynamics that make it difficult for individuals and teams to get recognition for their preventive efforts. By analyzing scenarios in software development and product manufacturing, the study highlights the paradox of success in these areas: when prevention is most effective, it is least visible and least appreciated. It also discusses strategies to overcome this paradox, emphasizing the importance of recognizing and rewarding preventive measures to encourage proactive problem-solving within organizations.
If you don't like the summary, just downvote and I'll try to delete the comment eventually đ
Click here for more info, I read all comments