Enterprise Agility Threshold

Definition

Enterprise Agility Threshold is the observable principle that agility itself is not a destination but a moving target. Fifty years ago, three years to market for a new vehicle was considered a competitive advantage over the five years General Motors required. Today, enterprises that take five years to bring a product to market will probably be out of business before launch, because the target market will have evolved. The threshold for what counts as "competitive agility" is constantly raised by technological innovation and competitor capability.

In the Book

Cummins opens the book with this observation: "Agilityhas always been important for an enterprise to achieve and maintain competitive advantage. However, the threshold for competitive agility is constantly changing." The General Motors example is the anchor. The implication is clear: an enterprise cannot declare victory on agility and rest. The moment it achieves parity with competitors on speed, that speed becomes table-stakes and no longer a competitive advantage.

This understanding shapes the book's central thesis. Traditional business systems were automated for stability—to lock in "best practices of the time." But "as we will see, business systems are also becoming increasingly complex to optimize customer value, control, and performance while increasing agility." This is not a one-time architectural change; it is a commitment to continuous evolution.

The book later identifies "Continuous strategic planning and transformation" as a key cultural objective: "It is impossible neither to predict all the forces that will require business change nor to anticipate the enterprise-level need for strategic planning...A significant transformation will likely be incomplete when the next transformation is initiated."

Why It Matters

Enterprise Agility Threshold reframes how organizations should think about transformation initiatives. It makes clear that "we are done, we have achieved agility" is a category error—like claiming you will never drive again so you will never need gas. Instead, the right question becomes: "What capabilities and governance models do we need to make transformation routine rather than episodic?" This perspective justifies investment in flexible architectures (like CBA), continuous sensing systems, and organizational cultures that expect change rather than resisting it. It also explains why enterprises that view agility as a project to complete always lose ground to those that institutionalize the ability to change.