3 ms·
From TFA: > The second common variant is, instead of centralizing a service so that everyone in the company uses it, every department does it on their own. Dep
by RevEng 15d ago
From TFA:
> The second common variant is, instead of centralizing a service so that everyone in the company uses it, every department does it on their own. Department managers like it because it’s one less party not reporting to them to depend on (and nothing scares managers more than needing things from people not reporting to them.) And the people managing the department managers like it because they don’t need to deal with the centralized service department allegedly failing — and having to figure out if that’s really true and how to fix it, or if it’s an excuse made up by the other departments for failing at their own job. Here, too, if outcomes are what concerns you rather than what's easiest for senior leadership, standardizing on something across the company vs having everyone roll their own variant is a hard decision to make.
The argument is that centralization is the better outcome, even if it's less appealing to leadership. My counter argument is that centralization has downsides that need to be considered; it isn't inherently better.
- yosefk 14d agoNo, the argument is that it's less appealing to leadership even when it's the better outcome, but not vice versa - it might or might not be better for reasons unrelated to said appeal ("standardizing on something across the company vs having everyone roll their own variant is a hard decision to make.") And of course you can also end up standardizing on something because it benefits someone good at politics even though it's a bad idea, I just didn't elaborate on this stuff because it is too far away from the subject. I didn't say you should always stanardize on something though, I said that it was a hard decision