Sailing Ship Effect
Never assume today’s incumbent is tomorrow’s incumbent, competition changes the incumbent before it replaces it.
What Is It?
Named by researcher W.H. Ward in 1967, the sailing ship effect describes how the introduction of a new, competing technology often accelerates innovation in the older, incumbent technology it threatens, rather than making further investment in it pointless. The classic historical example, a surge of design improvements to sailing ships after steamships appeared as competitors, has itself been debated by historians, a 2005 re-examination by John Howells argued the two technologies mostly served different market segments rather than directly competing. But the broader pattern has been observed often enough in other industries to remain a useful lens independent of that specific dispute. The mechanism is that threat changes the economics of improvement: investments that once seemed unnecessary suddenly become worthwhile because survival now depends on them. That’s why the threat often reveals unused capability rather than creating new capability, competition didn’t create the ability to improve, it created the incentive.
Why Does It Matter?
The common strategic assumption is that a disruptive new alternative simply makes the old option irrelevant, and the old option’s owners will fade quietly rather than compete. In practice, a legacy product, team, department, or process facing a genuine competitive threat is often the moment it improves the fastest, not the moment it gives up, because the threat itself is what finally makes the improvement urgent, an HR function threatened with outsourcing suddenly modernizes, a struggling product line facing a nimble competitor suddenly becomes customer-obsessed. This isn’t new capability arriving from nowhere, it’s latent capability the organization was leaving on the table until the payoff for using it changed.
What Changes Once You See It?
You stop forecasting an incumbent as static. Once genuinely threatened, it becomes a moving target, not a fixed baseline to plan against.
You also start being more honest about your own team’s incentive: real external threat is often what produces the urgency that internal pressure alone couldn’t.
Common Misunderstandings
- It isn’t a claim that incumbents always survive disruption. Many don’t. The pattern is specifically about a burst of genuine improvement in response to threat, not a guarantee that improvement is enough to win.
- It isn’t evidence that disruption has failed when it doesn’t happen. Sometimes the incumbent’s best period of innovation still ends in eventual replacement.
- It doesn’t mean competitive pressure should be manufactured for its own sake. The improvement is a real response to real threat, artificial urgency without genuine stakes doesn’t reliably produce the same effect.
- It isn’t proof the original historical case was as dramatic as it’s often told. The underlying pattern, threatened incumbents innovating harder, holds up on its own merits even if the sailing-ship story itself has been contested.
Diagnostic Question
Are we modeling the incumbent we see today, or the incumbent that competition is about to create?
Explore Further
Field Notes
None yet.
Related Field Guide
Origin
Named by W.H. Ward in 1967; the founding historical case was later disputed by researcher John Howells in 2005. The broader economics of how threat unlocks latent capability is echoed in Nathan Rosenberg’s later work on innovation.