Path dependence is a concept that describes how past decisions and historical trajectories shape future outcomes, often in ways that are not immediately obvious. It is a mental model that emphasizes how small, seemingly arbitrary decisions compound over time to create entrenched systems, behaviors, or technologies. It is a reminder that history matters, and that the road not taken can have profound implications for future possibilities. In the context of IT, path dependence can have a profound impact on organizations, creating inertia that makes it difficult to adapt to changing market conditions or adopt new technologies.

The term was first popularized by economist Paul David in the 1980s, though its roots trace back to earlier work on technological and organizational evolution. David’s seminal paper on the QWERTY keyboard, where the dominance of an inefficient layout persisted due to early adoption and network effects, illustrates how initial choices can lock systems into suboptimal paths.

The standard gauge of railway tracks is another example of path dependence. It shows how a seemingly insignificant event or circumstance can change the choice of technology over the long run despite contemporary know-how showing such a choice to be inefficient. More than half the world’s railway gauges are 4 feet 8¹⁄₂ inches (143.5 cm), known as standard gauge adopted in the late 1820s, despite the consensus among engineers being that wider gauges have increased performance.

As per Wikipedia, the phrase can imply two types of claims.

• The first is the broad concept that “history matters”, or “particular events in the past can have crucial effects in the future.”
• The second is a more specific claim about how past events or decisions affect future events or decisions in significant or disproportionate ways, through mechanisms such as increasing returns, positive feedback effects, or other mechanisms.

Also see: Path dependence – Wikipedia

IT Decision-Making Scenarios

1. Legacy System Lock-In: An organization adopting a proprietary software solution in the 1990s may find itself unable to transition to modern cloud-based platforms due to data silos, incompatible architectures, and sunk costs. The initial choice, driven by cost or vendor relationships, creates a path that limits innovation and scalability.
2. Vendor Dependency: Early reliance on a single cloud provider (e.g., AWS) can lead to over-optimization of workflows around that platform’s tools, making it costly and complex to migrate to competitors. This path dependence stifles competition and hampers the ability to leverage emerging technologies.

Subscribe to continue reading

Become a paid subscriber to get access to the rest of this post and other exclusive content.

Type your email…

Subscribe

Already a paid subscriber?