Research: Data Center Debate: Standardization vs. Specialization

Joe Masters Emison and Jonathan Feldman02/28/13

2013 Standardization Survey

Compare a standard four-door sedan, the modern iteration of Henry Ford's Model T, with a high-end minivan with integrated child seats, all-wheel drive, dual DVD players and 15 cup holders. If the minivan is right for you, it's really right. If not, that's a lot of money and efficiency out the window.

Likewise, there's something to be said for an IT infrastructure designed from standard building blocks -- uniform data center servers, network gear and software stacks -- and limited to a constrained set of end user hardware and operating systems. Such an environment will be easier to manage and secure, and new services can be rolled out fast. In contrast, giving business units carte blanche may deliver better flexibility, drive innovation and precisely meet employee needs.

The 400 business technology professionals responding to our InformationWeek Standardization Survey, no surprise, like standards. They nurture them and may even have enforcement powers. Among the 31% without policies, the No. 1 reason for avoiding standardization is the lack of power to stop business units from doing their own thing. The implication: If only.

But should IT pros fight for their right to drive conformity? (R6100313)

Survey Name InformationWeek 2013 Standardization SurveySurvey Date October 2012Region North AmericaNumber of Respondents 400Purpose To explore the state of IT standardization policies in the enterprise

3 Authors' Bios4 Executive Summary5 Research Synopsis6 Consumer Theory of Standardization9 Adoption Outside of Startups12 Can the Consumer Theory Work in the ­Enterprise?16 Standards Are Good; Being the 'No Police' Is Not17 It's All in How You Present It18 It's Complicated20 Driving the Point Home21 Grading and Governance23 Our Own Worst Enemy26 Appendix30 Related Reports