The Dynamic Capabilities: The Core of Modern Strategic Management

Dynamic capabilities is one of the most cited ideas in strategic management and one of the most loosely used. In its careless form it becomes a synonym for agility, and the article writes itself: change is constant, companies must adapt, here are five companies that adapted.

The framework is more specific and more useful than that. It makes a precise claim about where competitive advantage comes from when the environment will not stay still, it identifies the organisational routines that produce it, and it carries a real cost that makes it the wrong choice in some industries. It also attracts a serious academic criticism that is worth taking seriously rather than ignoring.

The problem it was invented to solve

Through the 1980s and early 1990s, the dominant explanation of competitive advantage was the resource-based view. A firm outperforms because it controls resources that are valuable, rare, difficult to imitate and hard to substitute. The logic holds and explains a great deal.

Its weakness is that it is static. It explains why a company is ahead at a given moment, and says little about how a company stays ahead when the conditions that made the resource valuable change. A resource that is rare and inimitable can also become irrelevant, and the theory has no account of that.

David Teece, Gary Pisano and Amy Shuen proposed the answer in 1997: the durable advantage is not the resource itself but the capacity to keep reconfiguring the resource base as conditions move. That capacity is what dynamic capabilities names.

Ordinary and dynamic capabilities

Teece's own distinction is the one most often dropped, and it is the one that makes the framework operational.

Ordinary capabilities are about doing things right. Manufacturing to spec, closing the accounts accurately, running an effective support desk. They can be benchmarked against best practice, they can often be bought or outsourced, and they are necessary. A company with weak ordinary capabilities will fail regardless of how well it reads the market.

Dynamic capabilities are about doing the right things. Deciding what the company should become and moving resources to make that possible. They are firm-specific, they cannot be purchased, and they do not follow from operational excellence.

The distinction matters because the two are frequently confused in practice. A company running an efficiency programme, standardising processes and cutting cycle times is strengthening ordinary capabilities. That is worth doing and it will not help at all if the market it is efficient in is disappearing.

The three components, and the routines underneath them

Sensing, seizing and transforming are the headline. The useful part is what sits underneath each, because a capability described in the abstract cannot be built. Teece's term for the underlying routines is microfoundations.

Sensing

Detecting shifts in technology, customer behaviour, competitive structure and regulation early enough to act on them.

The routines that produce it: research investment directed at questions rather than at products; systematic contact with lead users, who experience a need before the mass market does; competitor tracking that covers adjacent industries rather than only direct rivals; and, critically, a path by which an observation made at the edge of the organisation reaches a decision-maker without being filtered by someone whose unit the observation reflects badly on.

That last routine is organisational rather than analytical, and it is the one most often missing.

Seizing

Committing resources once something has been sensed. Investment, business model design, and the willingness to damage an existing revenue stream.

The routines: an investment process that can fund an option before the business case is provable; decision rights held closely enough that a commitment can be made in weeks; and incentive structures that do not punish an executive for cannibalising their own unit's revenue.

This is where companies fail, and it is not usually a failure of information. Kodak developed the first digital camera. Blockbuster was offered Netflix. Incumbent retailers understood e-commerce years before it displaced them. In each case the organisation sensed accurately and could not act, because acting meant harming something profitable that someone senior was measured on.

The popular telling of these stories as blindness is comfortable and wrong. They are governance failures, which is a harder problem than perception and a more tractable one.

Transforming

Continuously reconfiguring assets, structures and incentives so that the organisation remains able to sense and seize.

The routines: periodic reallocation of capital and people between units rather than incremental adjustment of last year's allocation; disciplined divestment of assets that no longer fit; structural design that keeps decision units small enough to move; and the deliberate management of what Teece calls asset orchestration, which is the pairing of assets that are more valuable together than separately.

Transformation is continuous rather than episodic. An organisation that reconfigures only during crises has, by definition, already been overtaken by the change it is responding to.

The criticism, stated fairly

The most serious objection to dynamic capabilities theory is that it risks being circular. If a company thrives we say it had dynamic capabilities; we identify dynamic capabilities by studying companies that thrived. On that reading the theory renames the outcome and explains nothing. Arend and Bromiley put the case sharply, and it applies with full force to the popular version of the idea.

Two responses hold. The first is that the microfoundations are specifiable in advance: it is possible to establish whether a company has a route from customer observation to resource decision, and how long it takes, without knowing anything about its performance. The second is that a serious version of the theory has to allow a well-equipped firm to fail anyway, because capabilities improve the odds rather than determine the outcome.

The practical consequence is a rule for reading any claim about this framework: if the evidence consists entirely of successful companies described after the fact, treat it as illustration rather than argument.

When the framework is not worth its cost

Dynamic capabilities are expensive. They require slack in the system, tolerance for investments that will not pay off, and a standing willingness to disrupt arrangements that currently work. All three are costly and none is free of organisational friction.

In a stable environment, that expenditure loses. Where technology moves slowly, customer preferences are durable and regulation is settled, a company that invests in ordinary capabilities and operational efficiency will beat one that spends the same money on optionality. The framework earns its cost where the rate of change is high enough that today's advantage will not survive the decade, which is many industries and not all of them.

Assuming otherwise produces a specific failure: perpetual reorganisation in a business that would have been better served by getting very good at one thing.

Diagnosing what you actually have

Assessment by intent is worthless, because every organisation believes it is adaptive. Assessment by history is harder to flatter.

• When did the company last stop something profitable because it no longer fitted the direction? If the answer is never, the seizing capability is untested.
• How long between a market signal being visible and a resource decision being taken? Measure it on a real example rather than estimating.
• What proportion of the budget moved between units in the last cycle? Allocation that mirrors last year's allocation indicates a reconfiguration capability that exists only on paper.
• How many current products or services did not exist three years ago?
• Where does an observation from a customer-facing employee go, and who can stop it?

Five answers drawn from what actually happened will tell you more than any capability assessment framework.

In smaller organisations

The framework is usually discussed at enterprise scale, and the mechanism differs meaningfully below it.

A small company has natural advantages in sensing, because founders talk to customers without a reporting layer in between, and in seizing, because there is little internal politics and little profitable legacy to defend. Its binding constraint is capacity: with limited resources, seizing one opportunity means declining several others.

So the discipline inverts. For a large organisation the hard part is mobilising against inertia. For a small one it is choosing, and refusing. The characteristic failure of a small company is not that it missed the shift but that it pursued four of them at once.

The point

Dynamic capabilities is a claim about where advantage comes from when the environment will not hold still: not from the resources a company controls but from its capacity to keep reconfiguring them. The framework becomes useful at the level of routines rather than at the level of the three headline words, and the routines are organisational rather than analytical. Sensing is largely a question of information flow, seizing of governance and incentives, transforming of allocation discipline.

Most failures attributed to blindness were failures of will, in organisations that saw the change clearly and could not bring themselves to damage what was working.

At go:lofty we work on strategic capability as part of the wider growth architecture, on the routines that determine whether an organisation can act on what it already knows.

Talk to us about the gap between what your organisation sees and what it does.