A Taxonomy of Strategic Situations
Military planning offers a useful comparison for classifying under uncertainty. Mission analysis helps leaders identify the relevant features of an operating environment. It lets them weigh courses of action without assuming they can predict the exact next move. A Strategic Situation taxonomy does something similar: it helps an enterprise recognize a class of demand before treating it as unprecedented. Prior recognition of the class can help leaders select or adapt a prepared response, though the right choice depends on current facts.
The four situation types describe preparation posture: lead time, how familiar the response may be, and how much new judgment the situation requires. That matters, but it does not tell you what the situation is about.
Picture a competitor stumbling in public, a regulation changing the compliance landscape overnight, or a major customer shifting strategic direction without warning. Their timing may look similar, yet each demands a different preparation architecture. The situation domains describe what a situation is about. They are neither preparation capabilities nor diagnostic measures.
A taxonomy of Strategic Situations can help leaders manage variety by sorting it into recognizable types. Medicine classifies diseases, biology organisms, finance assets, and cybersecurity threat vectors. Such classifications give practitioners a shared language without removing the need for judgment.
Without common terms, one executive sees a market disruption, another an innovation challenge, and a third a customer-experience issue. A shared vocabulary can cut the time spent negotiating what the organization faces. Leaders still have to test whether the label fits the facts. Enterprise Readiness proposes the taxonomy to organize complexity for coordinated response, not to predict every event. How an organization defines a Strategic Situation can shape how it responds. Like the checklists Atul Gawande studied, a taxonomy can work as a recognition aid. It can help keep important steps visible under pressure, though it cannot ensure they will always be followed.
The canonical hierarchy has three levels. Level 1 contains three strategic portfolios: Growth and Market Capture; Strategic Transformation; and Risk and Resilience. Level 2 contains nine operational domains. The first five are Competitive Positioning and Market Opportunity; Revenue and Client Growth; Innovation and Product Moves; Organizational Transformation and Change; and Leadership and Talent. Four more complete the set: Mergers, Acquisitions, and Partnerships; Regulatory and Compliance; Operational and Supply Chain Risk; and Cybersecurity and Technology Risk. Level 3 contains four preparation postures: Planned, Anticipated, Infrequent and high-consequence, and Unprecedented. Appendix C maps the nine domains and example situation types.
Alongside risk and resilience, the nine domains cover growth and market capture opportunities, competitive positioning moves, innovation windows, transformation demands, leadership transitions, and regulatory requirements.
Enterprise Readiness is not a transformation framework. It is organizational infrastructure that operates before, during, and after any transformation.
Transformation readiness asks whether the organization can redesign itself to capture AI value. Enterprise Readiness asks whether it is prepared to act on strategically significant problems, challenges, or opportunities. That question holds whether the transformation is complete, under way, or not yet started.
The domains and postures are useful at different stages of a transformation. An organization that has completed an AI transformation still faces competitive moves, regulatory changes, planned initiatives entering execution, and unprecedented situations. Preparation is meant to raise the chance that relevant parts of a response are built before one arrives.
Transformation readiness can help an organization reach a destination, while preparation readiness asks what it needs in place to act once it gets there.
The domains that follow are entry points, not isolated containers. Strategic Situations can form networks. A situation may begin in one domain, set off demands in others, and change meaning as conditions develop. The taxonomy supports recognition; the Situation Network helps leaders consider what may need to be interpreted together.
Strategic Situations Are Rarely About One Thing
One lesson the taxonomy can help surface is that many significant Strategic Situations cross departments or categories. A cybersecurity breach may become a technology, legal, communications, customer, financial, Board, and reputation issue. An acquisition may begin as a financial transaction and develop into a culture, leadership, systems-integration, customer-retention, and workforce challenge. Organizations sometimes classify the demand too narrowly. Legal sees legal exposure, Technology a systems problem, and Finance financial risk. Each view is accurate within its domain without describing the whole.
Strategic Situations can cut across functional boundaries. Enterprise Readiness proposes them as the organizing object when a response must be integrated across domains.
Growth situations require the enterprise to expand capability faster than its operating model allows. Entering a new market, completing a major acquisition, or accepting a contract that could triple annual revenue can test whether the organization is ready to absorb success.
Competitive situations change the enterprise's position relative to rivals. A competitor's public failure, a new cost structure, or a market opening can create a window. That window can close before an unprepared organization settles ownership and response.
Innovation situations change what the enterprise can make, offer, or learn. AI, an emerging technology, or a new business model may start as a weak signal that needs interpretation before the investment case is obvious.
Transformation situations change the enterprise's operating model, systems, or structure. Mergers, restructuring, major technology implementations, and workforce change require coordinated movement across functions, not a project plan alone.
Leadership situations change who sets direction or how the enterprise commits to it. Succession, executive disagreement, and changes in ownership expose whether authority, accountability, and institutional memory were prepared before the transition.
Regulatory situations change the obligations or constraints the enterprise operates under. A new rule, a compliance action, or a shifting regulatory landscape can compress the decision window. The response may then need legal, operational, financial, and communications work at once.
Risk situations threaten the enterprise's ability to continue or to protect value. Supply interruption, technology outage, vendor instability, liquidity pressure, a data privacy incident, a product safety issue, or cultural fragmentation may begin in one function and become enterprise-wide. Geopolitical instability, natural disasters, pandemics, and macroeconomic shifts belong here when external conditions create enterprise risk.
Returning to the Situation Network
The dimensions make a situation recognizable; the network makes the response coherent. Consider AI, which may begin in the Innovation dimension as new technical capability emerges. It can quickly become a Transformation situation as operating models and skills shift. When authority between humans and systems needs clarifying, it can become a Leadership situation, and when rivals deploy it, a Competitive one. Developing obligations can make it a Regulatory situation, and growing questions of transparency, privacy, and accountability can make it a Risk situation.
Leaders need to understand these interdependencies before execution begins. A response built for Innovation alone is likely to miss the other dimensions. It solves part of the problem while the rest compounds. That is why the Strategic Situation Portfolio in Chapter 17 organizes leadership attention around the network of related situations being managed at once. The relationships often matter more than any single situation on its own.