[bgro]

I was the go-to on almost every team at my last job when there was a hotfix, major risk change, security fix, etc. I knew the whole system pretty well and knew how to find and match up our awful logging to actual code and find the flaw far faster than anybody. I'd develop and test a fix and quietly discuss with that team's tech lead about risk vs reward concerns to see if they agree or want to discuss changes, then I'd get a pull request out there.

The management / executive team would always hear about major crisis hotfixes, then immediately see my name on the high visibility pull request. Thus, they think I personally must have been the cause of the problem. Somehow I was on every team and responsible for every feature, every hotfix, and the poor work every team developed that irritated clients. (Funny how I was never responsible for the positive things, though.)

Then there'd be companywide meeting / email to cover what happened with a screenshot with my name by a hotfix with comments like "Let's not have to do things like this going forward." "Some of us have to actually work for a living, and heh I don't know about you guys but _I_ don't appreciate having to panic review things like THIS!"

[pts_]

Career management enters the chat. Play blame game nothing gets done.

[mgh2]

Management had low understanding of correlation vs. causation.

This reminds me of one of Udacity's first classes: do firefighters cause fires? https://www.youtube.com/watch?v=Ku9E9uKyr4E

[bonzini]

Sometimes I have seen the opposite problem, where people look like they do not have enough engagement in customer cases, because most of the bugs are ironed out before the new release is announced.