Wikipedia Strategic Thinking

1. 1Separate the two streams before you synthesize: gather 'hard data' (market research, financials, competitive metrics) and 'soft insights' (personal experience, observations from others across the organization) as distinct inputs, since synthesis needs both per Mintzberg and Beaufre.
2. 2Run the analysis phase deliberately — Beaufre: 'analysis is necessary to assemble the data on which he makes his diagnosis.' Assemble and lay out the dots before trying to connect them.
3. 3Shift the framing question from 'What?' to 'Why?' and 'How?' — interrogate the assumptions underlying the organization's current strategy and value proposition rather than cataloging activities.
4. 4Synthesize into a vision: connect the dots from all sources into 'a vision of the direction that the business should pursue.' Force yourself to produce a single directional statement, not a list.
5. 5Apply a systems perspective: reconnect phenomena across levels and disciplines, treat them holistically, and trace recursive cause-and-effect rather than assuming linear logic (Terra and Passador).
6. 6Convert the vision into an explicit hypothesis and treat implementation as 'intelligent trial-and-error': lay out the general path, run modest probes, and serially modify on feedback rather than locking a finely honed plan.
7. 7Feed the synthesized strategy into strategic planning so it can be controlled, resourced, and integrated back into the business — keep the two processes working hand-in-hand.
8. 8Stress-test the diagnosis against Mulcaster's 11 forces (Time, Opposing forces, Politics, Perception, Holistic effects, Adding value, Incentives, Learning capabilities, Opportunity cost, Risk, Style) before committing resources.

The 2008 financial crisis is the passages' own cautionary case. In retrospect the crisis could have been avoided if banks had paid more attention to the risks associated with their investments. A strategic thinker would not have stopped at the hard data of returns (the 'What'); they would have asked 'Why' those returns held and 'How' the risk was distributed — a systems view of recursive cause-and-effect across an interconnected financial network. Mulcaster's framework names the missing forces explicitly: Risk, Holistic effects, Time, and Opportunity cost were under-weighted in the decision process. The failure was not a shortage of alternative strategies but a shortage of quality in strategic decision making. The corrective is procedural: change how decisions get made so those forces are incorporated, not just generate more clever plans afterward.

• If you are cataloging 'What' the organization does, then stop and re-ask 'Why' and 'How' — the conventional 'What' question is the wrong strategic question.
• If you are only connecting dots (synthesis) without having assembled them (analysis), or vice versa, then you lack Beaufre's required 'great capacity for both' — do the missing half.
• If the environment is turbulent and uncertain, then do not rely solely on top-hierarchy vision or a finely honed plan; use intelligent trial-and-error and involve people across managerial levels.
• If a strategy worked elsewhere and you want to imitate it, then check it against your situation's specifics first — strategic convergence fails because it ignores that a strategy must account for each situation.
• If you are treating a complex scenario with linear cause-and-effect logic, then switch to holistic, recursive-causality thinking — trivial actions can be magnified into unpredictable consequences.

• Systematizing strategic thinking: trying to run it as a formal procedure. Tell — you've turned synthesis into a planning exercise; Mintzberg's point is that strategic thinking cannot be systematized.
• Confusing strategic planning with strategic thinking: producing data and analyses and calling that strategy. Tell — you have inputs and control mechanisms but no synthesized vision of direction.
• Generating endless alternative strategies while ignoring decision quality. Tell — lots of options, no attention to what influences the quality and effectiveness of the decision (the 2008 pattern).
• Imitating a rival's successful strategy without accounting for your specifics. Tell — you adopt the same limited strategy across greatly differing circumstances (Hamel's strategic convergence).
• Locking a precise, linear plan in a turbulent environment. Tell — no feedback loop, no serial modification; you're pursuing a fixed destination instead of laying out a general path.

• ▸Hard data assembled: list the market research / financial / competitive facts (the dots).
• ▸Soft insights assembled: list observations from your own and others' experience across the org.
• ▸Assumptions being challenged: which current strategy/value-proposition beliefs are you testing?
• ▸Why / How reframe: restate the strategic question away from 'What' toward 'Why' and 'How'.
• ▸Systems map: recursive cause-and-effect links across levels/disciplines relevant to this issue.
• ▸Synthesized vision: one directional statement the business should pursue.
• ▸Hypothesis + first probe: the modest trial and the feedback signal that will confirm or revise it.
• ▸11-forces check: score Time, Opposing forces, Politics, Perception, Holistic effects, Adding value, Incentives, Learning capabilities, Opportunity cost, Risk, Style.
• ▸Hand-off to planning: resources, controls, and integration steps to realize the strategy.

1. 1Separate the two thought processes before you start: treat strategic thinking as synthesis ("connecting the dots" — capturing soft insights and hard market data into a vision of direction) and strategic planning as the surrounding activity that supplies inputs and controls implementation. Do not collapse them.
2. 2Explore all possible organizational futures rather than a single forecast. Use scenario development (per Godet, Lindgren & Bandhold, Shell) to build multiple divergent futures instead of one linear projection.
3. 3Challenge the conventional questions. Replace "What?" with "Why?" and "How?" — and ask the tough questions that challenge your own ability to view future opportunities, since executives avoid this because it demands high intellectual energy.
4. 4Develop an independent point of view of tomorrow's opportunities (Prahalad & Hamel's industry foresight): identify which core competencies — the collective learning across the corporation — must be built now to control resources for future leadership.
5. 5Run strategy as intelligent trial-and-error, not fixed steps. Lay out the general path, then use modest probes serially modified on the basis of feedback; adjust means and ends iteratively during implementation.
6. 6Incorporate Mulcaster's 11 forces into each decision (Time, Opposing forces, Politics, Perception, Holistic effects, Adding value, Incentives, Learning capabilities, Opportunity cost, Risk, Style) to raise the quality of decisions, not just generate more alternatives.
7. 7Balance the articulated strategy against intelligent opportunism — stay responsive to good opportunities so channeling effort efficiently doesn't blind you to alternatives better suited to a changing environment.
8. 8Feed the synthesis back into planning: realize and support the imagined futures by integrating chosen strategies into the business and building the control plans for implementation.

The passages cite the 2008 financial crisis as a foresight failure that could have been avoided if banks had paid more attention to the risks associated with their investments. Apply the drill-down retroactively: a bank practicing strategic foresight would not forecast a single benign future but explore multiple organizational futures, including a housing-price collapse scenario. It would ask "Why?" and "How?" its returns held up rather than only "What?" the current numbers were. Running Mulcaster's forces, it would weight Risk, Holistic effects, and Opportunity cost explicitly in the decision process rather than treating investments as isolated bets. Instead of committing fully to one honed plan, it would run modest probes and adjust based on feedback signals from the market. The tell of the failure was decision processes that generated returns without a mechanism to change how decisions were made — exactly the gap Mulcaster's Managing Forces framework was built to close.

