Leveraging AI: Navigating the Opportunity Without Incurring Technical Debt

AI is the Future, and the Present too

Adopting artificial intelligence (AI) as early as feasible is crucial, but the challenge lies in avoiding the technical debt that could arise from an industry still in its infancy. Predicting the long-term future is often easier than forecasting what will unfold in the next few years. Consider Microsoft CEO Satya Nadella’s recent bold assertion that, in the future, there will only be AI and data, and that companies will no longer have to rely on proprietary applications, as all processes will be managed by an AI “genie” in the cloud.

While this vision may ultimately prove accurate, it echoes the early 1990s mantra of the now-defunct Sun Microsystems: “The Network is the Computer.” Although prescient, the timing was premature—technology had not yet caught up. For instance, transferring a three-minute song in those days via AOL could take at least five minutes. It took decades, along with advancements in fast networks and cloud computing, to fully realize Sun Microsystems’ vision.

This example underscores the critical importance of timing. However, organizations cannot afford to wait for a utopian—or dystopian—AI-driven future to materialize. Instead, they must address the opportunities and challenges AI presents today. The last thing any company wants is to be outpaced by a competitor that unveils a market-disrupting AI application.

Crafting a Strategic Approach to AI

In a previous article, I outlined key criteria for an AI strategy: flexibility, staged adoption, alignment with data, alignment with business goals, and agile governance. Building on that foundation, an effective AI strategy should leverage off-the-shelf AI infrastructure to ensure rapid market entry while avoiding overcommitting to third-party vendors for specific point solutions.

On the other hand, organizations should prioritize developing proprietary AI functionality tailored to their unique processes and services. Despite recent advancements, the AI industry remains immature, and committing too early to a specific vendor can result in substantial technical debt.

Learning from the Past

The early days of the web offer a cautionary tale. Many companies quickly adopted proprietary technologies like Vignette, a leading content management system at the time. Vignette’s complex architecture locked businesses into its ecosystem, making migration to more modern, cost-effective, open-source tools difficult and expensive. A similar risk exists today with AI.

A Pragmatic Starting Point

Organizations should begin by developing a simple yet impactful AI application that delivers unique value and competitive advantage and that follows best-practice architectural principles. This approach minimizes risk while leveraging the abundance of development tools available in an industry where vendors are currently prioritizing market share over revenue.

This isn’t about creating a mere proof of concept—you should already be doing that. Instead, it’s about moving to the next stage: building a more significant AI-based application that aligns with your business goals. Acting sooner rather than later is essential.

Building Expertise and Evolving Strategically

A core objective is to rapidly develop internal AI expertise or establish partnerships with those who have it. By starting with an evolutionary step—enhancing existing applications rather than replacing entire systems—you can strike a balance between innovation and practicality. Adding AI functionality to an existing application allows for measurable improvements without the disruption of wholesale replacement. Larger-scale transformations can wait until current investments are fully depreciated and the AI industry reaches maturity.

Future-Ready While Staying Competitive

This pragmatic approach ensures your organization remains competitive in the ever-evolving AI landscape while laying the foundation for more ambitious innovations in the future. By addressing AI opportunities strategically, you can navigate the risks of technical debt and position your organization to thrive in the long term.

What do you think? I'm interested in your perpsectives.