4 ms·
It's not about having someone to sue it's about attracting blame. Blame assignment isn't really about who made good decisions, or who worked hard, or any of th
by erikpukinskis 10y ago
It's not about having someone to sue it's about attracting blame.
Blame assignment isn't really about who made good decisions, or who worked hard, or any of that, it's a combination of how bad it went and who made uncommon choices:
common choice + failure = external blame (who could have seen it coming?)
uncommon choice + failure = it's your fault for doing it weird
common choice + success = great job!
uncommon choice + success = I don't trust you, but you might be a genius
Since hierarchical relationships function using blame ("responsibility"), making predictable decisions becomes more important than making good decisions at some depth of hierarchy.
- iheartmemcache 10y agoThis is probably the most important comment in this thread. Being able to delegate blame out to $common-choice on project failures is the difference between that CIO being able to say "hey, not my fault, I bought the Oracle platinum integration package!" to satisfy the board rather than "sorry guys, I really thought my node.js idea would work, it's all the rage with the kids! Haven't you ever heard of Slack?!" (If this sounds strange to you, just replace "node.js" with "Rails 2" and you'll see why ASP.NET and Java's still king in any company with a market cap > 100MM && age > 20 years. It's about continuity of support, and Windows 2016 servers can still run ASP Classic and .NET 2 WebForms apps just fine.) "Responsibility" == risk mitigation for that purchasing authority.
- l1ambda 10y agoSlack is PHP and Jquery, no nodejs AFAIK.
- nandhp 10y ago> common choice + failure = external blame (who could have seen it coming?) "Nobody ever got fired for buying IBM"