A company can have exceptional engineers, a respected brand or a faster process and still lack a durable competitive advantage. A strength matters strategically only if it helps deliver something customers value relative to their alternatives—and if competitors cannot readily match or replace the result.
Consider a hypothetical retailer with unusually fast fulfillment. Speed may win orders, but competitors might buy similar warehouse technology and delivery capacity. The more revealing questions concern the choices behind that speed: Which customers does the retailer serve? How broad is its product range? Where does it hold inventory? What service promises does it decline to make? Those decisions could make fast delivery either a feature rivals can purchase or the result of a configuration they would have to rethink their businesses to match.
Start the strategy discussion with a harder question than "What are we best at?" What do our choices make us unusually good at delivering, and what would a rival have to change to offer customers an equally attractive result? That shifts attention from the strength itself to the choices that make it valuable.
A strength is not yet an advantage
Competitive advantage is relative. A capability matters when it helps a company create value customers choose or deliver comparable value at a lower cost than relevant competitors. Excellence at something customers do not sufficiently value is not an advantage. Neither is excellence that rivals can readily match.
Michael E. Porter's Competitive Strategy: Techniques for Analyzing Industries and Competitors and Competitive Advantage: Creating and Sustaining Superior Performance connect a company's competitive position with the activities through which it creates value and incurs cost. Those are two distinct tests for a claimed strength. Where does it place the company relative to competitors, and how does it improve the economics or value of the offering? An internal list of strengths cannot answer either question on its own.
In “What Is Strategy?”, Porter distinguishes operational effectiveness from strategy. Better execution can improve performance, but a practice available to everyone may not protect the gains. A distinctive position depends on choices, trade-offs and fit among activities. That does not make operational excellence optional. It means executing an activity well and building a position that is difficult to reproduce are different achievements.
Jay Barney’s resource-based analysis adds a necessary qualification. A resource’s potential to support sustained advantage depends on its value and rarity, as well as the difficulty of imitating or substituting for it. Not every meaningful advantage has to begin with an elaborate activity system: a protected or scarce asset may matter greatly. But Barney’s test makes the question sharper. What prevents a rival from acquiring, developing or working around the strength?
How a position becomes a system
Roger L. Martin and A.G. Lafley connect aspiration, where to play, how to win, capabilities and management systems in Playing to Win. That sequence makes capabilities answerable to a chosen competitive position, rather than an inventory of current strengths.
Gary Hamel and C.K. Prahalad's Competing for the Future adds the question of renewal: which capabilities will the next position require? Time spent building a strength does not ensure that customers will continue to value it.
At OutcomesLab, we bring these questions together through Advantage Architecture, a framework with four connected parts:
- Distinctive choice. Name the customers, needs and competitive position the company intends to serve. State what it will not pursue. Without boundaries, almost any strength can be called strategic.
- Enabling capabilities. Identify what the company must repeatedly do well to deliver that position. Separate capabilities essential to the promise from useful ones rivals can also obtain.
- Activity fit. Map how product design, channels, operations, service, incentives and other activities support those capabilities and one another. Identify contradictions as well as reinforcing links.
- Reinforcement over time. Invest in the connected configuration, learn from repeated work and revise its components when the market changes.
The framework makes the explanation specific. How does a choice require a capability? Which activities make that capability effective? Does repeated use improve the result? "We have great people" may be true, but it leaves those connections unexplained. The framework helps test a strategic argument; it does not guarantee superior returns.
Return to the hypothetical retailer. A narrow range could make demand easier to forecast, allowing inventory to sit closer to customers and fast delivery to become more economical. Broad customization could undermine that arrangement. These are relationships to investigate: leaders still need evidence about customer preferences, costs and competitors' alternatives before concluding that the configuration creates an advantage.
Test the result, not just the components
A connected system may be harder to imitate than a standalone practice. A rival could need several complementary changes rather than one purchase. Those changes could conflict with its existing model: a competitor committed to broad assortment, for example, may have reason not to adopt the hypothetical retailer’s narrower range. And when activities reinforce one another, the contribution of any single activity may be difficult to isolate.
These are possible barriers, not proof that complexity creates value. An elaborate operating model can be expensive without improving what customers receive. Nor does a competitor have to copy the original system. It may meet the same need through a different mix of technology, partners or channels.
Then apply the proposed OutcomesLab System Replaceability Test. Start with the apparent strength and ask:
- What customer outcome does it improve, relative to which alternatives?
- Which other activities must work for the strength to produce that outcome economically?
- Which activities could a rival copy, buy or hire independently?
- What choices would a rival have to change, and what would it give up, to match the complete result?
- Could a rival satisfy the same customer need without reproducing the system?
The final question guards against a common mistake in strategic reasoning. A company can make its own way of working difficult to copy while leaving the customer outcome easy to replace. Defensibility requires attention to substitutes for the result, not just imitation of the process.
The test can also expose a valuable but vulnerable strength. If customers value a capability but it requires few complements, involves no meaningful trade-off and has an accessible substitute, leaders should manage it as an important operating asset without assuming it will protect future returns. The distinction does not make the asset expendable; it changes what leaders should expect from it.
When the system becomes difficult to change
A patent, scarce resource, regulated position or network may confer meaningful advantage for a period without an intricate activity system. The claim that every advantage must be a system would be too strong. Leaders should instead ask what protects the asset, how long that protection may matter and what other activities are needed to benefit from it. Holding a patent, for instance, does not by itself determine how effectively a company develops, produces or brings an offering to customers.
There is an opposite danger in tightly fitted systems: they can be hard to change. If a new channel, product or technology requires several linked activities to change together, yesterday’s coherence can slow tomorrow’s response. Trade-offs that once protected a position may become liabilities when customer needs shift.
David J. Teece, Gary Pisano and Amy Shuen’s work on dynamic capabilities emphasizes coordinating and recombining assets under changing conditions. It supports a boundary on the system argument, not a demand that every company constantly overhaul its strategy. Leaders need to distinguish a value-creation logic worth preserving from routines that no longer serve it.
At OutcomesLab, we use Coherence Premium to describe the potential benefit of reinforcing choices. That is no reason to retain a choice after it stops serving customers. Likewise, Capability Compounding depends on useful learning; repetition that makes a business more rigid does not qualify. These principles express how we assess a system, rather than measured effects established by the cited research.
Durability is therefore conditional. A system may be difficult for rivals to copy yet lose value if customers change what they want. Sustaining an advantage requires both resistance to imitation or substitution and an ability to renew the configuration when its underlying logic no longer holds.
What leaders should do differently
Begin with a specific customer outcome and the alternatives customers can choose. Ask where the organization performs differently, not where it feels strongest. Then map the activities that produce the result. Which choices lower another activity’s cost, improve its quality or make it more reliable? Which choices work against the promise?
Next, identify the trade-offs. What attractive opportunity would weaken the configuration if pursued without redesign? This does not mean refusing growth. It means recognizing when a new segment, channel or service promise changes the operating requirements. Make those requirements explicit before approving the expansion.
Invest in the capabilities on which the chosen position depends, rather than funding isolated projects that repeatedly rebuild the same know-how. Look for evidence that repeated work improves both current delivery and future capacity: more reliable routines, better judgment, reusable tools and clearer feedback. If those improvements are absent, continued spending should not be described as a compounding advantage.
Finally, revisit the System Replaceability Test when demand, technology or competitors change—not only when performance declines. An activity map is a hypothesis about how advantage is produced. Check whether customers still value the result, whether its economics still work and whether rivals can now match or replace it.
An individual strength can be the beginning of an advantage. Judge its durability by the position it serves, the activities that make it effective and the alternatives customers can choose. The question worth returning to is what those connected choices allow the business to deliver, and whether that result remains worth defending.