The Cost of Moving Too Fast: When Innovation Outpaces the Foundations of Technology

The Cost of Moving Too Fast - cracked building foundation - Hero 3Sixty Insights Image

From wireless networking and cloud computing to AI-driven development, the pressure to innovate faster is creating a familiar problem. Organizations are advancing technology faster than their ability to manage the risks and operational consequences that come with it.

There is an uncomfortable pattern emerging across the technology industry. Organizations are moving faster than ever to develop, deploy, integrate, and adopt technology, driven by the pressure to keep pace with competitors and capitalize on emerging opportunities.

But there is a question that deserves more attention: Are organizations moving faster than their ability to manage what they are building?

Look at what has happened over the past several weeks. Microsoft experienced a significant disruption to Outlook, Teams, and other services. The FAA experienced a nationwide ground stop following problems with its telecommunications infrastructure. United Airlines encountered its own technology outage, and Apple and Marriott have also experienced service disruptions.

The banking industry hasn’t been immune either. On November 16, a software bug within JPMorgan Chase’s systems delayed transactions and created ripple effects for customers attempting to transact with other financial institutions. In October, a Google Cloud data center power failure disrupted banking, payment, trading, and risk-management services across parts of the UK financial sector.

These incidents have different technical causes, but they point to a common concern: organizations are increasingly dependent on complex, interconnected technology environments where a failure in one component can quickly affect thousands or even millions of customers.

And this isn’t a new problem. We’ve been here before.

We’ve seen this movie before

Think back to the early days of wireless networking and cloud computing. Organizations rushed to capitalize on the opportunities these technologies presented, often prioritizing speed of adoption over the security and operational practices needed to support them.

The result was an environment where vulnerabilities were introduced, sometimes with consequences that extended well beyond the organizations responsible for them.

One of the most memorable examples was the TJX data breach.

A parking lot, a wireless access point, and 45.7 million compromised accounts

In 2005, hackers began exploiting weaknesses in the wireless networks used by TJX, the parent company of T.J. Maxx, Marshalls, and HomeGoods.

The approach was surprisingly straightforward. Attackers reportedly parked outside a Marshalls location with a laptop, antenna, and specialized software, identifying weaknesses in the store’s wireless network and exploiting its outdated Wired Equivalent Privacy (WEP) encryption.

From there, they gained access to the retailer’s network and eventually reached systems processing customer transactions. When TJX initially disclosed the incident in 2007, it reported that approximately 45.7 million payment card accounts had been compromised, while subsequent estimates suggested the number could have reached 94 million.

What makes this incident particularly relevant today is that the vulnerabilities weren’t entirely unknown. WEP had already been recognized as inadequate, and stronger security standards were available, but the transition and supporting safeguards hadn’t been implemented effectively enough.

The attackers didn’t need to invent a sophisticated new way to break into a system. They simply found a weakness that already existed and took advantage of it.

Today’s technology race is creating familiar challenges

Fast-forward to today, and the technology landscape looks considerably different. Cloud computing has become foundational to enterprise operations, artificial intelligence is changing how software is developed, and AI-assisted tools are allowing organizations to build and deploy applications at unprecedented speeds.

The opportunities are significant, but so are the risks when development and deployment outpace the discipline required to manage them.

Consider the recent disruptions across Microsoft, the FAA, and the banking industry. Microsoft’s outage followed an issue associated with an earlier network capacity upgrade, while the FAA experienced instability in its legacy telecommunications infrastructure during a period involving network equipment replacement. JPMorgan Chase attributed its transaction delays to a software bug in its internal hardware systems.

These weren’t all the result of the same problem, and they weren’t necessarily caused by the same decisions. However, they demonstrate how changes, technical debt, insufficient safeguards, and increasingly complex dependencies can create problems that extend far beyond the original point of failure.

The banking industry provides another particularly important perspective. Financial institutions are among the most heavily regulated and technologically sophisticated organizations in the world, yet even they experience operational disruptions that affect customer access, payments, and critical business functions.

The UK’s Financial Conduct Authority has also identified change management, third-party failures, and hardware and software issues among the leading contributors to operational incidents reported by retail banks. This reinforces the importance of managing technology changes and dependencies rather than simply accelerating their introduction.

Security and operational resilience cannot become afterthoughts. Organizations need to account for vulnerabilities, testing, monitoring, and recovery before problems occur, rather than relying on reactive measures once something breaks.

The customer perspective is getting lost in the race

There is another dimension to this conversation that deserves attention: how much of the innovation organizations are racing to deliver is actually being used?

We spend considerable time discussing new functionality, AI capabilities, integrations, and product roadmaps, while technology providers compete to demonstrate how quickly they can deliver more. But what about the customers who are still trying to realize the value of what they already own?

Research conducted by 3Sixty Insights in collaboration with Insperity explored how organizations are using their existing HR technology and where gaps remain between technology investments and actual utilization. The findings reinforce an important consideration for the broader technology industry: organizations can make significant technology investments without fully realizing the value of the capabilities already available to them.

If customers are still struggling to fully utilize the technology they already own, why is the industry so focused on accelerating the introduction of even more functionality?

This isn’t an argument against innovation. It’s an argument for being more deliberate about what we build, how we deploy it, and whether customers are equipped to realize its value. Technology providers need to think beyond how quickly they can introduce the next feature, while enterprise buyers need to consider whether their organizations are prepared to adopt, integrate, secure, and operationalize what they purchase.

More technology doesn’t automatically translate into more progress.

Speed needs to be balanced with operational discipline

None of this suggests organizations should stop innovating or deliberately slow technological advancement. Speed has tremendous value, but speed without discipline can create an entirely different set of problems.

Organizations need to ensure their development and deployment practices include fundamental safeguards, including security by design, thorough testing, infrastructure and dependency management, operational readiness, and clear accountability. They also need to consider whether customers and internal teams have the resources and capabilities to successfully adopt and manage what is being introduced.

These aren’t revolutionary concepts. They have been established best practices for decades, yet they can easily get lost in the pressure to deliver more, faster.

As we move further into an era of AI-assisted and increasingly autonomous technology, that pressure isn’t going away. If anything, it will intensify, making it even more important that organizations invest in the foundations required to support what they are building.

The TJX breach reminds us that vulnerabilities don’t always come from sophisticated attacks or entirely unknown weaknesses. Sometimes they come from known problems that organizations haven’t addressed, safeguards that haven’t been implemented, or transitions that haven’t been completed.

Innovation is important. Speed is important. But neither matters much if the technology we’re building creates more problems than it solves.

Perhaps it’s time for the industry to spend a little less time asking how quickly we can build the next thing and a little more time asking whether we’ve built the right foundation to support it.

Share your comments: