Opening note

Business strategy frequently suffers from a severe lack of situational awareness. Organizations routinely rely on copying popular market memes, adopting magic frameworks, and navigating by storytelling rather than empirical reality. This approach equates to alchemy. Without a proper mechanism to observe the landscape, a business has no reliable way to learn from past encounters, anticipate context-specific moves, or effectively communicate direction across teams. Abundant and inefficient communication, characterized by a constant panic over where the organization should go next, is a primary symptom of poor situational awareness. True strategy requires treating business competition less like a storytelling exercise and more like a rigorous game of chess, where high-tech advantages do not guarantee victory against low-tech opponents who possess superior awareness of the board.

Core thesis

Strategy requires identifying exactly where to attack before determining how to attack. There are two distinct types of “why” in business. The first is the “why of purpose,” which is the foundational desire to win or exist. The second is the “why of movement,” which dictates why an organization should choose to move to one specific position over another. Strategy frequently degenerates into copying memes and issuing a tyranny of action statements because organizations confuse the purpose with the movement.

To determine the why of movement, operators must understand Sun Tzu’s five factors of competition. These factors are Purpose, Landscape, Climate, Doctrine, and Leadership. Without a visual map of the landscape, organizations are blind. A true map requires visual representation, context specificity regarding the battle at hand, positioning relative to an anchor, and a depiction of movement over time. All components within a business landscape evolve, and an organization must dynamically adapt its methodologies, purchasing frameworks, and structures to match the specific evolutionary state of each component it manages.

Main ideas / framework

The Anatomy of a Map

A Wardley Map is built upon two axes that plot the components necessary to deliver value.

  • The Anchor and Position (Y-Axis): The map must be anchored by the user, which can include customers, regulators, or the board of directors. Position is mapped vertically based on visibility and value to that specific user. The chain is constructed by asking what subcomponents are required to build the capabilities immediately above them.
  • Movement and Evolution (X-Axis): Components move horizontally from left to right driven by supply and demand competition. Every component exists in one of four evolutionary stages. Genesis is the uncharted domain of the rare and uncertain. Custom Built represents bespoke solutions. Product marks the transition into feature differentiation and high margins. Commodity or Utility represents the industrialized state of commonplace, predictable, and low unit margin components.

Creating this map requires group challenge and debate. Operators should focus on genuine user needs rather than the desires of the business to generate profit. The goal is not to create a perfect scale model, as all models are inherently wrong but some are useful. The goal is to expose assumptions and establish a baseline for strategic play.

Climatic Patterns

Climatic patterns are the rules of the game. They are external forces that change the map regardless of an organization’s actions, but their predictability allows them to be anticipated and exploited.

  • Everything Evolves: All activities, practices, data, and knowledge move relentlessly from the uncharted to the industrialized.
  • Efficiency Enables Innovation: Genesis begets evolution, and evolution begets genesis. Standardized, evolved components act as foundational building blocks that allow for the rapid creation of higher-order complex systems.
  • The Red Queen Hypothesis: Evolution is not optional. As competitors adopt evolved and highly efficient components, the pressure on the lagging organization to adapt becomes overwhelming. Standing still guarantees being overtaken.
  • Past Success Breeds Inertia: Existing suppliers strongly resist the industrialization of the components that drove their past successes. New entrants, unburdened by this inertia, adopt evolved components first. This turns a trickle of change into a flood that destroys slow-moving giants.

Universal Doctrine

Doctrine represents universally applicable principles that remain consistently useful regardless of the specific context.

  • Focus on User Needs: Start by examining actual transactions and customer journeys. In the uncharted domain, operators must gamble. In the transition domain, they must listen. In the industrialized domain, they must beware of legacy bias from the installed base.
  • Use a Common Language: Standardize on mapping to bridge the translation gaps between different organizational functions, preventing technical teams and finance teams from speaking entirely different languages.
  • Be Transparent: Openly share maps to invite critique. Retribution for challenging a map is a deadly organizational sin.
  • Remove Duplication: Use profile diagrams to overlay multiple maps. This exposes duplicated efforts across business units and highlights the biased treatment of commodities, such as teams attempting to custom-build basic infrastructure.
  • Use Appropriate Methods: There is no single operational methodology that fits all scenarios. Agile is designed for the exploratory nature of the uncharted domain. Lean is designed for the transition domain to reduce waste. Six Sigma and ITIL are designed for the industrialized domain to reduce deviation.

The PST Organizational Structure

To design for constant evolution, organizations must implement a cell-based structure built on three distinct aptitudes, complete with a formalized mechanism of theft.

  • Pioneers: These teams explore the uncharted, generate highly novel ideas, and operate with a high tolerance for failure.
  • Settlers: These teams steal prototypes from the Pioneers and turn them into profitable, trusted products.
  • Town Planners: These teams steal products from the Settlers and industrialize them into massive-scale utilities and platforms. This structure ensures continuous evolution. The Pioneers can then build their next crazy ideas on top of the robust platforms created by the Town Planners. Dual operating systems that only utilize Pioneers and Town Planners consistently fail because they ignore the critical transition phase managed by Settlers.

