Welcome!

Microservices Expo Authors: AppDynamics Blog, Automic Blog, Sujoy Sen, Liz McMillan, Pat Romanski

Related Topics: @CloudExpo, Java IoT, Microservices Expo, Agile Computing, Cloud Security, SDN Journal

@CloudExpo: Article

Cloud Computing: Help Desk Disasters

Saving nickels and wasting dollars should not be rewarded by bonus or promotion.

So many organizations switched to third-party help desk solutions without really putting in place any performance measures or tracking mechanisms to really measure how good - or bad - the support is.

Some executives got a big bonus for "thinking out of the box" and coming up with a cost-cutting initiative to outsource IT help desks. Those same executives do not want to hear all the complaints of people getting no results and wasting a lot of time in repetitive phone calls as well as no solutions to their problems. Even routine problems become time-consuming nightmares because the third-party support person on the other end doesn't understand the caller or the caller just doesn't understand them.

Was it a good solution for IT support? You may have saved some money on technical support costs, but how much executive time are you wasting everyday because the executive cannot get closure on a problem that would have been a routine (and short) support call? If you do an analysis, it's a clear failure.

Executives who made the decision would rather look the other way at a growing and costly problem. Is that considered leadership today in corporations? Not in my book.

First Step: Admit There Is a Problem
Most organizations won't go back and do an analysis on what they have put in place. Do a post-implementation review - if you even know what that is. (What I have seen in several organizations, the person who is supposed to have a strong, global view doesn't even have a grasp on what good systems implementation is all about. How and why did they get promoted into a leadership position?)

No one wants to see that their great decision was a costly failure as well as a waste of time for people trying to get their work done.

Stop looking the other way and trying not to acknowledge that there is a huge problem at many organizations with the lack of people knowing what they are doing in the support areas. They don't.

In talking to people from three different major banks, they all agree that their IT support sucks. Is that a clear enough description by those of you who live by politically correct corporate-speak?

Instead of flowery euphemisms and claiming that the savings outweigh the "small difficulties", face the facts. It is a disaster and by not fixing it, you are propagating the problem as well as losing money every day.

Typical problems encountered:

  • Can't hear the support person. The connection is bad.
  • Can hear the support person, but cannot understand them.
  • Can hear the support person, but they don't understand you.
  • Have to ask to speak to someone else because nothing is being done.
  • If there is a trouble ticket issued, they try to close it out before you get a resolution so their "problem resolved" numbers look good.
  • Making multiple calls for the same problem because it has not been resolved.
  • Other: You tell me - you know these issues are at your organization.

You're Losing Money - Fix the Problem
Let's be politically accurate. If you are in-charge of the IT area or the IT support area, get your head out of the sand. It ISN'T working. Look for a fix.

If you have a non-technical employee making $80,000- $250,000 getting a time-consuming run-around from a $20,000-$30,000 "technician," instead of a quick solution from a $60,000- $80,000 "technician," are you really saving money? How many wasted hours are acceptable per month? Half hour per executive? One hour per executive? Go to your boss or the corporate board of directors and ask how much wasted time per executive is acceptable?

Biggest complaints from the highly paid executives who have to deal with your "cost saving" support (my comments next to them):

  • I wasted my time with this person for several hours, got the resolution from someone else in 4 minutes. (Calculate the wasted time of the executive. Did you REALLY save the company any money on that call?)
  • I was so frustrated I ran this up my organization's management in order to get someone working on this resolution. (So let's see, instead of wasting one executive's time, your ingenuous "cost savings" initiative tripped up several executives into getting involved in what should have been a routine fix)
  • They cut the Network support staff and a security patch that should have been applied was pushed back. ALL the executive laptops that were connected on to the Corporate network had their hard drives wiped clean. Most of us did not have back-ups. (So letting go a couple of $40-$50,000 technicians made you "look good" at the bottom line. Now go back and add up ALL the wasted time you cost the company because all the executives lost all their work on their hard drives and probably will take weeks, if not more, to try to restore all that lost work - if they can. You think this is a "corporate urban legend"? This actually happened at a big-name company and no one ever went back to calculate all the time lost.)

