Why does the same change hold in one organization and stall in another?

Abstract banner of connected technology and research elements in blue and grey

Technology Differentiates Only When the Organization Changes Around It

Most enterprises adopt new technology to run what they already do a little better. Few use it to build something competitors cannot copy. The difference is rarely the technology. It is whether the organization is willing to be rebuilt around it.

The prevailing view treats technology adoption as a sequence: choose the platform, deploy it, then manage the change. That view explains why projects get funded and delivered. It does not explain why so many of them end in efficiency gains rather than differentiation. I would argue that the outcome is decided less by what a technology can do than by the configuration it enters: the culture, structure, talent, processes and metrics that determine whether its capabilities become consequential.

Three modes of adoption

Enterprises typically adopt new technology in one of three modes. Each asks a different question of the organization, and each produces a different kind of value.

  1. Business as usual. The technology makes existing business and technology operations run better. The operating model stays as it is; processes are optimized and refined.
  2. Incremental value creation. The technology adds value on top of the existing business model: enhanced offerings, better customer experience and, in some cases, new revenue streams that still rely on the current core.
  3. Net new differentiating value. The technology becomes the basis of a new business model or market. This mode changes what the organization is, not only how well it runs.
Business as usualIncremental valueNet new differentiating value
OpportunityOptimize existing operationsEnhance existing offerings, open adjacent revenueCreate new business models, enter new markets
Value createdEfficiency, lower costIncremental revenue, better customer experienceCompetitive advantage that is hard to copy
RiskLow, minimal disruptionModerate, possible cannibalizationHigh, real possibility of failure
What it demands of the organizationWillingness to change routinesBalancing new gains against the core businessTransformation of culture, structure, talent, process and metrics
Reading the table: risk and organizational demand rise together. The third column is expensive not because the technology is harder, but because the organization has to change more.

Why enterprises settle for the first two modes

Enterprises gravitate to business as usual and incremental value because both fit existing practices, budgets and accountability. They improve efficiency and reduce cost with limited risk, and they can be measured with the metrics the organization already trusts. That is precisely their limit. A technology deployed inside an unchanged configuration tends to reproduce that configuration more efficiently. It rarely produces a position competitors cannot reach.

The third mode is harder because it asks the organization to change the conditions under which the technology operates. The chain runs like this:

  1. A new capability is introduced into an existing organization.
  2. Existing metrics reward short-term financial performance, so the capability is directed at cost and efficiency.
  3. Existing structures route decisions through the current business lines, so new models compete with the core for attention and budget.
  4. The capability is absorbed into the current operating model.
  5. The result is optimization, regardless of what the technology could have enabled.

What differentiation looked like in practice

Two familiar cases show the third mode, and both show that the technology was only part of the story.

Amazon Web Services. Amazon turned infrastructure capability built for its own e-commerce operations into a separate business. AWS reported net sales of $128.7 billion in 2025 (Amazon, Q4 2025 results). The capability existed inside many large enterprises. What was rarer was the decision to treat internal infrastructure as a product, with its own structure, customers and economics, and the willingness to sell it to competitors.

Netflix. Netflix moved from DVD rental to streaming and then to original content production. Streaming technology was available to others. The difference lay in a willingness to disrupt its own business while that business was still working, and to reorganize investment and capabilities around the new model. The move forced traditional media companies to rethink their own distribution models.

In both cases, the differentiating asset was not the technology considered on its own. It was the configuration: the technology combined with a business model, an organizational structure and a set of decisions that competitors were unwilling or unable to make.

The configuration that makes the third mode possible

Pursuing net new value requires change across six elements. They matter less as a checklist than as a system, because each one constrains the others.

  • Culture determines whether experimentation and failure are tolerated. Without that tolerance, new structures and metrics are treated as exceptions to be closed down.
  • Structure determines where decisions are made. Hierarchies built around the current business route new models back into it; cross-functional teams with their own authority give them room to develop.
  • Talent determines who can translate capability into a business. Technical skill is necessary, but so are problem-solving and entrepreneurial judgment.
  • Process determines the speed of learning. Agile and DevOps practices shorten feedback loops, but only when processes are tied to strategic goals rather than to activity.
  • Metrics determine what survives. If new initiatives are measured on short-term financial return, they will lose to the core. Customer outcomes, market share growth and new revenue streams give them a fair test.
  • Technology determines what is possible: flexible, scalable infrastructure, data and analytics. It is necessary, and on its own it is not sufficient.

What follows for technology leaders

The practical implication for CIOs and CTOs is to treat the adoption mode as an explicit decision, not an outcome discovered after deployment. For each significant technology investment, ask which mode it is meant to serve, and whether the culture, structure, talent, process and metrics around it support that mode. Where the ambition is differentiation and the configuration is business as usual, the investment will most likely deliver optimization.

Business as usual and incremental value still matter; most technology spending should and will serve them. The point is not to abandon them, but to stop expecting them to produce differentiation. Technology is not a support function. Whether it becomes an engine of growth depends on the configuration it is allowed to reshape.

Which of your current technology investments is labeled transformation but configured for business as usual?

Discussion

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Mentor Cana, PhD

About Mentor Cana, PhD

Telecom and hi-tech strategist and former Gartner VP analyst. Mentor writes on why the same change holds in one organization and stalls in another: how culture, technology, processes, metrics, talent and structure shape one another, and the wider business and societal ecosystem around them.

More about Mentor · LinkedIn · Start a conversation

Get Signals by email

What matters for leaders in telecom and hi-tech, with links to the latest pieces. Sent periodically, with no sales pitches.

More like this