![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
*Sigh* How do you encourage a culture of "Fix It, Don't Blame It!" in a smallish company?
Along with a big case of mushroom syndrome, some people at my work tend to blame and/or get defensive about their code. I really don't care who botched it, made the bug, left something out, whatever. I just want to know how it gets fixed. The goal is to make the software work, damnit, not blame someone.
I'm trying to identify the cultural movers here... carefully.
Along with a big case of mushroom syndrome, some people at my work tend to blame and/or get defensive about their code. I really don't care who botched it, made the bug, left something out, whatever. I just want to know how it gets fixed. The goal is to make the software work, damnit, not blame someone.
I'm trying to identify the cultural movers here... carefully.
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
From:
Oof!
The couple of times I've had to, I would come in with a calm smile and demeanor, let the person know what I needed, and that I knew s/he would be able to help me, or at least steer me in the right direction.
When word got around that I didn't blame, and was pleasant in asking for help (!) in fixing (my predecessor was an abrasive personality who did the blame game), people were more comfortable with me and what I was trying to do.
Took time. Took a lot of patience. Definitely worth it in the end