• If the environment is turbulent and uncertain, then favor strategic thinking (synthesis, multiple futures) over adherence to a finely honed strategic plan — but keep planning running alongside to supply inputs and controls.
• If your team is asking "What?", then redirect to "Why?" and "How?" — the critical strategic questions that drive foresight.
• If a strategy is being imitated by rivals in different circumstances (strategic convergence), then rebuild it around the specifics of your situation, because a copied strategy that ignores context will not work.
• If a decision has long-term implications, then create psychological distance (in time or situationally) and evaluate it with a wide-angle lens across all opportunities before committing.
• If pursuing future industry leadership, then invest intellectual energy in developing a corporate point of view of tomorrow's opportunities and the core competencies to exploit them, even though it feels harder than cost-cutting drills.

• Treating foresight as strategic planning. Tell: you produce linear projections toward a single defined destination instead of exploring divergent futures — Mintzberg's warning that strategic thinking cannot be systematized.
• Analysis without synthesis. Tell: you accumulate market data ("finding the dots") but never connect it into a vision of direction, so no diagnosis or choice between alternative courses emerges.
• Copying a successful strategy wholesale. Tell: strategic convergence — you and rivals in different circumstances run the same play, and it fails because it ignores the specifics of each situation.
• Skipping the future-of-the-industry work because it's hard. Tell: executives spend all time on cost, quality, and productivity and never develop a corporate view of the future — the difficult questions go unasked.
• Generating alternatives while ignoring decision quality. Tell: lots of creative strategy options but no attention to the forces (risk, incentives, politics, opportunity cost) shaping whether the decision itself is sound — the 2008 pattern.

• ▸Strategic question reframed: rewrite the "What?" as "Why?"/"How?"
• ▸Divergent futures (list 3-4): describe distinct possible organizational futures, not one forecast
• ▸Core competencies to build now: name the collective learning/capabilities each future demands
• ▸Consequences of present initiatives: for each current initiative, state its likely long-term implication
• ▸Mulcaster forces check: rate Time, Risk, Opportunity cost, Holistic effects, Incentives on this decision
• ▸Synthesis vision: one sentence connecting the dots into the direction the business should pursue
• ▸Probe & feedback plan: the modest trial you'll run and the signal that triggers adjustment
• ▸Opportunism trigger: the emerging opportunity that would justify deviating from the plan

1. 1Diagnose the enacted pattern, not the stated plan. Trace at least three years of actual competitive moves—pricing, feature launches, segment entries—and let the consistent thread define the strategy. Mintzberg's 'strategy as pattern' means the realized behavior over time is what counts, not the intent.
2. 2Anchor the pattern to one of Porter's three principles: a unique and valuable market position, deliberate trade-offs ('what not to do'), or fit (activities aligned to reinforce each other). Name which one your moves cumulatively serve.
3. 3Run the environmental analysis that shapes the pattern: PESTLE (remote), Porter's 5 forces (industry—rival competitive behavior, buyer/supplier power, new entrants, substitutes), and internal strengths/weaknesses of people, processes, and IT.
4. 4Disaggregate the value chain into strategically relevant activities—designing, producing, marketing, delivering, supporting—and identify where each contributes to relative cost position or a basis for differentiation. Competitive advantage stems from these many discrete activities, not the firm as a whole.
5. 5Test coherence: confirm the activities fit together to support the chosen position rather than working at cross-purposes. A robust competitive position cumulates from many activities that fit coherently.
6. 6Decide where interorganizational relationships extend the pattern—alliances, joint ventures, licensing, franchising, buyer-supplier ties—when they are the most efficient form or improve status, power, reputation, or legitimacy.
7. 7Install a feedback loop to monitor execution and detect emergent drift; where the realized pattern diverges from intent, treat the divergence as a strategic signal to re-formulate, since formulation and implementation are iterative.

Porter's value-chain logic makes the pattern concrete: 'Competitive advantage cannot be understood by looking at a firm as a whole. It stems from the many discrete activities a firm performs in designing, producing, marketing, delivering and supporting its product.' Suppose a firm's realized pattern is differentiation. You disaggregate its chain and find design invests in distinctive features, marketing communicates a premium position, and support maintains high service levels—each activity creating a basis for differentiation and each fitting the others. The trade-off Porter demands is visible in 'what not to do': it declines the low-cost segment because serving it would break fit. Over three years the moves cohere into a consistent pattern, so by Mintzberg's definition the differentiation strategy is realized, not merely planned. If instead you found marketing chasing budget buyers while design pursued premium features, the activities would contradict, coherence would fail, and no durable advantage would cumulate.

• If the realized pattern of past moves diverges from the stated plan, then treat the pattern as emergent and re-examine whether the environment has shifted—don't force the old intent.
• If an activity in the value chain neither lowers relative cost nor creates a basis for differentiation, then it is not strategically relevant and should be cut or reassigned.
• If pursuing a new segment or move breaks the fit among existing activities, then decline it—trade-offs and 'what not to do' protect the position.
• If a needed resource or market lies outside efficient in-house reach, then form an interorganizational relationship (alliance, joint venture, licensing) rather than build or buy in the market.
• If mission, values, goals, resources, and capabilities are not aligned, then behavior across managers and employees will be inconsistent—realign before scaling the pattern.

• Reading the plan instead of the pattern. Tell: your strategy deck describes intentions no competitive move over the last three years actually confirms.
• Evaluating the firm 'as a whole' rather than its discrete activities. Tell: you can name a general advantage but cannot point to which designing, producing, marketing, delivering, or supporting activity produces it.
• Skipping trade-offs—trying to differentiate and minimize cost and focus at once. Tell: no coherent 'what not to do' list exists and activities pull in opposite directions.
• Assembling activities that don't fit. Tell: individual functions look strong but reinforce different positions, so no advantage cumulates.
• Treating formulation and implementation as sequential and final. Tell: no feedback loop monitors execution, so emergent drift goes undetected until performance drops.