What stood out in the highlights

Evolution versus Diffusion

A critical distinction exists between evolution and diffusion. Diffusion is simply the adoption of a specific item over time. Evolution is the changing nature of the act itself, shifting from high uncertainty to absolute ubiquity. Ubiquity is always relative to the applicable market. Furthermore, a point of stability is reached in evolution when industry publications stop discussing the operations, maintenance, and specific features of a component, and shift entirely to discussing solely how to use it.

The Nature of Disruption

Disruption takes multiple forms, and mapping reveals why incumbents frequently fail to survive them. Genesis disruption is inherently unpredictable. Product-to-Product disruption involves unpredictable timing and unpredictable new features. However, Product-to-Utility disruption is highly predictable and technically defensible. Despite this predictability, incumbents invariably fail during this transition due to institutional blindness and an inability to overcome their own inertia.

The Innovation Paradox

Organizations face a fundamental contradiction known as the Innovation Paradox. The need to innovate requires polar opposite capabilities, cultures, and metrics compared to the need to be highly efficient. Companies must explicitly manage both extremes simultaneously rather than attempting to blend them into a single, compromised culture.

Creative Destruction and Jevons Paradox

Industrializing components enables the creation of higher-order systems. Organizations build towers of order out of chaos, which decreases local entropy but permanently increases overall energy demand. Efficiency does not reduce overall budgets. According to Jevons Paradox, making a component highly efficient makes previously uneconomical acts feasible. This creates entirely new industries and drives up total consumption. Creative destruction functions as a punctuated equilibrium across evolutionary boundaries, destroying past business models while simultaneously funding the creation of the future.

System Resilience Types

Resilience is often misunderstood as a single attribute. Engineering resilience focuses on the efficiency of a specific function. Ecological resilience focuses on the continued existence of a function. A fragile system is low in both metrics. A robust system possesses high engineering resilience but low ecological resilience, making it highly efficient but easily destroyed by external shocks. A fluid system has low engineering resilience but high ecological resilience. True systemic resilience requires high levels of both. Furthermore, when navigating complex and rapidly shifting landscapes, utilizing an OODA loop is vastly superior to using a rigid PDCA cycle.

Operating lessons

Stop Self-Harm

The first phase of applying mapping is to stop organizational self-harm. This requires deeply understanding user needs, visually mapping the environment, and actively hunting for and removing duplicated efforts.

Breaking Down Contracts and the FIRE Mindset

Applying fixed-specification contracts to uncharted or custom-built components guarantees spiraling change-control costs and bitter disputes. The myth of having “one throat to choke” through a massive outsourcing contract is an illusion used by management to avoid dealing with underlying complexity. This approach inevitably leads to cost overruns and a catastrophic loss of strategic control.

Instead, operators must break contracts and systems down into small, distinct components. For industrialized components, organizations should use market standards, cloud utilities, or detailed specification outsourcing. For novel and uncharted items, organizations must either build them in-house or outsource to specialists strictly on a time-and-materials basis. When operating in the novel space, teams should adopt the FIRE mindset. Projects must be Fast to reduce risk through short time scales. They must be Inexpensive through thrift and reuse. They must be Restrained by enforcing small budgets, small documents, and small teams. Finally, they must be Elegant, focusing on pleasing simplicity and removing complexity rather than adding to it.

The ILC Gameplay Loop

The Innovate, Leverage, Commoditize cycle is a highly aggressive, context-specific stratagem. An organization begins by industrializing a component and offering it as a utility API. They then actively encourage an ecosystem of outside pioneers to build new businesses on top of this utility. The organization monitors the metadata and consumption patterns of this ecosystem to sense which future patterns are becoming successful. Once a successful pattern emerges, the organization industrializes that specific pattern into a new discrete component service. This creates a relentless, virtuous cycle that gives the utility provider the appearance of being highly innovative, incredibly efficient, and perfectly customer-focused all at once.

Managing Legacy Liability

Legacy systems eventually turn from assets into hidden liabilities due to outside evolutionary forces, a debt that standard double-entry bookkeeping completely fails to capture. Operators have three distinct plays for managing this liability.

  • The Strangler Pattern: Refactor the legacy estate piecemeal over time, specifically avoiding massive, all-at-once replacement projects.
  • Sweat and Dump: Shift the legacy system to an enterprise cloud provider to eliminate capital expenditure. Sweat the legacy asset to extract maximum remaining value while building the new world internally, then unceremoniously dump the legacy system once the transition is complete.
  • Pig in a Poke: Generate a compelling future story for the legacy asset and sell it to a third party. The organization extracts utility access agreements from the buyer while building a modern replacement, forcing the third party to bear the maintenance costs of the decline.

