For those who'd sacrifice application performance and uptime to save a few bucks: Have you lost your mind?

Lawrence Garvin, Technical Product Marketing Manager, SolarWinds

September 4, 2014

3 Min Read
(Source: OpenClips on Pixabay)

Cost savings is a perfectly admirable IT goal. But is it worth it when it comes at the expense of users' satisfaction with the availability and performance of the applications they need to perform their job every day?

Your answer to this question will depend on what you do. If you're a CFO or other financial type, your answer might be a resounding "Yes! Users? What are users?" However, your status as a -- and I'll just say it -- bean counter doesn't make you right.

If you're an IT pro, particularly one who interacts with users every day, you recognize that application performance is key to maintaining their happiness. Here are some basic tenets on how people are accessing and using their applications that have changed over the past five years.

First, we've become much more mobile. It was only seven years ago that the iPhone was launched. Almost immediately employees started expecting to use it in the workplace.

[Are you maximizing morale? See 5 Steps To A Healthy IT Culture.]

Second, everybody is working more hours, with larger workloads and an expectation of higher productivity, and all that work is now dependent upon applications. Twenty years ago, about the only people using applications regularly were secretaries (who spent about half their day typing in WordPerfect) and accountants (who spent about two-thirds of their day in Lotus 1-2-3). Speed wasn't much of a concern. Shucks, just considering how much faster a word processor was than an electric typewriter kept most secretaries in heaven until the turn of the century.

But today we're all engaging with myriad applications on PCs, notebooks, tablets, phones, and more devices to come, and we're accessing work applications "after hours" as well as at the office. As such, always-available, high-performance applications are essential for almost every person who has a job.

Ah, but if only it were that simple. The real problem is that delivering those applications involves a highly complex array of end-user devices, services, service providers, and connectivity methods. The IT pro is the face of all of those backend "black box" components that the end user doesn't really care about. The only thing the end user is thinking is "Just make the application work! Please!?"

Users also contribute to this complexity with their immediate-gratification mentality. They want 100% availability and optimal performance, and they demand instantaneous fixes when things go awry. But they're not going to get instantaneous fixes -- remember the complexity of the back end I just described? But they're going to demand them nonetheless. IT pros are going to have to step up their game.

Oh, here's a parting shot for the bean counters: Poor-performing applications or, worse, unavailable applications are productivity drains, costing companies tens of thousands of dollars to millions of dollars annually, depending on company size. And for those CFOs who'd sacrifice application availability and performance to save a few bucks, consider how your own financial teams would function without their spreadsheets and enterprise financial applications.

So IT pros: Rather than bend to the will of your money-minded brethren, your rally cry needs to be: It's all about the applications, stupid!

If the world wasn't changing, we might continue to view IT purely as a service organization, and ITSM might be the most important focus for IT leaders. But it's not, it isn't and it won't be -- at least not in its present form. Get the Research: Beyond IT Service Management report today (free registration required).

About the Author(s)

Lawrence Garvin

Technical Product Marketing Manager, SolarWinds

Lawrence Garvin, head geek and technical product marketing manager at SolarWinds, wrote his first computer program, in RPG-II, in 1974, to calculate quadratic equations. He tested it on some spare weekend cycles on an IBM System 3 that he "borrowed" from his father's employer. Since then he has studied, dabbled with, and actually programmed in just about every known computer language. Garvin also has worked on a half dozen different variants of Unix on 3B2s, RS 6000s, HP 9000s, Sparc workstations, and Intel systems. Along the way, he did a few years in database programming and database administration.

Never Miss a Beat: Get a snapshot of the issues affecting the IT industry straight to your inbox.

You May Also Like


More Insights