• ▸Realized pattern (3-yr): the consistent thread across actual competitive moves
• ▸Porter principle served: unique position / trade-offs / fit—pick and justify
• ▸5 forces read: rival behavior, buyer power, supplier power, entrants, substitutes
• ▸Value-chain map: for design/produce/market/deliver/support, note cost or differentiation contribution
• ▸Coherence check: do these activities reinforce or contradict each other?
• ▸'What not to do' list: segments/moves deliberately declined to protect fit
• ▸Interorg relationships: partners and the efficiency or legitimacy each provides
• ▸Alignment check: mission, values, goals, resources, capabilities in sync? (Y/N + gap)
• ▸Feedback loop: metric watched to detect emergent drift and trigger re-formulation

1. 1Separate intended from emergent strategy: document the plan you set out to pursue, then track the pattern of decisions actually realized in the market — the gap between them is your learning signal (Chaffee's planned vs. emergent vs. realized distinction).
2. 2Build a synthesis routine, not just a planning routine. Following Mintzberg, have the manager capture soft insights (personal experience, others' experience across the organization) alongside hard data (market research) and combine them into a revised direction, since strategy formation cannot be fully systematized.
3. 3Adopt the adaptive-strategy posture where the environment demands it: shift focus from fixed ends (goals) to means (resource mobilization to address the environment), decentralize decisions, and shorten or drop the planning window when continuous adaptation is required.
4. 4Install the five Liedtka competencies as operating disciplines: systems perspective (a mental model of the end-to-end value system), intent focus, thinking in time (holding past/present/future together), hypothesis-driven testing (creative + critical thinking, scientific method), and intelligent opportunism.
5. 5Run intelligent opportunism deliberately: keep the articulated strategy channeling effort, but hold a standing question — does a better alternative strategy suit the changed environment? — so you don't lose sight of it while executing.
6. 6Use scenario planning to change mindsets about the exogenous world before committing to specific strategies (as at Royal Dutch Shell), applying systems thinking to surface non-linear feedback loops and plausible storylines.
7. 7Treat business model adaptation as a repeatable capability: when individuals, events, or external factors (e.g., COVID-19) disrupt the market, modify specific business-model elements toward new configurations rather than defaulting to radical transformation.

Royal Dutch Shell uses scenario planning to change mindsets about the exogenous part of the world before formulating specific strategies. Rather than producing a single linear plan, analysts combine known facts (demographics, geography, mineral reserves) with driving forces identified through PEST analysis and generate simulation games for policy makers. Systems thinking is applied alongside, so the team recognizes that many factors combine in complex, non-linear feedback loops to create surprising futures. This lets Shell incorporate factors hard to formalize — novel insights about the future, deep shifts in values, unprecedented regulations or inventions. The output is a set of plausible scenario storylines grounded in causal relationships, not point forecasts. The organization then formulates strategy against these prepared mindsets, so an emergent shift in the environment is met with an already-rehearsed adaptive response rather than a scramble.

• If the environment requires continuous adaptation, then reduce or eliminate the planning window and emphasize means (resource mobilization) over fixed ends; if the environment is stable, then a linear planning approach with a long horizon is defensible.
• If the realized pattern of decisions keeps diverging from the intended plan, then treat the emergent pattern as data about a better-fitting strategy rather than as execution failure.
• If a good opportunity appears that a well-articulated strategy would exclude, then weigh the risk of losing an alternative better suited to a changing environment before rejecting it (intelligent opportunism).
• If disruption comes from an individual, event, or external factor, then apply business model adaptation (modify elements toward new configurations) before considering radical transformation — established firms are usually better motivated to adapt.
• If radical business model innovation is underway, then monitor person-organization fit, because sustained radical change reduces fit and raises workforce fluctuation.

• Systematizing strategy formation — running planning exercises as if they produce strategy. The tell: heavy analysis ("finding the dots") with no synthesis ("connecting the dots") into a direction, per Mintzberg.
• Over-committing to the articulated strategy so tightly that alternatives better suited to a changed environment go unseen — the tell is efficient execution toward goals that the environment has already made obsolete.
• Applying linear, Cartesian cause-and-effect logic to a complex system with recursive causality — the tell is that trivial actions produce unexpected magnified outcomes you keep treating as anomalies.
• Ignoring soft insights and relying only on hard market data — the tell is a vision disconnected from the lived experience of people across the organization.
• Choosing radical transformation when adaptation would serve — the tell is a spike in workforce fluctuation from collapsed person-organization fit during repeated radical model change.

• ▸Intended strategy: the planned goals, initiatives, and resource allocation you set
• ▸Realized pattern: the actual pattern of decisions the market shows over the period
• ▸Gap read: what the divergence reveals about environmental fit
• ▸Soft insights logged: experiences from you and others across the organization
• ▸Hard data logged: relevant market research findings
• ▸Adaptation type: business-model adaptation (modify elements) or transformation (radical) — and why
• ▸Opportunism check: which alternative strategy better fits the changed environment right now?
• ▸Fit watch: current signs of person-organization fit strain / workforce fluctuation

1. 1Quantify your experience curve: track cumulative production volume against unit cost and test whether costs fall 20-30% each time cumulative output doubles (the Boston Consulting Group experience curve hypothesis). If they do, scale is a real lever; if not, don't build strategy on it.
2. 2Confirm scale actually converts to profit before pursuing share. The PIMS study ran 19 years and found the greater a company's market share, the greater its rate of profit, via economies of scale plus experience curve advantages. Validate this holds in your specific industry rather than assuming.
3. 3Decide whether you are competing on scale or choice. Porter (1980) warned that the experience-curve paradigm pushes everyone toward larger scale and lower cost; if you can't win the share race, choose differentiation or focus instead of a losing cost-leadership fight.
4. 4For demand-side (network) advantages, identify whether your market is driven by technical standards or network effects that require interoperability/compatibility between users — the conditions Moore, Frank and Cook identified where a dominant firm gets a near-monopoly.
5. 5Sequence adoption to build the bandwagon. Following Moore, use Rogers' five-stage adoption process, focus on one customer group at a time, and use each group as a base to reach the next. Concentrate effort on crossing the chasm between introduction and mass acceptance.
6. 6Once momentum builds, drive toward de facto standard status so your product's installed base and switching costs lock in the position — the mechanism behind Internet Explorer's and Amazon's early dominance.
7. 7Stress-test durability: falling transaction costs and 'deconstructing' value chains (Evans, 2013) can strip scale advantages. Ask whether the information layer of your business can be separated and offered free/low-cost, as Wikipedia did to encyclopedias.

Take the encyclopedia business Evans cited in 2013. Traditional encyclopedias were information-based, vertically integrated firms whose scale (editorial staff, distribution, brand) built a defensible cost position. Wikipedia challenged that model as a network: it separated the information aspect from the functional activity, and because data was readily available for free or very low cost, the vertically integrated business could not remain intact. Here the network advantage inverted — the incumbent's scale became a cost burden while the challenger's user network produced value with near-zero marginal cost. Evans' underlying story is that transaction costs plummeting weakened the glue holding the value chain together, allowing it to separate. The lesson: a scale advantage grounded in owning information collapses when a network can assemble that same information for free, so audit whether your moat is real scale economics or just a temporarily protected information layer.

• If unit costs fall 20-30% per doubling of cumulative production, then pursue market share aggressively to compound experience-curve and economies-of-scale advantages (per PIMS: higher share yields higher profit).
• If you cannot realistically reach the highest-share position, then abandon cost leadership and choose Porter's differentiation or focus generic strategy instead.
• If the market is driven by technical standards or requires compatibility/interoperability between users, then race to become the de facto standard because network effects can give the dominant firm a near-monopoly.
• If transaction costs are plummeting and your value chain's information component can be separated from functional activity, then treat your scale advantage as temporary and prepare for deconstruction (Evans).
• If dominance was won purely on early network momentum, then keep reinvesting — Internet Explorer's later decline shows such dominance may be only temporary.

• Assuming scale automatically means profit. Tell: you cite market share as the goal but never verify the experience curve actually delivers the 20-30% cost decline in your industry.
• Chasing share when you'll never lead it — the 1970s trap Porter flagged. Tell: you're stuck mid-market, undercut on cost by the leader and undifferentiated against focused rivals.
• Treating temporary network dominance as permanent. Tell: you stop investing after becoming de facto standard, then decline like Internet Explorer.
• Trying to reach mass market before crossing the chasm. Tell: you spread effort across all customer segments at once instead of using one group as a base for the next, so no bandwagon builds.
• Defending a vertically integrated information business as transaction costs fall. Tell: a free or near-zero-cost network (like Wikipedia vs. encyclopedias) starts peeling off your information layer and you keep behaving as if the value chain is still glued together.

• ▸Cumulative-production cost test: does unit cost fall 20-30% per doubling? (yes/no + data)
• ▸Share-to-profit link: is higher market share correlated with higher profit here per PIMS logic? (yes/no)
• ▸Realistic share position: can you attain the highest-share/cost-leader spot? (yes/no)
• ▸Chosen generic strategy if not: differentiation / focus / cost focus
• ▸Network-effect trigger: is the market driven by standards or user-compatibility? (yes/no)
• ▸Adoption sequence: which single customer group first, and which group next?
• ▸De facto standard path: what makes your product the compatibility default?
• ▸Deconstruction risk: can your information layer be separated and offered free/low-cost? (yes/no)
• ▸Durability check: what keeps this advantage from being temporary (like IE)?

1. 1Decide scope and type first: per Porter (1980), commit to either lower cost or differentiation as the type of advantage you seek, and define the industry/customer segment you target — do not straddle both.
2. 2Locate the advantage in your value chain (Porter, 1985): map the discrete activities and processes you perform, then identify which ones you can execute at superior performance relative to rivals — that superior execution is the foundation of the advantage.
3. 3Confirm the value-creating strategy is not simultaneously implemented by rivals; audit competitors' cost positions and offerings to verify your position is 'unique and valuable' (Porter's first principle).
4. 4Make explicit trade-offs — Porter's second principle: choose 'what not to do' so the position cannot be cheaply copied by a rival trying to serve everyone.
5. 5Build 'fit' (Porter's third principle): align activities so they reinforce one another to support the chosen strategy, making the advantage a system rather than a single feature.
6. 6For cost advantage, exploit the experience curve: pursue higher cumulative volume/market share to drive unit costs down 15–25% per doubling, and track whether your cost structure is actually improving relative to competitors' experience positions.
7. 7Guard against decay: apply the 'nothing fails like success' warning — stimulate inquiry and healthy debate, watch for value migration and disruptive technology, and reassess whether yesterday's strength has become today's weakness.

Take Henry Ford's Model T as a cost-advantage case grounded in the passages. Ford pursued a single, undifferentiated offering — 'any color he wants, so long as it is black' — which is a deliberate trade-off of variety in exchange for scale. High cumulative production drove unit costs down along the experience curve, giving a cost position rivals could not match while they offered varied, costlier products. This was a value-creating strategy (an affordable car) not simultaneously matched by competitors, so Ford outperformed on cost. But the passage's 'nothing fails like success' maxim shows the trap: once customers began defining the business (Drucker, 1954) and the shift moved from production focus to market focus, that same no-variety strength became a weakness. Ford's cost advantage eroded because differentiation on color and features migrated value to rivals. The lesson: a cost advantage from scale is real but not automatically sustainable when the basis of competition shifts.

• If you cannot name whether you are competing on lower cost OR differentiation, then you have no competitive strategy yet — Porter forces the choice.
• If a rival is already implementing the same value-creating strategy, then it no longer confers advantage; find a position not simultaneously occupied.
• If your position requires no trade-offs (no 'what not to do'), then it is easily imitated and will not be sustained.
• If your cost lead depends on scale, then defend market share aggressively — the experience curve only rewards higher cumulative production.
• If yesterday's strength is now unquestioned and unchallenged internally, then treat it as a liability and stimulate constructive conflict before disruption forces the issue.

• Straddling cost and differentiation instead of choosing — the tell: your strategy statement claims to be both cheapest and most premium, and no activity trade-offs are visible.
• Confusing operational efficiency with competitive advantage — the tell: you're improving efficiency and controlling costs within existing strategy boundaries (operational management) but not creating a unique position.
• Treating a single feature as advantage without 'fit' — the tell: one strong activity sits isolated and rivals copy it easily because nothing reinforces it.
• Assuming an advantage is permanent — the tell: 'nothing fails like success,' where the firm depends on what worked yesterday and refuses to let go, missing value migration or disruptive technology.
• Doing everything right by current customers and still failing — the tell: Christensen's disruption trap, where the organization's capabilities define its disabilities and it ignores emerging low-end markets.

• ▸Advantage type: state lower cost OR differentiation (pick one).
• ▸Target scope: name the industry/customer segment you compete in.
• ▸Value-creating strategy: one sentence describing the unique, valuable position.
• ▸Rival check: list competitors and confirm none simultaneously hold this position.
• ▸Source activities: which value-chain activities you perform with superior performance.
• ▸Trade-offs made: explicitly list what you choose NOT to do.
• ▸Fit test: how your activities reinforce one another to support the strategy.
• ▸Cost/experience lever (if cost): current cumulative volume and expected unit-cost decline.
• ▸Decay watch: signals of value migration, disruption, or a strength becoming a weakness.

1. 1Define what you actually measure before claiming performance. Profit is ideal but dis-aggregate profit data is seldom obtainable, so use market share and survival rates as proxies — while knowing these links to profit can be weak and ambiguous.
2. 2Answer Drucker's first question: 'What is our business?' with the customer as the determinant, then set objectives across his eight areas (market standing, innovation, productivity, resources, worker performance, profitability, manager development, public responsibility).
3. 3Run a SWOT: assess firm strengths and weaknesses against environmental opportunities and threats. Match internal factors to external circumstances, and build a long-term coordinated strategy since structure follows strategy.
4. 4Choose your competitive advantage explicitly per Porter (1980): lower cost or differentiation, targeting particular industries and customers. Do not straddle both.
5. 5Audit your value chain (Porter 1985): identify where activities and processes outperform rivals, and locate resources or capabilities that let you operate more effectively in specific chain segments.
6. 6Test each candidate resource against VRIO: is it Valuable (exploits opportunity/mitigates the five threats), Rare (short supply AND persistent over time), Inimitable, and Organizationally exploitable? Rarity failing either condition drops you into perfect-competition dynamics.
7. 7Build an importance-performance matrix using nine-point scales (binary is too crude): plot each attribute's importance to customers against your performance versus competitors. Direct highest urgency to the most important areas where you perform worse than competitors.
8. 8Shift from acquisition to retention: estimate customer lifetime value and design sustained relationships, since businesses commonly overspend on winning customers versus keeping them.

Consider first-mover longevity through the passage's real cases. A pioneering firm reaps early profits from lack of competition, but the name 'first-mover advantage' misleads: profits sometimes fall near zero as a patent expires, forcing patent sale or market exit. Atari lost share to Nintendo; Apple's Newton PDA was overtaken by the Palm Pilot; and Charles Stack Online Bookstore was eroded by Amazon.com. The second-mover wins because it learns from the first mover's experience, spends less on R&D, less on educating the public, and faces less risk of product rejection. It redirects those saved resources to build a superior product or out-market the pioneer. So if you measure early market share as performance, you can misread durable advantage — the first-mover here is not guaranteed longevity.

• If you cannot obtain dis-aggregate profit data, then use market share and survival as proxies — but flag that these links to profit are weak and may cause ambiguity.
• If a resource is valuable but not rare (fails short-supply OR persistence), then expect perfect-competition dynamics and no sustained advantage — do not build strategy on it.
• If you hold early market share as a first-mover, then check whether it translates to profit; early entrant share advantage does not always mean higher profits.
• If an attribute is highly important to customers but you perform worse than competitors, then assign it highest urgency in operations strategy.
• If your firm is over-diversified, then only add a business where the parent can add more value than rival parents (parenting advantage); otherwise the portfolio destroys value.

• Assuming a durable, technically good product guarantees profit — the production-orientation fallacy Levitt called 'marketing myopia'; the tell is starting with the product and trying to sell it rather than starting with the customer.
• Treating first-mover status as guaranteed longevity — the tell is celebrating early market share while ignoring patent expiry, near-zero profit, and second-movers learning from your R&D and market-education spend.
• Confusing 'core competence' with 'something the company is good at' — the tell is applying the label to a single SBU rather than to collective learning across the corporation steered from the corporate level.
• Letting core competences become core rigidities and strategic assets become strategic liabilities — the tell is that the very capability once giving advantage now blocks adaptation, producing competitive disadvantage.
• Using a binary importance-performance matrix — the tell is coarse ratings that miss distinctions; the source calls binary 'too crude' and recommends nine-point scales on both axes.

• ▸Performance measure used: state whether profit, market share, or survival — and note the proxy's known weakness.
• ▸Business definition: answer 'What is our business?' from the customer's viewpoint.
• ▸Chosen advantage: circle lower cost OR differentiation, with target industry/customer.
• ▸VRIO test per resource: mark Valuable / Rare / Inimitable / Organized (Y/N each).
• ▸Rarity check: is the resource in short supply AND persistent over time? (both required)
• ▸Value-chain hotspot: name the activity where you outperform rivals.
• ▸Importance-performance entry: attribute, importance (1-9), performance vs competitors (worse/same/better).
• ▸Retention economics: estimated customer lifetime value and current retention vs acquisition spend.
• ▸Longevity risk: identify patent/first-mover exposure and any second-mover threat learning from you.

1. 1Scope the three environmental layers explicitly before analyzing: remote external (PESTLE), industry (Porter's Five Forces), and internal (resources: people, processes, IT systems). Assign each factor to its layer so nothing gets double-counted or dropped.
2. 2Run PESTLE on the remote external environment: catalog political, economic, social, technological, legal and environmental factors. Treat these as the two external elements Porter names—industry opportunities/threats and broader societal expectations.
3. 3Assess industry attractiveness with Porter's Five Forces: rate competitive rivalry, bargaining power of buyers/customers, bargaining power of suppliers, threat of new entrants, and threat of substitute products. Use the output to decide which markets and offerings belong in the portfolio.
4. 4Audit the internal environment for strengths and weaknesses across resources—people, processes, and IT systems—plus the personal values of key implementers (management and the board), which Porter counts as an internal element.
5. 5Match internal factors to external circumstances via SWOT (Andrews, 1963): assess firm strengths and weaknesses in light of environmental opportunities and threats. This is Selznick's original 'match the organization's internal factors with external environmental circumstances' formalized.
6. 6Convert findings into answers to the strategic questions: what is our business, who is the target customer, what is 'value' to them, what differentiates us, which resources/capabilities to develop, what opportunities and risks matter, and how to grow.
7. 7Hand the analysis off as inputs, not conclusions. Environmental analysis is analytical (finding the dots); the strategist still synthesizes it into a vision (connecting the dots). End formulation with concrete goals, objectives, and measures.

Selznick in 1957 coined 'distinctive competence' to describe how the Navy tried to differentiate itself from the other services, and he formalized matching an organization's internal factors with its external environmental circumstances. Kenneth Andrews took that core idea in 1963 and developed it into what we now call SWOT analysis, where the firm's strengths and weaknesses are assessed against the opportunities and threats in the business environment. Applied operationally: you inventory the Navy's internal resources and distinctive competencies (strengths), name its gaps (weaknesses), then read the external service-rivalry landscape for opportunities to differentiate and threats from other services. The match—not the lists themselves—is the analytical product. Porter's 1980 framing sharpens it: two elements are internal (company strengths/weaknesses; personal values of key implementers) and two external (industry opportunities/threats; broader societal expectations). The four-element structure keeps the analysis from collapsing into a single undifferentiated list.

• If a factor sits outside the firm and outside the industry, then it belongs in PESTLE; if it is competitive behavior of rivals, buyers, suppliers, entrants, or substitutes, then it belongs in Five Forces; if it concerns people/processes/IT, then it is internal.
• If you are deciding which businesses, products, or markets to include or exclude from the portfolio, then run Porter's Five Forces to gauge market attractiveness first.
• If you have collected internal and external factors separately but not related them, then run SWOT—the value is in matching, per Selznick and Andrews, not in the four lists.
• If the analysis has produced a 'vision' or 'the answer,' then you have overstepped: environmental analysis supplies inputs; synthesis into strategy is a separate thinking activity.
• If the personal values of management and the board are absent from your internal assessment, then the analysis is incomplete—Porter treats them as one of the two internal elements.

• Treating environmental analysis as strategy itself. The tell: the deliverable claims 'connecting the dots' into a direction, when analysis only 'finds the dots'—synthesis is a distinct step.
• Producing four separated lists (PESTLE, Five Forces, S, W) with no cross-linking. The tell: a SWOT grid where strengths and opportunities never get matched to each other.
• Confining the assessment to top-management views. The tell: no inputs from other managerial levels, ignoring that people from different levels interact to produce knowledge strategy.
• Omitting an environmental layer. The tell: rich rival analysis but no PESTLE legal/environmental scan, or a portfolio decision made without checking buyer/supplier power or substitutes.
• Skipping the personal values of key implementers. The tell: an internal audit covering only resources, missing Porter's second internal element and the values that shape which strategies are actually acceptable.

• ▸Business definition — state 'what is our business,' answered from the customer's perspective (Drucker).
• ▸PESTLE (remote external) — list political, economic, social, technological, legal, environmental factors as opportunities/threats.
• ▸Five Forces (industry) — rate rivalry, buyer power, supplier power, new-entrant threat, substitute threat; note market attractiveness.
• ▸Internal resources — strengths and weaknesses across people, processes, and IT systems.
• ▸Personal values of key implementers — values of management and the board that constrain acceptable strategies (Porter's 2nd internal element).
• ▸Broader societal expectations — external element beyond industry (Porter's 4th element).
• ▸SWOT match — pair each strength/weakness against a specific opportunity/threat (the analytical output).
• ▸Strategic questions answered — target customer, definition of value, differentiation, capabilities to develop, growth path.
• ▸Handoff note — flag this as inputs for synthesis, listing goals/objectives/measures to carry into strategy formation.

1. 1Start with the internal environment audit: catalog your people, processes, and IT systems, then sort them by strengths and weaknesses relative to what customers consider 'value'.
2. 2Apply the resource test used in the resource-based view: identify which capabilities are strategic per the value chain, meaning they excel, are difficult to duplicate, and coordinate people across multiple functional areas or processes.
3. 3Isolate your core competency using Hamel and Prahalad's rule — the one area where the organization excels — then decide what to keep, what to let go, and what to outsource.
4. 4Tie each retained capability to a competitive advantage type (Porter): does it produce lower cost or differentiation relative to rivals?
5. 5Answer the formulation question explicitly: 'Which resources, skills and capabilities should be developed within the firm?' and set specific short- and long-term objectives with measures for each.
6. 6Move to implementation: structure resources (by product, service, or geography), assign leadership, set incentives, communication, and monitoring mechanisms to track capability development against objectives.
7. 7Protect inimitability by keeping the competency embedded in cross-functional coordination rather than in any single, poachable component; outsource only the non-core value-chain elements.
8. 8Run a feedback loop — continuously re-test the assumptions behind the competency against the external environment, since business theory 'must be continuously analyzed.'

Selznick's 1957 use of 'distinctive competence' described how the Navy attempted to build a capability distinct to it — a resource lens later formalized as the resource-based view. Apply the same logic to a firm: an organization first asks Drucker's question, 'what is our business?', and answers it from the customer's definition of value. It then audits internal resources (people, process, IT) and finds, say, an ability to coordinate design and manufacturing engineers to deliver a product rivals cannot copy. Because this competency spans functional areas and is difficult to duplicate, per Hamel and Prahalad it qualifies as core, so the firm keeps it in-house and outsources peripheral value-chain activities. It then structures resources around that competency and sets objectives with measures per Drucker's areas — innovation, productivity, physical and financial resources. Finally it monitors execution through a feedback loop, re-testing whether the competency still delivers differentiation as the external environment shifts.

• If a capability is valuable, rare, hard to duplicate, and coordinated across functions, then develop and protect it in-house; if not, outsource it.
• If an activity is strategic as indicated by the value chain, then treat the underlying capability and ability to learn as strategic too.
• If the competency delivers no lower cost or no differentiation relative to rivals, then it is not a source of competitive advantage — stop investing in it as core.
• If you are the corporate parent, then only retain a business or capability where you can 'add more value' than rival parents (parenting advantage).
• If the assumptions behind your core competency stop matching the external environment, then re-analyze the business theory rather than defend the capability.

• Treating any strength as a core competency — the tell is a competency that is easily duplicated or lives in one function, not coordinated across processes.
• Skipping the internal audit and defining resources aspirationally; the tell is objectives without measures tied to actual people, process, and IT.
• Building capability without linking it to lower cost or differentiation; the tell is investment that never changes market position relative to rivals.
• Outsourcing a competency that is actually core to save cost; the tell is losing the cross-functional coordination that made it inimitable.
• Letting the business theory calcify — the tell is assumptions never re-analyzed even as society, technology, customers, and competition shift.

• ▸Capability name: state the specific skill or resource in one line.
• ▸Value to customer: what value this delivers as the customer defines it.
• ▸Rarity/inimitability: why rivals cannot easily duplicate it (cross-functional coordination).
• ▸Advantage type: does it produce lower cost or differentiation vs. rivals?
• ▸Keep/outsource decision: core (develop in-house) or non-core (outsource).
• ▸Development objective: short- and long-term goal for building this capability.
• ▸Measure: the metric tracking progress toward that objective.
• ▸Structure & owner: how resources are structured and who leads it.
• ▸Reassessment trigger: which environmental shift forces re-analysis of assumptions.

1. 1Choose your competitive advantage type first: decide between lower cost or differentiation relative to rivals, because Porter holds a firm must choose one or waste resources trying to be everything.
2. 2Set your competitive scope: decide whether you target the broad industry or a narrow segment (focus), giving you the three generic strategies — cost leadership, differentiation, or focus (with cost-focus and differentiation-focus variants).
3. 3Diagnose the industry structure before committing: map the five forces and identify which segments exist, since achieving competitive advantage results from coping with those forces better than rivals.
4. 4Build the position in the customer's mind, not just on paper: per Ries and Trout, judge the strategy by how customers see it relative to competition, then craft a single position in the collective consumer mind.
5. 5Use perceptual mapping and related techniques (multidimensional scaling, factor analysis, conjoint analysis) to identify the dimensions on which positions should be based and where uncontested space lies.
6. 6Anchor the position on real core competencies: select competencies that are distinctive, superior, communicable, unique, affordable, and profitable, so the claimed position is defensible.
7. 7Reinforce the position through corporate identity and communication: shape image via a coordinated campaign, but earn reputation only through consistent performance over time.

Consider Porter's own departure from the 1970s experience-curve paradigm, which pushed firms toward maximum market share and lowest cost. Under that older view, a company simply chased scale so unit costs fell 20–30% each time cumulative production doubled (Henderson's experience curve). Porter's 1980 move was to say a firm must instead make a choice about scope and advantage type: it could pursue the highest market share to win on cost (cost leadership), or it could target particular industries and customers with a differentiated offering. Firms chasing scale for cost advantage fit cleanly under cost leadership, but the choice to differentiate or focus was a genuinely new perspective. Henry Ford's Model T — 'any color so long as it is black' — illustrates the production-orientation extreme, where scale and standardization dominate. The later shift to market focus, echoing Drucker's point that the customer defines the business, is what forced positioning to become a mental battle for the customer's mind rather than an internal engineering claim.

• If you try to pursue cost leadership and differentiation simultaneously, then stop — Porter holds you will waste precious resources; pick one advantage type.
• If you cannot serve the broad industry against larger rivals, then choose a focus strategy (cost-focus or differentiation-focus) on a defined segment instead.
• If your position is justified only by internal company factors, then rebuild it — Ries and Trout require judging by how customers see you relative to competition.
• If a claimed differentiator is not distinctive, superior, communicable, unique, affordable, and profitable, then it is not a defensible core competency to build the position on.
• If you want reputation rather than just image, then rely on consistent performance over time, not a communication campaign alone.

• Straddling generic strategies — trying to be low-cost and differentiated at once; the tell is diffuse messaging and resources spread across incompatible activities.
• Judging the position by internal quality alone (production orientation); the tell is confidence that a durable, well-made product will profit itself, as with the Model T mindset.
• Confusing image with reputation — running a coordinated campaign but with inconsistent delivery; the tell is short-term image gains that decay because performance never matched the claim.
• Choosing a position without mapping industry segments or the five forces; the tell is a position that competitors match immediately because it sits in contested space.
• Basing the position on a competency that isn't communicable or unique; the tell is customers who can't articulate why you differ from rivals.

• ▸Advantage type: state lower cost OR differentiation (pick one).
• ▸Competitive scope: broad industry OR narrow segment (name the segment).
• ▸Resulting generic strategy: cost leadership / differentiation / focus (cost or differentiation variant).
• ▸Five-forces read: note where rivalry, buyers, and entrants most threaten this position.
• ▸Perceptual map dimensions: list the 2–3 attributes customers use to compare you.
• ▸Intended mental position: one sentence stating the place you want in the customer's mind vs. named competitors.
• ▸Core competency anchor: the competency that is distinctive, superior, communicable, unique, affordable, profitable.
• ▸Identity-to-image plan: the coordinated communication that projects the position.
• ▸Reputation proof: the consistent performance you will deliver to make it credible.

1. 1Diagnose whether your landscape is stable, complex, or chaotic before choosing a method. Complexity is 'chaos with a dash of order' — multiple agents interacting so that a glimpse of structure appears; chaos is turbulence that rapidly becomes disordered. Match your response to the diagnosis rather than defaulting to formal planning.
2. 2Run environmental analysis at three levels: remote external (PESTLE/STEEP — political, economic, social, technological, legal, environmental), industry (Porter's Five Forces — rivals, buyer/supplier power, new entrants, substitutes), and internal (resource strengths/weaknesses via SWOT). Feed these as inputs, not conclusions.
3. 3Scan for discontinuity types explicitly: name your 'strategic drift' risks (gradual, unnoticed change) separately from 'transformational change' risks (sudden, exogenous shocks), and mark suspected 'strategic inflection points' where a new trend begins.
4. 4Where outcomes cannot be predetermined, switch from single-forecast planning to scenario planning: build multiple plausible outcomes, assess implications of each, and evaluate likelihood. Treat it as an exercise in insight, complexity, and subtlety — not formal analysis and numbers.
5. 5Apply Terra and Passador's moves for genuinely non-linear systems: reconnect phenomena across levels/disciplines holistically, trace recursive causality, understand facts through their dynamics, and use mappings and negative approaches rather than linear cause-effect chains.
6. 6Build a deliberate self-renewal mechanism to counter 'nothing fails like success' — stimulate inquiry, healthy debate, and constructive conflict so yesterday's strength does not become today's weakness.
7. 7Widen who does the thinking. Do not confine strategy to top-hierarchy vision; the micro-foundation framework requires people from different managerial levels to interact dynamically, because classic vision has limits in turbulence.
8. 8Once direction is set, install monitoring: balanced scorecard, strategy maps, and feedback loops (regular divisional/corporate meetings) so you detect drift and inflection points early through performance data.

Consider the pre-2008 banks the passages cite. In retrospect the crisis could have been avoided had banks paid more attention to the risks tied to their investments — a case where existing strategies were stressed by an interconnected, non-linear system whose 'trivial actions' were magnified through intricate relationship networks into 'entirely unpredictable consequences.' The failure was not a lack of plans but a decision process blind to holistic effects and recursive causality. Applying Mulcaster's Managing Forces framework would have forced the eleven forces — including Risk, Holistic effects, Time, Opportunity cost, and Perception — into the decision process rather than treating investment returns linearly. Scenario planning would have generated multiple outcomes including a systemic downturn, assessed its implications, and weighted its likelihood, replacing the single optimistic forecast. The lesson the passages draw is that too little work targets the quality of strategic decision-making itself; turbulence demands changing how decisions are made, not just what is decided.

• If outcomes cannot be known in advance and sources of competitive advantage cannot be predetermined, then abandon single-formula 'excellence' models and use scenario planning with multiple weighted outcomes.
• If the system shows recursive cause-and-effect and non-linearity (small actions producing magnified, unpredictable results), then use holistic, systems-thinking methods instead of Cartesian linear logic or punctual dialectical logic.
• If a strength that worked yesterday is being defended as the answer today ('nothing fails like success'), then treat it as a source of weakness and force constructive conflict to test it.
• If change is gradual and unnoticed (strategic drift) versus sudden and exogenous (transformational), then build early-warning monitoring for the former and pre-planned response options for the latter.
• If strategy is being drawn only from top-hierarchy vision in a turbulent environment, then bring multiple managerial levels into dynamic interaction because classic top-down vision has cognitive limits here.

• Applying linear planning to a non-linear system — the tell: your plan assumes stable cause-effect and single forecasts, and 'trivial' events keep producing outsized surprises you never modeled.
• Confusing complexity with chaos and over-planning or giving up — the tell: you either impose rigid formulas on genuinely turbulent systems or treat a partially structured environment as pure randomness.
• Ignoring risk and holistic effects in decision-making, as the pre-2008 banks did — the tell: returns and upside dominate the analysis while downside interconnections go unexamined.
• Defending past success — the tell: prevailing strategies become self-confirming, debate is suppressed, and the organization refuses to let go of what worked before.
• Confining strategy to top management — the tell: no dynamic interaction across managerial levels, and knowledge held lower in the organization never reaches the strategy.

• ▸Environment classification: mark stable / complex (order glimpsed) / chaotic (rapidly disordered) with evidence.
• ▸Remote environment (PESTLE): list the top political/economic/social/technological/legal/environmental shifts stressing current strategy.
• ▸Industry forces (Five Forces): note strongest pressure among rivalry, buyer power, supplier power, new entrants, substitutes.
• ▸Discontinuity watch: name one strategic-drift risk and one transformational-change/inflection-point risk.
• ▸Recursive-causality map: identify one 'small action → magnified/unpredictable outcome' loop in your system.
• ▸Scenarios: state three plausible outcomes, each with implications and estimated likelihood.
• ▸Managing Forces check: score the 11 forces (Time, Opposing forces, Politics, Perception, Holistic effects, Adding value, Incentives, Learning, Opportunity cost, Risk, Style) as addressed / missing.
• ▸Success-trap review: which current strength risks becoming a future weakness, and what debate tests it?
• ▸Voices included: which managerial levels contributed, and which are missing from the strategy conversation?

1. 1Define the industry boundary precisely before analyzing forces: name the business you are in, the target customer, where customers are and how they buy, and what they consider 'value' — these questions from the formulation stage scope which rivals, buyers, and suppliers actually count.
2. 2Run Porter's five forces as a structured pass: (1) competitive behavior of rival organizations, (2) bargaining power of buyers/customers, (3) bargaining power of suppliers, (4) threats from new entrants, (5) the ability of buyers to substitute products. Score each force as high or low.
3. 3Locate the structural cost drivers: assess whether unit production costs fall 20–30% each time cumulative production doubles (experience curve). Where they do, market share confers a cost advantage that raises entry barriers and shapes rivalry.
4. 4Position each business unit on the two dimensions that survived portfolio theory: industry attractiveness (e.g., industry growth rate) and competitive position (e.g., relative market share). Use this to decide where to invest and what to divest.
5. 5Translate the force map into a strategic choice: pick a unique, valuable market position, then make explicit trade-offs about what not to do, choosing among cost leadership, differentiation, or focus.
6. 6Build 'fit' by aligning value-chain activities (inbound logistics, operations, outbound logistics, marketing/sales, service) coherently so the configuration differentiates you from rivals and defends the chosen position.
7. 7Feed the analysis into implementation and a feedback loop: structure resources, incentives, and monitoring around the position, then monitor execution to inform the next round of planning as forces shift.

Consider a company weighing entry into a mature manufacturing industry. Applying the experience curve, it finds unit costs decline roughly 20–30% each time cumulative production doubles, so incumbents with the highest market share hold a cost advantage — a strong barrier signaling low threat of profitable entry. Plotting the target business on the growth–share matrix (used by about 45% of the Fortune 500 by 1979), it sits low-growth, low-share: a divest-or-avoid quadrant. Rather than compete head-on on cost leadership, the firm instead chooses Porter's differentiation route, aligning its value-chain activities coherently around a distinctive service the largest incumbent never offers. It makes the trade-off explicit — declining to chase volume — and builds fit so rivals cannot easily copy the whole configuration. Structure then follows strategy, per Chandler, as resources are aligned to defend the position.

• If unit costs fall 20–30% per doubling of cumulative production, then high market share yields cost advantage — either pursue scale for cost leadership or avoid competing on price against the scale leader.
• If a business unit sits in low-growth, low-share territory, then divest or starve it; if high-growth, high-share, then invest resources there.
• If industry attractiveness is high but your competitive position is weak, then either build position deliberately or exit — do not straddle.
• If buyers can readily substitute products or hold strong bargaining power, then differentiation on attributes buyers rate as important must precede any price move.
• If you cannot name what you will NOT do, then you have no strategy — a valuable position requires explicit trade-offs and coherent activity fit.

• Analyzing the firm as a whole rather than its discrete value-chain activities — Porter warns competitive advantage 'cannot be understood by looking at a firm as a whole.' Tell: you can describe your advantage but not point to which specific activities produce it.
• Over-diversifying into unrelated industries as a conglomerate. Tell: deregulation-era logic shows the portfolio is worth more broken up than held together, because there is no shared technical or operating competence linking the units.
• Treating industry structure as static. Tell: you skip the feedback loop that monitors execution and informs the next planning round, so a shifted force (new entrant, new substitute) blindsides you.
• Marketing myopia — defining the industry by your product rather than by customer value. Tell: you never asked what the customer wants and produced for yourself instead, missing substitute threats entirely.
• Using a crude binary importance/performance matrix. Tell: everything looks either important or not, obscuring where performance is worse than competitors on attributes buyers actually rate as important; use nine-point scales instead.

• ▸Industry boundary: name the business, target customer, and how they buy.
• ▸Rivalry: describe competitive behavior of rivals; rate intensity high/low.
• ▸Buyer power: rate customers' bargaining power and cite the driver.
• ▸Supplier power: rate suppliers' bargaining power and cite the driver.
• ▸Threat of entry: note entry barriers, including experience-curve cost advantage.
• ▸Substitute threat: list products buyers could substitute and ease of switching.
• ▸Portfolio position: plot on industry growth rate × relative market share.
• ▸Chosen position: state the unique position and the explicit 'what not to do' trade-off.
• ▸Fit check: list value-chain activities and confirm they cohere to defend the position.