The Evolution of Action Methods

Operational methodologies must evolve as components move across the map. In the uncharted domain, where the environment is unknown, operators must rely on Just Do It mentalities and OODA loops to act first and check results later. As the component moves into the transitional phase and experience grows, the methodology shifts to Plan, Do, Check, Act cycles. Once the component reaches the evolved, familiar state of a utility, the methodology must shift to Define, Measure, Analyze, Improve, Control paradigms based on concrete measurements and absolute certainty.

Risks and misreadings

The Anti-Pattern Organization

The anti-pattern organization consistently confuses its own internal needs for profit or data with the actual needs of the user. It relies heavily on single-size methods, demanding Agile everywhere or applying Six Sigma universally due to outcome bias from a past success. Instead of challenging assumptions, it relies on the highest paid person’s opinion and copies strategies directly from popular business articles. This type of organization routinely builds custom versions of commodity components internally, wasting vast amounts of engineering talent on non-differentiated heavy lifting. Ultimately, the anti-pattern organization trades the ability to continuously learn for the illusion of simple management, frequently reducing complex environments to basic matrices.

The Anatomy of Inertia

Inertia kills organizations far more frequently than a lack of innovation. Blockbuster and Kodak successfully out-innovated their competitors in technology but failed entirely due to inertia surrounding their existing fulfillment and revenue models. Inertia barriers increase exponentially the more evolved and successful a component becomes.

Consumer inertia stems from three sources. The first is disruption to past norms, marked by the fear of losing political or human capital. The second involves massive transition costs, including the need to re-architect legacy estates and change governance models. The third is the agency of the new, driven by fears over vendor lock-in, unproven pricing models, and loss of strategic control.

Supplier inertia is driven by past financial success, rigid corporate cultures, and Wall Street expectations. When an industry shifts from a product to a utility phase, suppliers experience a rapid decline in margins. This triggers a predictable organizational panic.

The Spiral of Death

When legacy companies attempt to rent-extract a declining position, they inevitably resort to aggressive cost-cutting measures based on past-performance metrics. This blind cost-cutting accidentally fires the pioneers and radicals within the organization who are actually capable of creating the future. The culture then reinforces its own inertia, circling the wagons around the obsolete core product. Common executive mistakes during this phase include fleeing to overseas markets to hide from the disruption, attempting to add innovative features to an obsolete product architecture, engaging in blind price cutting, and doubling down on a transient definition of the core business. A sweating play only buys time for a lucky break to occur. Firing the people capable of finding that break guarantees organizational death.

The Danger of Deathstar Maps

A significant trap in mapping is attempting to create a single, all-encompassing map of the entire enterprise. These massive efforts are doomed to fail. Operators should favor iterative, localized mapping, starting small with a strong bias for action. Excuses claiming an environment is too complex or teams are too busy to map often mask a deep-seated resistance to transparency. Shared knowledge reduces individual political power, and operators should expect fierce bureaucratic battles when introducing mapping to siloed organizations.

Questions to reuse

Questions about Purpose and Direction

  • Are we confusing our internal desire to win with the strategic reasoning of why we should move to this specific position?
  • Are we confusing our organization’s need for profit or data with the genuine needs of the user?
  • Are we engaging in strategic play, or are we simply copying market memes and issuing action statements?
  • Does this strategic plan identify exactly where to attack before explaining why?

Questions about the Landscape and Map

  • What is the specific anchor for this map, and what are their actual, unfiltered needs?
  • Have we mapped components based on what they actually are, or are we biased by how our organization currently treats them?
  • Which components are standard building blocks, and which are we incorrectly attempting to custom-build?
  • Is our strategy focused heavily on the core, and have we recognized that our core is transient and actively evolving?

Questions about Methods and Execution

  • Are we using a single-size methodology across all components, regardless of their evolutionary state?
  • Have we applied fixed-specification contracts to uncharted components, guaranteeing spiraling change-control costs?
  • Can this large system be broken down into smaller components and outsourced using appropriate, evolutionary-matched methods?
  • Does this new initiative adhere to the principles of being Fast, Inexpensive, Restrained, and Elegant?

Questions about Organization and Inertia

  • Are we forcing technical and financial teams to communicate without a standardized visual language?
  • Do we have a dedicated coordination function that identifies duplicated efforts across isolated business units?
  • Are we protecting our pioneers and giving them the autonomy to fail, or are we measuring them by the efficiency metrics of town planners?
  • Is our current cost-cutting initiative accidentally firing the personnel required to build our future operating models?
  • Are we delaying the adoption of utility components solely because of the political capital tied to our legacy infrastructure?

Wardley Maps on Amazon