4 Reasons Naysayers Win IT Battles, Not Wars
By Mark Peters
InformationWeek
Let's look at a few examples, and try to figure out why the tech world's knee-jerk reaction is to explain why something won't work, and, in particular, why storage changes can seem to take such a long time. On the one hand this "reluctant embrace of progress" (as some might call it) is far more prevalent than you might think, tempting me to simply quote J.K. Galbraith and be done with this. As he pointed out, "faced with the choice of changing one's mind and proving that there is no need to do so, almost everybody gets busy on the proof." But, on the other hand, the "cautiously pragmatic adoption of the new" (as others would see it) is also far more logical than you might think.
The longer history of technology shows that what I'm about to describe is not new. For instance, Chester Carlson spent years trying to get someone to buy into his idea, a process that we now know as xerography But--hey--who would ever really want near-instant copies of documents?!? Closer to home, we all know that Thomas Watson (of IBM fame) thought that there might be a total market of five mainframe computers! (And you get bonus points for remembering the name of the person who challenged the notion of ever needing a computing device at home.)
[ Learn more about Solid State: From Silver Bullet To Silver Lining. ]
Even more recently, the Internet grew from a pragmatic need for access across university systems, not from someone imagining a need for electronic email or recognizing that online shopping might be the next great idea. Why on earth would you want computers to talk to each other?
Perhaps this is our first clue: The real power and potential of something new is not always seen at the outset. Cars and telephones were merely cool toys at first, and they needed a whole infrastructure to realize their potential and endemic popularity. The same is essentially true of the Web--it was something of a chicken-and-egg situation, constrained by access speeds and network costs, as well as the limited number of websites. But its value was--at first gradually, then rapidly--seen.
Whole new approaches to business took shape. It wasn't so much invented per se, as it coalesced and occurred; no focus groups had been sitting around demanding an Internet, or a personal computer, or an automated tape library, or an iWhatever, or Google, or email, or solid-state based storage, or even deduplication. The value of such things wasn't always in fulfilling known, or well-expressed needs, but in teasing out latent needs and then fuelling the value.
1. "Safety first" is, understandably, the mantra of most IT shops of any size. Few IT managers are actively rewarded for embracing the new (although that's beginning to change as IT departments begin to use incentives and MBOs to encourage the use of things like virtualization and cloud services), whereas plenty of IT managers will be chastised if anything goes wrong. This simply means that ultra-conservatism is inbred; and interoperability, certification, application-testing, and support are certainly not things to be sniffed at when you're running, say, an airline, manufacturing, or telecom system.
2. Often only one or two vendors will bring forth a particular type of technical advance. This means that the natural competitive response from the rest of the vendor ecosystem is to point to all the negatives (whether real or simply FUD) of the new thing; whether this is because they don't have an equivalent offering or if they're merely trying to buy time until they do, the effect is the same: The volume of negativity about new tools and methods gets amplified beyond what might be expected. Mark Peters is a Senior Analyst at the Enterprise Strategy Group, a leading independent authority on enterprise storage, analytics, and a range of other business technology interests.
Federal agencies must eliminate 800 data centers over the next five years. Find how they plan to do it in the new all-digital issue of InformationWeek Government. Download it now (registration required).
1 | 2 | Next Page »
| To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy. |
Virtual Infrastructure Reports
Informed CIO: VDI Snake Oil Check
You won't lose your shirt on a desktop virtualization initiative, but don't expect it to be simple to build or free of complications. This report examines the three biggest problems when developing a business case for VDI: storage costs, ongoing licensing, and the wisdom of prolonging the investment in PC infrastructure.
Fundamentals: Next-Generation VM Security
Server virtualization creates new security threats while turning the hypervisor into a network black hole, hiding traffic from traditional hardware defenses -- problems a new breed of virtualization-aware security software tackles head-on.
Delegation Delivers Virtualization Savings
IT can't-and shouldn't-maintain absolute control over highly virtualized infrastructures. Instituting a smart role-based control strategy to decentralize management can empower business units to prioritize their own data assets while freeing IT to focus on the next big project.
The Zen of Virtual Maintenance
Server virtualization has many advantages, but it can also lead to chaos. Many organizations have unused or test VMs running on production systems that consume memory, disk and power. This means critical resources may not be available in an emergency: say, when VMs on a failed machine try to move to another server. This can contribute to unplanned downtime and raise maintenance costs. Easy deployment also means business units may come knocking with more demands for applications and services. This report offers five steps to help IT get a handle on their virtual infrastructure.
Pervasive Virtualization: Time to Expand the Paradigm
Extending core virtualization concepts to storage, networking, I/O and application delivery is changing the face of the modern data center. In this Fundamentals report, we'll discuss all these areas in the context of four main precepts of virtualization.
Virtually Protected: Key Steps To Safeguarding Your VM Disk Files
We provide best practices for backing up VM disk files and building a resilient infrastructure that can tolerate hardware and software failures. After all, what's the point of constructing a virtualized infrastructure without a plan to keep systems up and running in case of a glitch--or outright disaster.



Subscribe to RSS