Let's learn the importance of balancing respect for the past with the need to innovate for the future through Jonathan and Miriam’s experiences.
What is "Legacy" Software?
Jonathan no longer codes; he is busy running and growing the business. Somewhere else, Miriam is the CEO of a company whose software products are built on technology that was once cutting-edge, but that's no longer the case. Both Jonathan's and Miriam's companies have made great strides with the software they have on hand. Their software has helped them build their legacy so far. Both companies stayed in business partly thanks to their software systems. For the context of this post, we call such systems legacy systems.
Respect the Legacy
Jonathan and Miriam’s companies might only exist because of their legacy systems. These systems deserve respect, as do those who created and maintained them. Those developers did their best with the tools, knowledge, and time they had. Jonathan and Miriam’s teams lived through the challenges, and their experience forms the foundation for future improvements.
Building on Legacy
The world around Jonathan and Miriam is changing—new technologies, evolving business practices, and shifting customer expectations. Their legacy systems enabled their companies to succeed, but now it’s time to build on that foundation to create innovative systems that meet modern needs.
Estimation
When Jonathan considers upgrading his system, one of his first questions is, "How big of a project will this be?" Miriam has the same concern. Both need to assess their systems’ size and complexity. They look at lines of code (LOC), database structures, screens, reports, and business logic to understand the scope of the task ahead. However, Jonathan and Miriam realize that their new systems won’t just replicate the old ones; their businesses have evolved.
The Business is Stuck in Old Ways
Jonathan’s and Miriam’s businesses have operated similarly for so long that it’s hard to envision new possibilities. In their minds, updating software means adding a column here or a button there. However, modern businesses need systems that fit their needs, not systems that force the company to conform to outdated workflows.
Do Not Rebuild Line by Line
Jonathan’s legacy system is packed with features, some of which his team no longer uses. Miriam’s system also has modules that create more pain than value. As they both plan for new systems, they realize that not every feature needs to be rebuilt. With advancements in technology, a deeper understanding of their industries, and better design practices, Jonathan and Miriam see the opportunity to create systems that truly serve their businesses.
UX/UI Design
When Jonathan’s legacy system was first built, user experience wasn’t a primary concern. Now, Jonathan’s employees expect the systems they use at work to be as intuitive as the apps on their phones. Miriam faces a similar challenge. To meet these expectations, Jonathan and Miriam must ensure that their new systems prioritize user experience and interface design.
Wants vs. Needs
Jonathan often needs help to separate what he wants from what his business truly needs. Miriam does, too. While Jonathan may wish for a particular feature, he needs a system that delivers real value. Similarly, Miriam knows that her focus should be on addressing the core needs of her business rather than getting distracted by nice-to-have features.
Cost vs Value
Jonathan and Miriam both understand that not every need is created equal. Before spending resources, they must evaluate the value a particular feature or upgrade will bring. They know it’s time to reconsider if the cost outweighs the value.
Automated Testing
Jonathan and Miriam have experienced the chaos of rolling out updates that went wrong. They know their new systems must prioritize automated testing, especially for features critical to their business operations.
Paradigm shift
Jonathan’s and Miriam’s legacy systems were built around CRUD operations—create, retrieve, update, and delete. But their businesses have evolved. Instead of deleting records, they now need workflows that reflect modern business processes. Jonathan and Miriam see that their systems must be designed around how their companies operate today, not just around data storage.
Integrations (Build vs. Buy)
Jonathan’s legacy system has many custom-built features, but now there are off-the-shelf solutions that can replace much of that custom code. Miriam is also aware that she doesn’t need to rebuild every feature. They recognize the value of leveraging existing software solutions where appropriate.
Focus on Value, Address Pain Points
Jonathan and Miriam realize that only some parts of their systems need to be rebuilt. They first address the most significant pain points, whether upgrading their data storage, improving their user interfaces, or streamlining critical business workflows.
Summary
Replacing a legacy system isn’t easy. But with careful planning, respect for the past, and a focus on value, Jonathan and Miriam can build on their legacy and take their businesses to new heights. Do Jonathan and Miriam's fictional (albeit uncanny) stories of our characters resonate with you? We would love to help you in your journey. Contact us so we can discuss how.
