Rebuilding the Foundation: Why Legacy Systems Hold Companies Back

Most conversations around product development tend to focus on what is visible. Features, user experience, and the pace of iteration often dominate the discussion, and understandably so. These are the elements users interact with and the areas where teams feel the most immediate impact. And so it’s easy to believe that if the product looks right and behaves well, the hard part is largely done.

In reality, the most consequential challenges tend to sit just below that surface.

But inside growing organizations, there is often a different kind of friction that is harder to name. Decisions are taking longer than expected. Teams enter the same meeting with different numbers. Simple questions require more time and effort than they should. Over time, these moments accumulate, creating a subtle yet persistent drag on progress. And that friction isn’t caused by the product itself, but by the legacy technology quietly supporting it.

These aren’t product problems in the traditional sense. They are symptoms of something deeper.

In a recent episode of the Product Builders Podcast, we sat down with Mason Lancaster, Senior Data Engineer at CHG Healthcare, to explore how data systems quietly shape the way products are built, scaled, and improved. What emerged from that conversation was not just a story about data migration, but a broader look at how foundational systems can enable or constrain everything.

When Systems Fall Behind the Business

Nobody sets out to build fragmented systems for their organization. In early stages, system structures are often simple and effective. A few tools are introduced to support immediate needs, and data begins to accumulate in ways that feel manageable.

As a business grows, that simplicity fades. Data begins to live in multiple places, each with its own structure, logic, and limitations. Each decision is reasonable in isolation, but over time, these systems harden into what most organizations would recognize as legacy technology — deeply embedded, difficult to change, and increasingly misaligned with how the business actually operates.

From the outside, an organization can appear functional. Dashboards exist, reports are generated, and insights are shared. Under the hood, however, the experience is very different. Teams spend more time validating data than using it, and engineers are pulled into maintaining pipelines rather than enabling new work. The business continues to evolve, but the systems supporting it remain anchored in a previous version of reality.

As Mason Lancaster, Senior Data Engineer at CHG Healthcare, explained during our conversation:

Systems weren’t built for the world the business operates in today.

‍

This gap is rarely dramatic at first, but it compounds quickly. Technology continues to move forward, while internal systems struggle to keep pace. And what begins as a manageable inconvenience gradually becomes a constraint on how the business operates.

How to Know You Have a Data Problem

The impact of outdated systems is rarely confined to engineering teams. It shows up in the day-to-day experience of the entire organization.

Not every inefficiency means you need a full overhaul. But there are patterns that consistently appear across organizations dealing with legacy systems. These signals are often framed as data issues, but they are just as often symptoms of deeper legacy constraints within the organization’s technology stack.

A few signals to look for:

• Leaders find it difficult to get clear answers quickly.
• You can’t answer basic business questions without pulling data from multiple sources.
• Different teams report different numbers, and no one’s sure which is right.
• Data requires manual work to clean, validate, or interpret.
• Product teams begin to rely more on instinct than on data they can trust.
• Insights take too long to generate to be useful.
• Product decisions are made without confidence in the data.

And then there’s the bigger one:

• There are clear opportunities for the business but the system can’t support them.

These signals are often easy to rationalize in isolation and often teams will just accept these inefficiencies as a normal part of the process.  But together, they point to a system that has fallen behind. And now you’re not just dealing with inefficiency. You’re dealing with missed potential.

If there are things that would benefit the business that you’re not able to do today, there’s probably a deeper issue with the system.

‍

At that stage, the issue is no longer about efficiency. It is about capability. The organization is not just moving slowly; it is unable to move in the ways it needs to.

What Can Change When the Foundation Is Fixed

When teams talk about modernizing their systems, the focus often goes straight to the tools. But the real impact shows up in how the business operates.

At a basic level, data becomes more accessible and more reliable. Teams begin working from a shared understanding, which reduces friction and allows conversations to focus on action rather than validation. Engineers can spend more time building and less time maintaining, creating momentum across the organization.

As these improvements take hold, the effects extend further. Decision-making becomes faster and more confident. Teams can experiment and iterate without being constrained by underlying systems. And perhaps most importantly, trust starts to return. Not just in the systems, but between teams. Much of this shift comes from moving away from rigid legacy systems toward more flexible, modern foundations built to evolve with the business.

Mason touched on this in a way that’s easy to overlook: a large part of the success wasn’t just better tools. It was better communication, better alignment, and stronger relationships across the organization.

The Tradeoff Most Teams Avoid

If this all sounds obvious, there’s a reason companies still delay it. Modernizing systems is hard and disruptive. And investing in foundational systems can feel like slowing down, especially when there is pressure to continue shipping features and demonstrating progress. In many traditional organizations, legacy technology is not just outdated; it is deeply embedded in how teams operate, which makes change feel riskier than staying the same.

In reality, teams are already operating at a slower pace than they realize. As inefficiencies become normalized, workarounds are treated as part of the process. They become ingrained in team workflows rather than being questioned. Over time, these small frictions accumulate, creating a significant drag on the organization’s ability to move forward.

The decision to modernize legacy software is not simply “move fast vs slow down.” It is a choice between continuing to operate with hidden constraints or addressing them directly.

Making that shift requires alignment at multiple levels. Leadership needs to recognize the long-term value of investing in infrastructure. Teams need to understand how the work will impact their day-to-day responsibilities. And the organization as a whole needs to accept that sometimes the fastest way to move forward is to pause and fix what’s underneath.

What Teams Can Do

Although data systems are often managed by engineering teams, their impact extends across the entire organization from product and design to operations and leadership.

And everyone plays a role in shaping how these systems evolve. Before committing to a large-scale system upgrade, teams can begin making a few shifts today that often signal whether a bigger change is needed.

Ask Better Questions

The easiest place to start is with curiosity. Instead of taking data at face value, teams can dig a layer deeper by asking where it comes from, how it is structured, and whether it is reliable. These questions do not require technical expertise, but they often reveal gaps that would otherwise go unnoticed.

Pay Attention to Decision-Making, Not Just UX

Product teams are naturally focused on the end user, but internal friction is just as important. When decisions take longer than expected or feel inconsistent across teams, it is often a signal that something upstream is not working as it should. Looking at how decisions are made can be just as revealing as analyzing how a product is used.

Advocate for the Unseen Work

Foundational improvements rarely show up as exciting roadmap items, which makes them easy to deprioritize. At the same time, they are often what enable everything else to move faster and more effectively. Creating space for this kind of work requires intention and a willingness to look beyond short-term outputs.‍

Build Alignment Early

Large system changes do not happen in isolation. They depend on shared understanding and buy-in from leadership and cross-functional teams. Starting those conversations early helps surface challenges, align on priorities, and ensure that when the time comes, the organization is ready to move together.

Avoid Getting Locked In

Technology evolves quickly, and the tools that feel right today may not hold up in a few years. Rather than optimizing for a single solution, teams benefit from thinking in terms of flexibility and adaptability. Systems that are easier to change over time tend to create fewer constraints as the business grows.

Better Products Start Below the Surface

For many organizations, that friction is not a sign that the product needs to change, but that the legacy systems supporting it need to evolve. 

It is easy to focus on what users see. The interface, the features, and the overall experience are tangible and immediate. They are also only part of the story.  The most effective products are supported by systems that make it easier to build, iterate, and make decisions. These systems operate quietly in the background, but their impact is felt throughout the organization.

When those foundations are strong, teams move with greater clarity and confidence. When they are not, even the best product ideas can struggle to take shape.

For teams experiencing friction that is difficult to explain, the answer may not lie in the next feature or redesign. It may lie in the systems that support everything else. And in many cases, that is where the most meaningful progress begins.