Three trends blocking digital transformation

From cloud computing to generative AI, digital transformation has become a critical imperative for organizations seeking to remain competitive in today’s rapidly evolving technological landscape. However, despite significant investments in the tools, platforms and talent to support these initiatives, many IT and engineering organizations find themselves struggling to achieve tangible ROI.

In this chapter, we examine three critical trends blocking digital transformation–and what leaders can do about it.

Decreasing developer productivity

According to McKinsey, the average developer spends 17.3 hours each week (opens in new tab) dealing with technical debt, bad code and maintenance tasks like debugging and refactoring instead of building. This maintenance burden creates a vicious cycle where innovation becomes nearly impossible, as teams find themselves constantly fighting fires rather than shipping new features. Developer burnout accelerates as talented engineers lose motivation working on outdated systems that offer little opportunity for professional growth or creative problem-solving. The psychological impact extends beyond individual contributors to entire teams, creating a culture of resignation where “that’s just how things work here” becomes the default response to systemic inefficiencies.

Talent acquisition and retention

As software technology evolves at an exponential pace, expertise in older systems becomes increasingly scarce, with fewer technical professionals possessing proficiency in legacy programming languages and architectures. Meanwhile, young developers graduating from computer science programs have been trained on modern languages and cloud-native architectures, making positions that require old languages increasingly difficult to fill.

Rising technical debt and security risks

According to a recent survey conducted by Protiviti (opens in new tab), nearly 70% of organizations cite technical debt as a primary inhibitor on their ability to innovate. In specific industries, the numbers are much more stark, with 82% of biotechnology and 78% of financial services organizations citing technical debt as a blocker to new feature development.

Security vulnerabilities multiply as legacy systems no longer receive patches or updates from vendors who have long since moved on to newer technologies. Each unpatched vulnerability represents a potential entry point for malicious actors, with legacy systems often lacking the monitoring and security controls that modern architectures provide by default. Additionally, compliance requirements continue to evolve while legacy systems remain static, creating an ever-widening gap between what regulations demand and what systems can deliver.

As a result of this debt, financial services organizations struggle to implement real-time fraud detection on batch-processing systems, healthcare providers cannot meet interoperability mandates with siloed databases and retailers face customer data protection requirements that legacy architectures were never designed to support. Organizations find themselves trapped between the fear of change and the escalating risk of maintaining the status quo in an environment of increasing cyber threats and regulatory scrutiny.

The root cause: legacy engineering practices

Across industries, decades-old architectural decisions continue to constrain digital transformation initiatives. Documentation is often lost over time through staff turnover and organizational changes, leaving critical business logic trapped in code that few understand and even fewer can modify safely. The original designers and implementers have often moved on, taking with them the contextual knowledge that made these systems comprehensible.

As a result, organizations develop a culture of fear around touching “working” systems, where the definition of “working” often means “we’re afraid to verify if it actually works correctly.” This paralysis manifests in risk-averse behavior where teams know change is necessary but fear the potential consequences of attempting it, leading to a status quo that becomes increasingly untenable.

There has to be a better way.