Most organizations use more than one strategy framework. They diagnose with SWOT or Porter's Five Forces, plan growth with the Ansoff Matrix or BCG Matrix, design business models with the Business Model Canvas, and measure execution with the Balanced Scorecard or OKRs. Each framework does its job. The problem is that no two of them share a vocabulary, a structural logic, or an explicit connection to each other.
The result is that strategic reasoning fragments at every handoff. A competitive diagnosis produces findings in one language. Growth planning translates those findings into a different language. Business model design starts over in a third. Execution measurement tracks progress against objectives that may no longer connect to the original diagnosis. At each transition, context is lost, assumptions shift, and the analytical thread breaks.
This is not a criticism of any individual framework. The frameworks described in this resource — across diagnostic, growth and positioning, business model and innovation, and execution categories — were designed to solve specific problems, and most do that well. The integration gap is structural: these frameworks were created independently, at different times, by different thinkers, to address different questions. Nobody designed them to work together.
Consider a realistic strategic planning process. An organization begins with a SWOT analysis and Porter's Five Forces assessment to understand its competitive position. The diagnosis reveals that buyer power is high, a key capability is not rare or inimitable, and a technological shift threatens the current value proposition.
The team then uses the Ansoff Matrix to evaluate growth options and decides to pursue market development — entering a new geographic market with existing products. They use the Business Model Canvas to map the required business model for the new market. They set OKRs for the expansion and build a Balanced Scorecard to track performance across financial, customer, process, and learning dimensions.
Every step is reasonable. Every framework is used appropriately. But look at what happened at each transition:
Diagnosis → Growth Planning: The Five Forces analysis identified high buyer power and a technological threat. The Ansoff Matrix categorized the response as market development. But the Ansoff Matrix doesn't have a way to represent buyer power or technological threats — it operates on market and product dimensions only. The specific competitive dynamics that motivated the move are no longer part of the analysis.
Growth Planning → Business Model Design: The decision to enter a new market was made using Ansoff's categories. The Business Model Canvas maps the nine elements needed to operate in that market. But the canvas has no mechanism for assessing whether this particular configuration of elements will create competitive advantage in the new market, or whether it addresses the buyer power and technological threat that started the process.
Business Model Design → Execution: The Balanced Scorecard tracks performance across four perspectives. OKRs cascade priorities. But neither framework connects back to the original diagnosis. If the technological threat accelerates faster than expected, or if buyer power in the new market is even higher than in the old one, the execution metrics won't detect it — they measure progress toward the objectives that were set, not the validity of the assumptions behind those objectives.
At each handoff, the framework changed, the vocabulary changed, and the strategic thread thinned. By the time the organization is measuring execution, the connection to the original competitive diagnosis is implicit at best and absent at worst.
Using multiple frameworks is not integration. Integration requires structural properties that most framework combinations lack.
A shared vocabulary across strategic functions. When an organization uses SWOT for diagnosis, Ansoff for growth, Business Model Canvas for design, and Balanced Scorecard for execution, it operates in four different vocabularies. The "strengths" in SWOT don't map to the "key resources" in BMC, which don't map to the "internal processes" in the Balanced Scorecard — even when they refer to the same underlying reality. A shared vocabulary means the terms used to describe strategic elements at the diagnostic stage are the same terms used at the design, execution, and evaluation stages. Insights carry forward without translation loss.
Explicit connections between stages of analysis. Integration requires that the output of one analytical stage is a structured input to the next — not a set of findings that must be manually reinterpreted through a different framework's lens. When diagnosis identifies a vulnerable competitive position, the design stage should receive that finding in a form it can operate on directly, not as a narrative summary that must be re-encoded.
A mechanism for assessing advantage dynamics. Most frameworks describe static positions or structures. Integration requires a way to assess whether a strategic configuration will compound advantage over time, stall, or decay — because the answer to that question determines whether a strategy is worth executing, regardless of how well-designed or well-measured it appears.
A mechanism for detecting strategic failure. Execution frameworks measure progress toward objectives. Integration requires a way to assess whether the objectives themselves remain valid — whether the assumptions embedded in the strategy still hold, and under what conditions they would stop holding. Without this, an integrated system is still blind to its own obsolescence.
A mechanism for assessing external disruption at the structural level. Strategy does not operate in a vacuum. Integration requires a way to evaluate how external forces — particularly AI-driven disruption — affect specific elements of a strategy, not just the business as a whole. Different strategic elements face different disruption dynamics, and an integrated system must be able to assess exposure at that level of specificity.
Genuine strategic integration is rare. Most "comprehensive strategy" involves using multiple frameworks sequentially without structural connections. A small number of systems attempt to solve the integration problem directly, each with a different architecture.
Playing to Win, developed by A.G. Lafley and Roger Martin, integrates through a cascading choice architecture. Five strategic choices — winning aspiration, where to play, how to win, core capabilities, and management systems — cascade from broad direction to operational specifics. Each choice constrains and enables the choices below it, creating alignment from aspiration through execution.
What it integrates well. Playing to Win connects strategic positioning to capability requirements to management systems in a single coherent architecture. The cascading structure forces explicit decisions at every level and makes misalignment between levels visible. The "where to play" and "how to win" choices create direct linkage between competitive positioning and capability investment, solving the positioning-to-execution handoff that many organizations struggle with.
Where its integration has boundaries. Playing to Win integrates through a top-down choice architecture: define the aspiration, then choose where to play, then determine how to win, then identify required capabilities, then design management systems. This architecture is strong on coherence and alignment. It is less explicit on several dimensions that a fully integrated analytical system might address:
It does not provide a shared structural vocabulary for decomposing the basis of competitive advantage. The "how to win" choice is answered in natural language (for example, "we win through superior product innovation and brand strength") rather than by classifying the specific strategic elements present and analyzing their interactions.
It does not separately assess advantage durability. The framework assumes that a coherent and well-executed set of choices produces advantage, without providing a distinct mechanism for evaluating whether that advantage will compound, stall, or decay under competitive pressure.
It does not assess element-level exposure to AI-driven disruption. Published in 2013, Playing to Win predates the emergence of AI as a primary strategic variable. Its architecture does not include a mechanism for evaluating how AI affects specific components of a strategy.
It does not provide a mechanism for detecting when a strategy stops working from within the framework — for identifying the specific conditions under which the chosen strategic configuration would break.
These are boundaries, not deficiencies. Playing to Win solved a real and important problem — strategic incoherence — and it remains one of the most effective frameworks for ensuring that an organization's strategic choices align. Its integration operates at the choice level; it does not attempt structural decomposition or dynamic analysis.
(For full coverage of Playing to Win's strengths and boundaries as a design framework, see Business Model and Innovation Frameworks.)
The Strategic Formula System, created by Eric D. Noren, integrates through structural decomposition and dynamic analysis. Rather than organizing strategy as a cascade of choices, it decomposes strategy into discrete elements, analyzes their interactions, and assesses the economic dynamics that emerge from those interactions.
The system is built on three interdependent components, each with a fixed and non-overlapping role, and supports formal applications that translate system structure into applied strategic analysis:
Periodic Table of Business Strategy. The structural taxonomy of the system. It defines 35 discrete strategic elements — 12 business models, 17 strategies, and 6 competitive advantages — that can appear in any Strategic Formula. Any business's strategy can be described as a specific combination of these elements without inventing new categories. The table provides the shared vocabulary that carries across every stage of analysis: the same elements used in diagnosis are the same elements assessed for advantage dynamics, disruption exposure, and failure conditions.
A Strategic Formula is expressed as (Business Model + Strategy) × Competitive Advantage. This notation is conceptual, not mathematical. Business models and strategies compose the operating logic of a business; competitive advantages determine whether that logic merely functions or compounds over time.
Each element in the Periodic Table carries a fixed set of Critical Success Factors — executional priorities mapped to a shared vocabulary of nine operational categories. When elements combine in a formula, overlapping Critical Success Factors reveal points of executional concentration: where the formula's performance depends most heavily on strength in specific operational areas, and where weakness creates structural fragility.
Learning-Loop Economics. The strategic theory that explains why some Strategic Formulas compound advantage over time while others stall or decay. It focuses on proprietary learning loops — tightly coupled cycles of use, learning, and improvement — and the conditions under which those loops create durability, lock-in, and increasing returns. The strength of a learning loop depends on cycle speed and data exclusivity; its viability depends on exclusive data capture, tightly integrated architecture, and rapid feedback tempo.
AI Susceptibility Index. A diagnostic instrument that assesses how exposed each element in the Periodic Table is to AI-driven pressure, commoditization, or erosion. Each element is scored across five dimensions: digitizability of value, data intensity and availability, automation potential, network-effects sensitivity, and capital re-allocation friction. The ASI operates at the element level, not the company level — identifying where within a Strategic Formula AI pressure is structurally concentrated.
Strategic Breakpoint Analysis. A diagnostic application that identifies the conditions under which an existing strategy stops working. A failure mode is the specific way a strategic configuration breaks when its underlying assumptions no longer hold — a structural property of the strategy, not a prediction about events. A strategic breakpoint is the threshold at which one or more failure modes become binding: the point at which previously tolerable assumptions, dependencies, or constraints cross from latent to decisive. Breakpoint analysis makes explicit how a strategy would fail and under what conditions that failure becomes unavoidable.
How the system integrates. The Periodic Table provides the shared vocabulary. A Strategic Formula composed from that vocabulary can be analyzed for advantage dynamics (Learning-Loop Economics), disruption exposure (AI Susceptibility Index), executional concentration (Critical Success Factors), and failure conditions (Strategic Breakpoint Analysis) — all using the same structural elements, the same terminology, and the same analytical foundation. Diagnostic inputs flow into design, design flows into dynamic assessment, and dynamic assessment flows into failure detection without translation loss or vocabulary change.
Where Playing to Win asks "What are our choices, and are they coherent?", the Strategic Formula System asks "What is structurally present, how do the elements interact, and under what conditions does this configuration break?"
Wardley Mapping, created by Simon Wardley, integrates through positional and situational awareness. It maps value chains against an evolution axis — genesis, custom-built, product, commodity — to visualize how components of a business move through predictable stages of maturity. The map provides a spatial representation of strategy: where components sit on the evolution curve, how they depend on each other, and where movement is likely.
What it integrates well. Wardley Mapping provides a unique perspective that other integration approaches lack: a visual representation of how strategic components evolve over time and how that evolution creates opportunities and threats. The evolution axis is a genuine contribution — it explains why certain strategic moves are predictable (commoditization of infrastructure, for example) and why organizations that fail to anticipate component evolution are repeatedly surprised. The mapping approach also integrates supply-chain relationships with competitive dynamics in a single visual, connecting value chain analysis to strategic positioning.
Where its integration has boundaries. Wardley Mapping integrates through visual mapping and situational awareness rather than through a shared analytical vocabulary or structural decomposition. The maps are powerful communication tools, but the analytical vocabulary is less formalized — different practitioners may map the same business differently, and the framework does not provide a fixed taxonomy of strategic elements. It is strong on anticipating evolution and weaker on assessing the specific structural basis of competitive advantage or the dynamics that determine whether advantage compounds or decays.
One reason strategy frameworks don't connect is that strategy itself suffers from imprecise language. The terms "strategy," "business model," "competitive advantage," and "moat" are routinely used interchangeably in practice — by executives, consultants, analysts, and journalists — despite referring to structurally different concepts.
A business model defines how a business creates, delivers, and captures value. A strategy defines how a business chooses to compete. A competitive advantage is a durable structural condition that allows superior returns without continuous reinvention. These are different things. A business model is not a strategy. A strategy is not a competitive advantage. Competitive advantage is not guaranteed by having either a business model or a strategy.
This imprecision compounds the integration problem. When an organization can't distinguish between its business model and its strategy, it can't diagnose which one is failing. When it uses "competitive advantage" to describe operational efficiency or brand awareness — neither of which constitutes structural advantage — it can't assess whether its position is durable or fragile.
Any system that attempts to integrate across strategic functions must start by separating these terms. The Periodic Table of Business Strategy addresses this directly: it defines business models, strategies, and competitive advantages as three distinct categories with non-overlapping elements, providing a shared vocabulary that prevents the conflation that undermines strategic reasoning.
Not every organization needs an integrated strategy system. The decision depends on the complexity of the strategic problem.
A single framework is sufficient when you are addressing a single strategic function — diagnosing your competitive position, evaluating a growth option, designing a business model, or measuring execution. Most strategy frameworks do their intended job well. Using SWOT to generate a situational snapshot, or the Business Model Canvas to map a new venture's structure, does not require integration.
Integration becomes necessary when the strategic problem spans multiple functions and the connections between them matter:
You are making cross-functional strategic decisions — where diagnostic findings need to inform design choices, and design choices need to flow into execution priorities, using a consistent vocabulary throughout.
You are assessing competitive dynamics at the structural level — not just "what is our position?" but "why does this position compound or decay, and what specific elements are responsible?"
You are evaluating exposure to AI-driven disruption — not at the company level ("AI will affect us") but at the element level ("AI most threatens this specific aspect of our strategy, and here is why").
You are trying to understand why a strategy that was working has stopped — not "what metrics are declining?" but "what assumptions has this strategy embedded, and which of those assumptions are no longer holding?"
You are managing a portfolio of businesses or strategic configurations that need to be compared, diagnosed, and evaluated using consistent structural language.
For organizations facing these problems, the integration gap is not an academic concern. It is the constraint that prevents strategic reasoning from connecting across functions — and it is the problem that integrated strategy systems are designed to solve.
Part of: Business Strategy Frameworks: A Functional Comparison
Previous: Execution and Performance Frameworks: Measuring Progress Without Detecting Failure
Framework category comparisons:
Diagnostic Strategy Frameworks
Growth and Positioning Frameworks
Business Model and Innovation Frameworks
Execution and Performance Frameworks
Strategic Formula System:
Strategic Formula System — System overview and definition
Periodic Table of Business Strategy — Structural taxonomy
Learning-Loop Economics — Advantage dynamics
AI Susceptibility Index — Disruption assessment
Strategic Breakpoint Analysis — Failure detection
