I was recently asked to do a keynote on the critical need to modernize enterprise technology systems in response to the threat of digital disruptors.
As I was doing my keynote prep, my mind wandered — yes, I know, shocking — to my own personal record of technology innovation. I take great pride in embracing new technologies and experimenting with technologies long before they become mainstream. And yet, as I gazed around our house, I found embarrassing instances of our personal legacy technology long tail.
Out With the Old, In With the New?Consider our personal records management system. This legacy tail of paper records management is doubly embarrassing when I consider the additional boxes of paper records in the basement with notations like, “Destroy in 2012.”
Not to mention our state of the art “image” collection. This collection is digital since the advent of decent cell phone cameras — numbering over 40,000 images in Google Photos, all automatically tagged and categorized by Google — but embarrassingly Costco analog for long stretches of our children’s lives. The long-tail of this legacy personal history is devoid of even the most rudimentary of taxonomies or metadata to help figure out exactly what is inside these mysterious Costco envelopes.A walk through our family room also turns up some technology artifacts — a landline phone, CDs and DVDs — all of which survive and take up space despite the fact we have long since moved onto cell phones, Spotify and Netflix. Our landline phone is a particular mystery to our children, who pepper us with questions like, “Why do you still have a landline?” — not realizing the answer would be doubly confounding if they realized we never answer this phone.
Related Article: Where Does Legacy Software Fit in the Digital Workplace?
Legacy Systems' Holding Power on Organizations
These revelations led me to ponder the pesky question of exactly how difficult it is for organizations to innovate quickly at scale while all of their pesky legacy systems continue to slog along in the background.
Consider a few data points:
- Over 17 million fax machines are still in use in the US, with global numbers in excess of 46 million fax machines (source: HTPoint.com).
- US companies spend more than $120 billion a year on printed forms, most of which outdate themselves within three months' time (source: Integrify.com).
- The estimated global annual invoice volume is 550 billion, and about two thirds of this volume is still in unstructured formats like paper and PDF (source: Billentis.com).
- There are 116 million Americans over the age of 50, and 20% of them do not use the internet.
The list of examples of legacy technology drag goes on and on.
Legacy systems will not go away on their own. Just because newer and more modern technologies have been introduced, doesn't mean the legacy system goes up in a cloud of smoke. Legacy systems persist for many reasons — some customer-based, some technological, some political, some financial — and they are difficult to displace. But these legacy systems do ultimately need to be replaced and modernized.
Related Article: The Road to Digital Innovation Lies in ... Legacy IT?
The Digital Transformation Elephant in the Room
So what is the path forward? The long tail of legacy technology in most large-scale organizations cannot just be ignored. It is the digital transformation elephant in the room and must be treated as such. The path forward is to make modernization and replacement a strategic information governance priority, rather than an afterthought.
For too long, information governance has been viewed by organizations as something more akin to good hygiene or eating more fiber: something you should do, but that isn't necessarily pleasant. The challenge of the accelerating pace of technology innovation and the resulting explosion of information chaos is compounded by the head in the sand approach many organizations have when it comes to facing the reality of their legacy infrastructures.
This means developing a strategy for deciding what to do with all of the accumulated information in systems due for retirement. It means thinking about what portions of this accumulated history actually have long-term value, what portions of your dark and impenetrable information archives could have value if you applied modern cognitive and machine technologies to them, and getting rid of the rest.
These choices are not nearly as simple as they seem. Many organizations dodge the necessity for information migration and disposition and put the problem off to be addressed “sometime.”
Here are some of the annoying questions organizations need to ask about each information system as they modernize:
- How old is the system and where is it in its lifecycle? That is, is the system a current version and/or still supported by the vendor?
- Is it customized or integrated with any other systems?
- Where is it physically located? This is often a significant issue for multinational organizations, and governmental entities, because of privacy and data protection concerns.
- Who owns the system (and therefore the data on it)? IT is a custodian, but ultimately the business is the steward and owner of the information on those systems.
- How will you find out where rogue or shadow IT systems, likely unsupported by IT, are being used? Common examples include file sharing systems, personal email and communications applications.
- How will you find where one-off tools — like Access databases, Lotus Notes applications, authoring tools, business-deployed SaaS applications, and single-seat applications — are being used?
(source: AIIM CIP Study Guide)
As is demonstrated in survey after survey, without very deliberate and carefully planned change management strategies that directly tackle core information governance questions, even the most well-intended digital transformation initiatives often go astray. Make it a New Year’s resolution to build a strategy that avoids the dangers of unplanned legacy modernization.
Related Article: Failure to Launch: 5 Causes of Digital Transformation Failure
Learn how you can join our contributor community.