The VMware debate has reignited discussions around vendor lock-in. Discover what the situation reveals about technology dependency, business flexibility and long-term infrastructure strategy.
Technology leaders spend a lot of time thinking about the risks of adopting new platforms.
We assess costs, capabilities, security requirements and implementation challenges. We compare vendors, build business cases and try to make the best decision possible with the information available at the time.
What we don’t always spend enough time thinking about is what happens years later if we need to change direction.
That’s why the recent debate around VMware has caught the attention of so many organisations.
Following Broadcom’s acquisition of VMware, many customers have faced changes to licensing models, product packaging and commercial agreements. For some organisations, those changes have led to significantly higher costs. For others, they’ve prompted a broader reassessment of their infrastructure strategy and long-term dependence on a single platform.
On the surface, it looks like a conversation about licensing, pricing and commercial models. In reality though, I think it’s exposing something much bigger. Too many organisations are discovering just how difficult it can be to move away from a platform that has become deeply woven into their operations.
That doesn’t mean adopting VMware was a mistake. In fact, the opposite is often true.
The technologies that create the strongest forms of vendor lock-in are usually the ones that have delivered the most value.
They become trusted.
Teams build expertise around them.
Other systems integrate with them.
Critical processes begin to depend on them.
Over time, what started as a sensible technology decision becomes part of the organisation’s foundation.
And most of the time, that’s not a problem.
But then something unexpected happens…
A shift in pricing. A change in strategy. A merger or acquisition. New regulatory requirements. Suddenly, a platform that once offered stability can start to limit flexibility, and organisations find themselves facing decisions that are far more complex than they expected.
For me, that’s the real lesson from the VMware story.
It isn’t about one vendor, one platform or one licensing model. It’s a reminder that every technology decision creates dependencies, and the longer a platform remains successful, the more significant those dependencies can become.
The challenge for organisations isn’t avoiding commitment. It’s making sure that commitment never turns into constraint.
It’s easy to look at the recent conversations surrounding VMware and view them as a dispute about licensing, contracts or commercial terms.
Those factors are certainly part of the discussion, but focusing solely on them risks missing the more important lesson.
The organisations now reassessing their VMware investments are not necessarily doing so because the technology has failed. In many cases, quite the opposite is true. VMware became a cornerstone of enterprise infrastructure because it solved real problems, delivered reliability and helped businesses modernise their environments at scale.
That’s precisely why the current situation has resonated so widely.
It’s forced organisations to examine a question that extends far beyond any single vendor: how much flexibility do we actually have when circumstances change?
For years, infrastructure decisions were judged on factors such as performance, stability, functionality and cost. If a platform delivered on those requirements, it was considered a success.
But today, organisations evaluate technology through a different lens.
Business priorities change faster than they once did. Regulatory requirements evolve. Acquisitions create integration challenges. New technologies emerge. Economic conditions shift. Infrastructure strategies that looked sensible five years ago may need to support very different business objectives today.
That doesn’t mean previous decisions were wrong. It means the environment around those decisions has changed.
The VMware conversation has encouraged many organisations to take a fresh look at their infrastructure landscape and ask whether they still have the freedom to adapt as quickly as the business requires.
Technology choices rarely stay confined to the IT department.
As platforms become embedded within an organisation, they influence operational processes, security models, disaster recovery plans, staff skills, procurement decisions and future technology investments. Over time, the platform itself becomes intertwined with how the organisation functions.
At that point, changing technology is no longer simply a technical exercise.
It becomes a business challenge.
Migration projects become larger. Costs increase. Timelines extend. Risks multiply. Decisions that might once have taken weeks can take months or even years to execute.
This is where vendor lock-in becomes a strategic concern. Not because dependency exists, but because that dependency begins to limit an organisation’s ability to respond when business needs change.
The VMware situation has brought this reality into sharper focus, but the principle applies to every major technology platform. The specific vendor may differ. The underlying challenge remains the same.
One of the reasons vendor lock-in can be difficult to identify is that it rarely emerges from a failed technology investment.
In most cases, it develops because a platform has been successful.
When organisations find a technology that performs well, supports growth and earns the trust of users, they naturally invest more heavily in it. Additional workloads are moved onto the platform, new integrations are introduced and internal teams build valuable expertise around it. Over time, what began as a sensible technology choice becomes deeply embedded within the organisation.
That’s usually viewed as a positive outcome, and for good reason.
The challenge is that every layer of integration, every new process and every investment in specialist skills can make future change more difficult. By the time organisations begin evaluating alternatives, they are often assessing far more than the technology itself.
Vendor lock-in is rarely the result of a single decision.
More often, it emerges gradually through hundreds of sensible decisions made over many years.
A team adopts a platform because it solves a problem. Another system is integrated to improve efficiency. Staff receive training. Operational processes are refined around the technology. New projects build on the same foundation because it already exists and is delivering value.
None of these decisions are inherently risky. In fact, most are signs of a mature and well-managed technology environment.
The difficulty is that dependency tends to grow quietly in the background. Organisations often don’t notice how reliant they have become on a particular platform until they begin exploring what it would take to move away from it.
Standardisation is generally a good thing.
It reduces complexity, improves supportability and allows organisations to operate more efficiently. Most IT leaders actively encourage standardisation because maintaining dozens of different technologies often creates unnecessary cost and risk.
Dependency is VERY different.
An organisation can standardise on a platform whilst still retaining flexibility. Dependency occurs when changing direction becomes so difficult, disruptive or expensive that realistic alternatives begin to disappear.
The distinction matters because many organisations assume the two concepts are interchangeable.
They are not.
One creates efficiency. The other reduces choice.
The true test of flexibility isn’t whether an organisation can operate effectively today. It’s whether it can adapt when circumstances change tomorrow.
As long as a platform continues to meet expectations, questions about dependency rarely attract much attention. There’s little incentive to revisit decisions that appear to be working well.
That changes when organisations are faced with a significant shift, whether that’s a pricing change, a strategic realignment, a merger, new compliance requirements or the emergence of alternative technologies.
Suddenly, assumptions that have gone unchallenged for years are brought into the spotlight.
The recent VMware discussions have created exactly this kind of moment. They haven’t introduced the concept of vendor lock-in. They’ve simply prompted many organisations to measure it for the first time.
When vendor lock-in is discussed, the conversation usually centres on cost.
That’s understandable. Licensing changes are easy to quantify, procurement teams can model the financial impact and leadership teams can quickly see how technology spending might be affected. It’s often the first place organisations look when evaluating the risks associated with a particular platform.
In my experience, however, the financial implications are rarely the most significant.
What concerns me far more is the impact vendor lock-in can have on an organisation’s ability to respond when priorities change. Technology exists to support the business, yet there comes a point where deeply embedded platforms can begin shaping the options available to the business itself. When that happens, the relationship starts to reverse.
That’s where the real risk begins to emerge.
Few organisations welcome unexpected increases in technology expenditure, particularly when budgets are already under pressure.
Yet higher costs don’t automatically create a strategic problem. Businesses deal with changing costs all the time. Markets shift, suppliers adjust their pricing and economic conditions evolve. Whilst those changes may be frustrating, they’re often manageable.
The more difficult question is what happens when an organisation no longer feels it has meaningful alternatives.
If moving to another platform would require years of planning, extensive retraining, major operational disruption or substantial migration costs, then the discussion quickly moves beyond pricing. At that stage, organisations aren’t simply deciding whether they want to change. They’re evaluating whether changing is realistically possible.
That’s a very different conversation.
Most organisations operate in environments that look very different today than they did five years ago.
New customer expectations have emerged. Regulatory requirements continue to evolve. Artificial intelligence is reshaping technology roadmaps. Business leaders are under growing pressure to improve efficiency whilst remaining agile enough to respond to whatever comes next.
Against that backdrop, flexibility has become one of the most valuable characteristics an organisation can possess.
The challenge is that flexibility isn’t something you can buy at the point you need it. It’s usually the result of decisions made years earlier.
I’ve seen organisations discover that launching a new initiative, integrating an acquisition or adopting a different operating model is far more difficult than expected because a critical part of their technology estate was never designed with change in mind. The platform itself may still be performing exactly as intended, but the business around it has moved on.
That’s why I tend to view vendor lock-in as a strategic issue rather than a technical one.
The greatest cost isn’t necessarily what an organisation pays today. It’s the opportunities that become harder to pursue tomorrow.
There was a time when infrastructure decisions were largely viewed as technical matters.
As long as systems remained available, users could access the tools they needed and the business continued to operate, most discussions around platforms and architecture stayed within the IT function. Leadership teams understandably focused their attention elsewhere.
That’s becoming increasingly difficult to do.
Today, infrastructure choices influence everything from operational resilience and cybersecurity to acquisition strategies, digital transformation programmes and the adoption of emerging technologies. Decisions that might once have been viewed as purely technical can now shape an organisation’s ability to execute its broader business objectives.
As a result, conversations about infrastructure are no longer confined to server rooms, data centres or IT departments. They’re becoming leadership conversations.
Every organisation wants the ability to respond quickly when circumstances change.
Whether that’s entering a new market, integrating an acquisition, launching a new service or responding to changing customer expectations, agility has become a competitive advantage in its own right.
Technology plays a significant role in determining how quickly those changes can happen.
When infrastructure supports flexibility, organisations can adapt with greater confidence. When technology environments become overly complex or tightly coupled to specific platforms, even well-intentioned strategic initiatives can take longer to deliver than expected.
This doesn’t mean organisations should avoid committing to technology platforms. That’s simply not realistic. It does mean leaders should understand how those commitments may affect future options, particularly when making decisions that are expected to remain in place for many years.
One of the most interesting aspects of the current VMware discussion is that it’s taking place at a time when many organisations are also exploring artificial intelligence, automation, advanced analytics and broader cloud adoption.
In other words, businesses aren’t just evaluating where they are today. They’re thinking about where they want to be next.
The ability to adopt new technologies is often influenced by decisions that were made long before those technologies existed. Infrastructure can either create a strong foundation for future innovation or introduce constraints that make change slower, more expensive or more complex than it needs to be.
That’s why infrastructure strategy deserves a place in wider business discussions.
The choices organisations make today won’t just affect performance, resilience and cost. They’ll also influence how easily the business can adapt to opportunities that haven’t even emerged yet.
The VMware discussion has generated plenty of opinions about licensing models, commercial strategy and infrastructure platforms.
Whilst those debates are likely to continue, I believe the most valuable lessons sit elsewhere.
This isn’t really a story about one vendor making changes to its commercial approach. It’s a reminder that every significant technology investment creates dependencies, and that organisations should understand those dependencies long before they become a problem.
The goal isn’t to eliminate risk entirely. That’s impossible. Every platform, supplier and technology decision involves a degree of commitment. What matters is understanding where that commitment exists and how it could affect future choices.
Most organisations have a reasonable understanding of the technologies they use.
Far fewer have a clear picture of the dependencies those technologies have created over time.
A platform may support critical business processes, underpin security controls, host essential applications or provide the foundation for disaster recovery planning. In many cases, those dependencies have developed gradually as the organisation has grown and evolved.
There’s nothing inherently wrong with that.
Problems tend to arise when organisations only discover the extent of those dependencies at the point they’re considering a significant change. By then, decisions are often being made under pressure and with fewer options available than expected.
Understanding where dependency exists doesn’t mean change is inevitable. It simply allows organisations to make future decisions with greater clarity.
One of the most common mistakes I see is treating exit planning as something that can be addressed later.
In reality, the easiest time to think about how you might leave a platform is when you’ve only just adopted it.
That doesn’t mean creating detailed migration plans for every technology investment. In most cases, that would be unnecessary. It does mean asking sensible questions about data portability, integration complexity, contractual commitments and the practical challenges that might arise if business requirements change in the future.
The organisations that navigate change most successfully aren’t always those with the newest technology or the largest budgets.
More often, they’re the organisations that have preserved optionality.
They’ve thought ahead, documented dependencies and retained enough flexibility to make decisions on their own terms rather than having decisions imposed upon them.
Not every system requires the same level of flexibility.
Some platforms are so central to business operations that a degree of long-term commitment is both expected and entirely reasonable. Attempting to optimise every technology decision for maximum flexibility can introduce unnecessary complexity and cost.
The key is understanding where flexibility delivers the greatest value.
For some organisations, that may be around data portability. For others, it may be application architecture, cloud strategy or the ability to integrate emerging technologies as business requirements evolve.
The important thing is making those decisions deliberately.
Vendor lock-in becomes far less concerning when organisations have consciously evaluated the trade-offs and understand exactly where they’re choosing to make long-term commitments.
If there’s one lesson organisations should take from the VMware discussion, it’s that vendor lock-in isn’t always the result of poor decision-making.
In many cases, it’s the consequence of good decisions delivering value over a long period of time.
Successful platforms naturally attract further investment. Teams develop expertise. Processes evolve. Integrations expand. Over time, technology becomes woven into the fabric of the organisation. That’s often a sign that a platform has been doing exactly what it was intended to do.
The challenge arises when those dependencies are no longer fully understood.
Businesses need technology partners. They need platforms. They need suppliers. No organisation can operate without making commitments, and attempting to avoid every form of dependency would create more problems than it solves.
What matters is maintaining awareness of the trade-offs.
The organisations best positioned for the future won’t necessarily be those with the newest infrastructure or the most ambitious technology strategies. They’ll be the organisations that understand where they’ve become dependent, where they still have flexibility and where they may need more options in the years ahead.
That’s why I don’t see the VMware story as a warning about a particular vendor.
I see it as a reminder that technology decisions don’t just shape the systems we use today.
They shape the choices available to us tomorrow.
Written By:
Why Pay For A Modern System Your Teams Can’t Run Themselves?
The Infrastructure Mistakes Almost Everyone Makes First Time Round
Ready For More?
