What to do when the worst possible time is all the time? Don't panic -- it's just downtime.
In the wee overnight hours, our campus portal crashed due to a major network outage on the part of our cloud provider. We started receiving calls from students detailing accessibility issues, and we took the communication ball and ran with it. Three hours later, all systems were back up. In between? Virtually no excessive complaints.
I'm sure there were frustrated users inconvenienced by the downtime. Fortunately, a portion of the past year has been spent methodically, transparently, and realistically communicating about the impact of technology at our university: the good, the bad, and the ugly.
If you haven't spent time educating your users on the typicality of downtime, the time is now. Our world is moving more and more toward automation, self-service, and mobility. Users rely on absolute uptime, and when that connection is broken, panic sets in.
Technology will fail. I know this like I know that, every time I sit down to put my feet up, my dog will start running circles to let me know he needs to go outside immediately. I know it like I know that, on nights when I desperately need a full night's sleep, one of my kids will have a nightmare at 2:00 a.m. Downtime occurs at the worst possible time. Why? Because as much as we rely on technology, the worst possible time is all the time.
Technology departments tend to have the bad reputation of exhibiting only reactionary behavior, as if programmers and network admins were simply sitting on their hands and waiting for a notification that the email system is down. If you find yourself stuck in the rut of primarily responding to fires, your leadership needs to make a 180 -- quickly.
The truly valuable technology departments have moved far beyond a role of simple service provider. You need to be better than that. Simple service is expected. However, as in Mario Brothers, you need to beat the simple-service-provider level to even think about higher levels like value, impact, transformation, and efficiency.
Once you remind your users of the normalcy of unexpected downtime and instill in them a confidence about your dedicated response, you will empower them to self-soothe when these events occur. As the Beatles sang, take a sad song and make it better.
Fury at a technical outage is similar to road rage. With cars on roadways, there will be accidents, traffic, and delays. It's simply a price you pay for the convenience of using automation (a car) to get from A to B. You should teach your users to replace downtime frustration with busy work. Take a walk. Visit a colleague. Rearrange some files. There is plenty that you can do outside of the world of technology.
When a storm is coming, families create backup plans, buy ready-to-eat foods, and stock up on candles and firewood. When the electricity goes out, is there prolonged fury? Typically, the response is a resolute "Well, we knew this was coming. Let's make the best of it." Do you cancel your electricity service and find a way to power your home with a bicycle? No, you wake up, give thanks that the electricity is back on, and go about your day.
The same preparation and backup plans should be at the ready 24/7 for tech outages. As a technology leader, you should make different paths to the same services available. Students at Fairfield University can access email via the portal. When the portal is down, they can access their email via the website, direct link to Gmail, or a phone app.
Faculty members may access their courses via the portal, Blackboard, and the website. The major downtimes will typically be network-related with all access dead in the water. During those times, find your communication routes -- social media, text alerts, or cellphone calls to department leaders. Identify these communication methods in advance, and make sure people are aware of them.
Our end goals as technology leaders are to eliminate fear about technology, educate users, and promote efficiency. Being honest about downtime is step No. 1.
Are you better protected renting space for disaster recovery or owning a private cloud? Follow one company's decision-making process. Also in the Disaster Recovery issue of InformationWeek: Five lessons from Facebook on analytics success (free registration required).
Paige Francis is the CIO for IT Services at Fairfield University in Fairfield, Conn. She has a wide range of experience including defining and implementing strategic priorities for applying technology in any environment, rallying consensus across diverse interests, and ... View Full Bio
We welcome your comments on this topic on our social media channels, or [contact us directly] with questions about the site.