Daniel Jabaraj is CEO of Syncfusion, leading a global team that builds developer tools and enterprise software.
Move fast or get left behind. The same message is reinforced in every major technology shift. Most companies choose to move fast, but very few succeed in the transition.
Decades of platform transitions have followed this pattern, including mainframe to PC, desktop to web and mobile and on-premises to cloud. That pattern is currently playing out again with AI. Gartner predicted that at least 30% of generative AI projects will be abandoned after proof-of-concept, citing the organizations’ inability to connect to a clear business purpose.
MIT researchers found that 95% of organizations are getting zero return from their AI pilot programs, despite $30 billion to $40 billion in enterprise investment. That same report notes that the delta between cost and success rates isn’t due to model quality or the technology itself, but rather the approach. In my experience, technology is rarely the problem.
The Failure Isn’t Technical
When companies struggle through a tech transition, the post-mortem usually focuses on the wrong things: the tools chosen, missed timelines or employees themselves. But the root causes run much deeper.
The most common reason for failure is, in my mind, also the most underappreciated. Companies tend to define themselves by their method (a specific platform or a category of product, for example) rather than by their mission (the underlying value they exist to deliver).
Companies that confuse the two have nowhere to go when the methods get disrupted. Harvard Business Review identified this in a study of digital transformation failures: Organizations “put the cart before the horse, focusing on a specific technology rather than doing the hard work of fitting the change into the overall business strategy first.”
I’ve watched this play out across 25 years in the software industry. A company whose mission is enabling faster, easier software development can survive any and every platform shift. A company focused on one platform rather than its overarching mission has no answer when that platform becomes obsolete. That’s why it’s important to focus on the end goal (faster development) over the means (a specific platform or delivery model).
Confusing mission and method doesn’t fail companies on its own; other factors compound it. For one, there is a strong, natural affinity to the status quo. What’s working today might feel safer than what might work tomorrow. Fear of lost revenue can overpower the ability to see long-term benefits and opportunities. Misunderstanding the new tech or misjudging its change of pace is equally dangerous: Some organizations jump too early on technology that isn’t ready; others wait too long and lose the window to act on their own terms. And almost universally, companies underestimate the work required for a real transition.
The result is a lot of motion and very little progress, which is exactly what the MIT researchers I mentioned earlier found.
Is It A Headwind Or A Tailwind?
Understanding why most transitions fail only solves half of the equation. The other half requires a look at posture—how is leadership framing this change?
The same technology change can be a headwind that slows progress, or it can be a tailwind that accelerates it. Companies that treat AI as a threat to what they’ve built may spend the next several years defending their business while relevance erodes. Companies that ask questions like “How does this accelerate the value we’re already delivering?” may instead emerge on top.
This question—headwind or tailwind—only has a clear answer if your mission is clear, which is why it’s so important to know the difference between method and mission. It’s also urgent, as the market won’t reward hesitation. The leaders still standing after 30 years of platform shifts share something in common: They get excited about change, not simply because they’re optimistic by nature. It’s because they’ve clearly defined their business by why they do it; they refuse to conflate the “why” with the “how.”
What The Exceptions Do
The companies that I’ve seen come through transitions successfully generally make three practical moves.
The first move is to define your mission at the right altitude. It should be broad enough to survive changes in method, yet specific enough to mean something. This isn’t supposed to be an abstract exercise. Ask yourself the following: If the technology you’ve built your company around were to disappear tomorrow, would your mission—your reason for existing—still hold true?
The second move involves how your organization thinks about new technology. The companies that navigate transitions well tend to see each new wave of tech not as a replacement, but as an additive layer, building on accumulated expertise. Seeing AI as a replacement leaves survival as the only goal. Seeing it as an additive layer can open the door to applying what you already know in a new way.
Data around productivity supports this framing. A joint study by GitHub and Cornell found that developers using AI assistance completed tasks 55% faster. In the study, AI served as an amplifier—developers moved faster. And for companies whose mission is tied to developer productivity, that number is confirmation.
The third move relates to timing: Drive internal disruption before the market’s external pressure forces your hand. Most organizations wait too long for better tools or clearer signals. By the time they make the move, the window to act on their own terms has closed.
25 Years In
As AI accelerates everything, the temptation is to treat this moment as purely technical. But the companies that come through will be the ones whose customers and partners trust them on the other side.
That’s what 25 years in this industry has taught me. The transitions we navigated successfully weren’t won on technology alone. The transitions were won because we stayed clear on why we existed, moved before we were forced to and gave customers reasons to stay with us through any uncertainty.
The next five years will test a lot of organizations on all three. The companies that treat this moment as a technology problem will spend those years solving for the wrong thing.
Forbes Technology Council is an invitation-only community for world-class CIOs, CTOs and technology executives. Do I qualify?
