Two years ago, you and your team spent a great deal of time and a good deal of money on a new backup and recovery system. The system and vendor you selected hit all the check boxes in the technology selection plan, and the demos of the system were perfect. In addition to the great platform, the vendor was wonderful and the system has been working well.
Your selection project went off without a hitch, as did the implementation phase. Things are going well and, for the most part, everyone is happy with the new platform.
About six months ago (a year and a half after implementation), the organization started going through a growth phase. This growth added additional requirements for your systems and processes. New people meant new computers. New computers meant new support and storage, which meant new administrative processes and tasks.
These additional requirements were fairly easy to meet. The platform and vendor you chose easily kept up with the growth requirements, and your team has been able to keep ahead of the changes and growth.
While the organization is undergoing growing pains, you and your IT staff have been able to continue to provide top-notch service. Things look easy these days, and you’re being congratulated from all corners of the organization for the great work you and your team have done.
Then one day some systems went down. These systems were mission-critical, and everyone was screaming to have them back online as soon as possible. Unlike previous backup/recovery processes where recovery time was measured in days and weeks, your system was able to get your most critical applications and servers back up in less than three hours.
Based on the quick recovery and the months of great service from the IT staff, the CEO called a town hall meeting to deliver a well-deserved congratulatory message to the entire IT staff. Everyone’s happy with the work the team has done, and there are plenty of folks applauding the efforts of the team.
As we all know, it’s not easy for IT to be applauded. IT is usually behind the curve when it comes to growth. IT is usually struggling to do more with less. So in this case, you and your team are very proud of the work you’ve done.
But the great work you’ve done today has its foundation in the hard work your team has done for years. In fact, it goes back many years. It goes back to the preparation for the selection phase of your new system, when you and your team spent many days and weeks preparing the selection criteria and researching systems and vendors.
One area that you spent a great deal of time on was considering the future state of the organization and how you could select a system today to allow you to future-proof the organization. You and your team spent a lot of time understanding what the future requirements are for the system. Your team had to truly understand what your system should do for your organization today and what the system needs to do the next year and for years to come.
This hard work in the past has helped you prepare for today and tomorrow. Your team was able to future-proof the systems within the organization to prepare for exactly the scenario you’ve just encountered.
Easy never comes quick and easy. It takes hard work and long hours to make things look easy. Hard work and a little bit of future-proofing can go a long way to making things look easy.
How are you preparing your team and systems for the future?
Image Credit: Hard Work on Flickr