It's time to sit down and do some evaluations. Better yet, get rid of those who don't understand systems implementation or the idea of having a sense-of-urgency in keeping the organization moving forward.

•   •   •

Carlini's book, "Location, Location, Connectivity" will be coming out later this year.

Follow daily Carlini-isms at www.TWITTER.com/JAMESCARLINI

Copyright 2014 - James Carlini

More Stories By James Carlini

James Carlini, MBA, a certified Infrastructure Consultant, keynote speaker and former award-winning Adjunct Professor at Northwestern University, has advised on mission-critical networks. Clients include the Chicago Mercantile Exchange, GLOBEX, and City of Chicago’s 911 Center. An expert witness in civil and federal courts on network infrastructure, he has worked with AT&T, Sprint and others.

Follow daily Carlini-isms at www.twitter.com/JAMESCARLINI

Comments (1)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


@MicroservicesExpo Stories
In a crowded world of popular computer languages, platforms and ecosystems, Node.js is one of the hottest. According to w3techs.com, Node.js usage has gone up 241 percent in the last year alone. Retailers have taken notice and are implementing it on many levels. I am going to share the basics of Node.js, and discuss why retailers are using it to reduce page load times and improve server efficiency. I’ll talk about similar developments such as Docker and microservices, and look at several compani...
From the conception of Docker containers to the unfolding microservices revolution we see today, here is a brief history of what I like to call 'containerology'. In 2013, we were solidly in the monolithic application era. I had noticed that a growing amount of effort was going into deploying and configuring applications. As applications had grown in complexity and interdependency over the years, the effort to install and configure them was becoming significant. But the road did not end with a ...
The goal of any tech business worth its salt is to provide the best product or service to its clients in the most efficient and cost-effective way possible. This is just as true in the development of software products as it is in other product design services. Microservices, an app architecture style that leans mostly on independent, self-contained programs, are quickly becoming the new norm, so to speak. With this change comes a declining reliance on older SOAs like COBRA, a push toward more s...
Small teams are more effective. The general agreement is that anything from 5 to 12 is the 'right' small. But of course small teams will also have 'small' throughput - relatively speaking. So if your demand is X and the throughput of a small team is X/10, you probably need 10 teams to meet that demand. But more teams also mean more effort to coordinate and align their efforts in the same direction. So, the challenge is how to harness the power of small teams and yet orchestrate multiples of them...
Many private cloud projects were built to deliver self-service access to development and test resources. While those clouds delivered faster access to resources, they lacked visibility, control and security needed for production deployments. In their session at 18th Cloud Expo, Steve Anderson, Product Manager at BMC Software, and Rick Lefort, Principal Technical Marketing Consultant at BMC Software, will discuss how a cloud designed for production operations not only helps accelerate developer...
SYS-CON Events announced today that Peak 10, Inc., a national IT infrastructure and cloud services provider, will exhibit at SYS-CON's 18th International Cloud Expo®, which will take place on June 7-9, 2016, at the Javits Center in New York City, NY. Peak 10 provides reliable, tailored data center and network services, cloud and managed services. Its solutions are designed to scale and adapt to customers’ changing business needs, enabling them to lower costs, improve performance and focus inter...
Much of the value of DevOps comes from a (renewed) focus on measurement, sharing, and continuous feedback loops. In increasingly complex DevOps workflows and environments, and especially in larger, regulated, or more crystallized organizations, these core concepts become even more critical. In his session at @DevOpsSummit at 18th Cloud Expo, Andi Mann, Chief Technology Advocate at Splunk, will show how, by focusing on 'metrics that matter,' you can provide objective, transparent, and meaningfu...
In the world of DevOps there are ‘known good practices’ – aka ‘patterns’ – and ‘known bad practices’ – aka ‘anti-patterns.' Many of these patterns and anti-patterns have been developed from real world experience, especially by the early adopters of DevOps theory; but many are more feasible in theory than in practice, especially for more recent entrants to the DevOps scene. In this power panel at @DevOpsSummit at 18th Cloud Expo, moderated by DevOps Conference Chair Andi Mann, panelists will dis...
Wow, if you ever wanted to learn about Rugged DevOps (some call it DevSecOps), sit down for a spell with Shannon Lietz, Ian Allison and Scott Kennedy from Intuit. We discussed a number of important topics including internal war games, culture hacking, gamification of Rugged DevOps and starting as a small team. There are 100 gold nuggets in this conversation for novices and experts alike.
The notion of customer journeys, of course, are central to the digital marketer’s playbook. Clearly, enterprises should focus their digital efforts on such journeys, as they represent customer interactions over time. But making customer journeys the centerpiece of the enterprise architecture, however, leaves more questions than answers. The challenge arises when EAs consider the context of the customer journey in the overall architecture as well as the architectural elements that make up each...
In 2006, Martin Fowler posted his now famous essay on Continuous Integration. Looking back, what seemed revolutionary, radical or just plain crazy is now common, pedestrian and "just what you do." I love it. Back then, building and releasing software was a real pain. Integration was something you did at the end, after code complete, and we didn't know how long it would take. Some people may recall how we, as an industry, spent a massive amount of time integrating code from one team with another...
Admittedly, two years ago I was a bulk contributor to the DevOps noise with conversations rooted in the movement around culture, principles, and goals. And while all of these elements of DevOps environments are important, I’ve found that the biggest challenge now is a lack of understanding as to why DevOps is beneficial. It’s getting the wheels going, or just taking the next step. The best way to start on the road to change is to take a look at the companies that have already made great headway ...
Struggling to keep up with increasing application demand? Learn how Platform as a Service (PaaS) can streamline application development processes and make resource management easy.
As the software delivery industry continues to evolve and mature, the challenge of managing the growing list of the tools and processes becomes more daunting every day. Today, Application Lifecycle Management (ALM) platforms are proving most valuable by providing the governance, management and coordination for every stage of development, deployment and release. Recently, I spoke with Madison Moore at SD Times about the changing market and where ALM is headed.
If there is anything we have learned by now, is that every business paves their own unique path for releasing software- every pipeline, implementation and practices are a bit different, and DevOps comes in all shapes and sizes. Software delivery practices are often comprised of set of several complementing (or even competing) methodologies – such as leveraging Agile, DevOps and even a mix of ITIL, to create the combination that’s most suitable for your organization and that maximize your busines...
I have an article in the recently released “DZone Guide to Building and Deploying Applications on the Cloud” entitled “Fullstack Engineering in the Age of Hybrid Cloud”. In this article I discuss the need and skills of a Fullstack Engineer with relation to troubleshooting and repairing complex, distributed hybrid cloud applications. My recent experiences with troubleshooting issues with my Docker WordPress container only reinforce the details I wrote about in this piece. Without my comprehensive...
Digital means customer preferences and behavior are driving enterprise technology decisions to be sure, but let’s not forget our employees. After all, when we say customer, we mean customer writ large, including partners, supply chain participants, and yes, those salaried denizens whose daily labor forms the cornerstone of the enterprise. While your customers bask in the warm rays of your digital efforts, are your employees toiling away in the dark recesses of your enterprise, pecking data into...
You deployed your app with the Bluemix PaaS and it's gaining some serious traction, so it's time to make some tweaks. Did you design your application in a way that it can scale in the cloud? Were you even thinking about the cloud when you built the app? If not, chances are your app is going to break. Check out this webcast to learn various techniques for designing applications that will scale successfully in Bluemix, for the confidence you need to take your apps to the next level and beyond.
With DevOps becoming more well-known and established practice in nearly every industry that delivers software, it is important to continually reassess its efficacy. This week’s top 10 includes a discussion on how the quick uptake of DevOps adoption in the enterprise has posed some serious challenges. Additionally, organizations who have taken the DevOps plunge must find ways to find, hire and keep their DevOps talent in order to keep the machine running smoothly.
Much of the discussion around cloud DevOps focuses on the speed with which companies need to get new code into production. This focus is important – because in an increasingly digital marketplace, new code enables new value propositions. New code is also often essential for maintaining competitive parity with market innovators. But new code doesn’t just have to deliver the functionality the business requires. It also has to behave well because the behavior of code in the cloud affects performan...