2 ms·
> This is what happens when there are non-technical folks in the upper-echelons of an organization The described behavior can be found in non technical organiz
by willcipriano 4y ago
> This is what happens when there are non-technical folks in the upper-echelons of an organization
The described behavior can be found in non technical organizations as well. A room full of people will never blame itself, they will always blame someone not in the room (or failing that push someone out of the room and blame them). In group VS out group behavior[0][1].
You could tell the same story around a lemonade stand, "Looks like we are going to be busy next week, should I order more lemons?" "no, we ordered plenty", a week later "Why didn't you order more lemons!".
It's not a technical problem in the slightest, or even a human nature problem, this stuff was wired in when we were early primates.
[0]https://en.m.wikipedia.org/wiki/In-group_and_out-group https://en.m.wikipedia.org/wiki/In-group_and_out-group
[1]https://en.m.wikipedia.org/wiki/In-group_favoritism https://en.m.wikipedia.org/wiki/In-group_favoritism
- oblio 4y agoThis probably predates primates and it's just a standard social animal trait that's useful so is kept around. Think dogs, wolves, ants, whatever.
- asoneth 4y agoI used to believe this too, but I've worked in multiple organizations now where there was no shame associated with assessing who or what factors contributed to project failures. The primary desire was to understand them accurately to mitigate those same failures in the future. Ultimately it comes down to the organization's culture and whether failures are punished or accepted as a necessary side-effect of doing ambitious work.