CYA is best practice
Well, well... Here we have a survey that says the most heavily-bureaucratised IT departments are Microsoft's early adopters.
Maybe their formal processes are working well - and I hope so, because the need for performance-monitoring IT is all-too-obvious in our corporations and our government - but I have my doubts about this survey: it records the presence of particular documentation flows, not the effectiveness of the organisation's IT administration.
All too often, box-ticking 'processes' that certify our service reliability are revealed as a chaotic sham when the lights go out and someone has to restart the servers. Could it be that organisations with a thick sheaf of operational studies, proving that they can back out the change, are living in a fool's paradise? Are the studies demonstrating operational savings from Vista's enterprise management an object lesson in objective auditing - or a demonstration that the masters of a sophisticated bureaucracy can find the figures to justify any decision they want?
Could it be that favoured customers - large bureaucratic organisations dominated by 'process' - are statistically-likely to be offered substantial discounts as early adopters by Redmond? I bet the words 'Partner' and 'Strategic' are measurably correlated with a 2007 Vista rollout.
And I'm prepared to bet that you can find surveys in the 1970's, proving that America's most forward-looking and progressive corporations could be identified by their purchases of IBM machinery. There's a famous aphorism that nobody ever got fired for that - but have you ever heard that 'Nobody ever got fired for buying Microsoft'..?
Here's a final prediction: every single sheet of paper saying that 'X' corporation, department or division should be implementing Vista will be outnumbered three-to-one by cleverly-equivocal memoranda distancing the managers responsible from the consequences. And that's as good an explanation as any from Redmond as to why bureaucracy is correlated with an early Vista rollout.