Legacy technology—we’ve all got it. Old computers, old software, old cell phones… heck, we’ve even got an old TV or two in the basement or at the cottage. The problem with legacy technology is that while it still works, more or less, it’s often underpowered for today’s needs and as a result, it slows us down.
When you’re talking about a TV at the cottage that only gets used on rainy days, legacy technology is fine. But when you have business solutions dependent on legacy technology, it can be a serious problem.
In the world of business intelligence, we see this problem a lot. Companies invest heavily in a state-of-the-art infrastructure and for a long time, it works brilliantly. But after a while, the legacy systems become a liability. Over time, problems creep in, the needs of your users evolve, and newly available features and technologies can be really nice-to-have features.
It’s important to keep a finger on the pulse of the people who use your information systems—what they have to say about the system’s present day usefulness just might surprise you—and plan for that day when your state of the art technology has become an antique.
Working with legacy systems is just one of the factors we see regularly that makes it unnecessarily difficult for organizations to meet their core objectives, and was one of the inspirations behind the always-up-to-date SaaS (Software as a Service) model we chose for simpleBI.
Like this post? You might like some of our other posts too!