Skip to main content

Featured

Shareholder Primacy vs. Stakeholder Theory: A Critical Analysis of Corporate Legal Obligations

The debate between shareholder primacy and stakeholder theory concerns the legal obligations of corporate directors. Introduction A corporation is never just a machine for making money. It is a legal institution, a social system, and a vehicle for allocating power, risk, and responsibility. That is why one of the most important debates in corporate governance continues to divide scholars, executives, regulators, and investors: should corporations exist primarily to maximize shareholder value, or should they balance the interests of all the people and institutions affected by their actions? This debate is commonly framed as shareholder primacy vs. stakeholder theory. Shareholder primacy says the corporation's central obligation is to its owners, the shareholders. Stakeholder theory says the corporation owes duties to a wider circle of affected parties, including employees, customers, suppliers, creditors, communities, and sometimes society at large. This is not a purely academ...

Reconciling Deliberate and Emergent Strategy

This post is a deep dive into Mintzberg's deliberate and emergent strategy distinction: the 1985 framework, the Honda case that illustrates it, the Honda Effect debate that complicates the narrative, and the criticisms the framework has attracted.

By Kateule Sydney — Researcher and Writer | Last Verified: 2026-09-30 | Published by Kat-Syd Resources Hub
Strategy team analysing deliberate and emergent strategy patterns
Mintzberg's deliberate and emergent strategy: how plans and patterns differ

I Put Mintzberg's Deliberate and Emergent Strategy on Trial, and the Distinction Survives, but the Honda Case Does Not Prove It

Mintzberg and Waters developed the deliberate and emergent strategy distinction in their 1985 article "Of Strategies, Deliberate and Emergent," published in Strategic Management Journal. The claim is that strategy is not only what a firm plans to do, but also what it actually does over time. A deliberate strategy is one that was intended and realized. An emergent strategy is a pattern that develops without having been intended in advance. The central claim is that understanding both is necessary to explain what a firm actually does.

I want to give the framework its strongest version of its own case before I challenge it. Mintzberg and Waters did not simply say that some strategies are planned and some are not. They identified a spectrum of strategy types, from pure deliberate to pure emergent, and argued that most real strategies fall somewhere along that spectrum. The framework's value is diagnostic. It forces managers to ask whether what their firm is actually doing matches what their firm said it would do, and if not, whether the difference is drift or learning.

The framework rests on several distinctions that Mintzberg and Waters set out clearly:

  • Intended strategy — what the firm planned to do
  • Deliberate strategy — the part of the intended strategy that was actually realized
  • Unrealized strategy — the part of the intended strategy that was abandoned or not achieved
  • Emergent strategy — patterns that developed without having been planned, which can be coherent without having been intended
  • Realized strategy — the strategy the firm actually pursued, which may contain both deliberate and emergent elements

The framework is often described as a simple choice between planning and adaptation. That is not what Mintzberg and Waters wrote. Their contribution was to show that realized strategy is not the same as intended strategy, and that the gap between the two is where learning happens. Emergent strategy is not the absence of strategy. It is the recognition that some patterns become strategy without having been planned as such.

I will test the framework against three questions:

  • Does the framework's distinction hold up? — is the difference between deliberate and emergent strategy analytically useful
  • Does the Honda case prove the framework? — the case is often cited as the standard illustration, but the evidence is more contested than the standard account suggests
  • Where does the framework fall short? — what does the deliberate-emergent distinction miss about how strategy actually forms

My thesis is that Mintzberg's deliberate-emergent distinction is a genuinely useful diagnostic, but the Honda case does not demonstrate that planning failed and emergence prevailed. Honda's entry into the US motorcycle market illustrates how intended strategy can be substantially reshaped through experience, adaptation, and learning. It should not be treated as evidence that planning is obsolete.

The Witnesses Testify to a Simple Question: Is Strategy Planned or Does It Emerge?

Mintzberg and Waters were not writing in a vacuum. By the mid-1980s, the dominant view in strategic management was that strategy was a formal planning exercise conducted by top management and communicated down through the organization. The planning school, associated with Igor Ansoff and others, held that strategy could be formulated systematically and then implemented. Mintzberg came from a different tradition. His work on the nature of managerial work and the reality of organizational decision-making suggested that strategy often formed through patterns of action, not through formal planning.

The witnesses for the framework include Mintzberg and Waters themselves, writing in Strategic Management Journal in 1985, and the later work of Mintzberg, Ahlstrand, and Lampel in Strategy Safari, which classified the learning school as "strategy formation as an emergent process." The framework's animating question is not "how do we plan strategy" but "what strategy are we actually following, regardless of what we said we would do?"

The framework's defenders make three specific claims:

  • Realized strategy differs from intended strategy — the strategy a firm actually pursues is not the same as the strategy it set out to pursue, and the difference matters
  • Emergent strategy is not the absence of strategy — coherent patterns can develop without having been planned, and those patterns deserve to be called strategy
  • Both deliberate and emergent strategies are legitimate — the framework does not claim that one is superior to the other; it claims that both occur and both must be understood

I find these claims convincing. The distinction between intended and realized strategy is analytically important, and the recognition that coherent patterns can emerge without prior intention corrects a bias in the planning school. But I want to be clear about what the framework does not say. Mintzberg and Waters did not argue that all strategy should be emergent. The Strategy Safari project presents ten schools of strategic thought as different perspectives, not as competing claims where one is correct and the others are wrong.

The framework attracted criticism from the planning tradition, most notably from Igor Ansoff, who argued that the learning school understates the role of deliberate analysis and overstates the role of front-line experimentation. Ansoff's critique, published in various forms through the 1990s, holds that the deliberate-emergent distinction risks excusing poor planning by relabelling failure as learning. That criticism has force, and I will return to it in the cross-examination.

The defense must show that the framework can distinguish between genuine emergence and the rationalization of drift. That is what the practice section will test.

The Practice Evidence Shows the Framework's Diagnostic Value, but Honda Does Not Prove It

The framework proposes that understanding both deliberate and emergent strategy is necessary to explain what a firm actually does. I want to test that proposal against the case that is most often used to illustrate it.

The Honda case is the standard illustration, and I want to give the standard account its strongest form before I qualify it. According to the account that Richard Pascale published in 1984, Honda entered the US motorcycle market in 1959 with an intended strategy of selling large-engine machines to American buyers. The plan did not work as expected. Large-engine sales were slow, and the small Super Cub bikes that Honda's own executives had been using for local transport in Los Angeles began to attract American buyers. Over the following years, Honda adjusted, and by 1966 it dominated the US motorcycle market. On the standard reading, the realized strategy was substantially different from the intended strategy, and the emergent element — small bikes sold to ordinary Americans — became the basis of Honda's success.

I am judging the practice evidence against three criteria:

  • Does the case show intended and realized strategy diverging? — the Pascale account supports this; the intended strategy and the realized strategy were not the same
  • Does the case prove that emergence was the cause of success? — no; the case is a contested interpretation, not a controlled experiment
  • Is the framework useful for understanding the case? — yes; the deliberate-emergent distinction helps explain what happened, even if it does not prove a general law

My position is that the practice evidence supports the framework as a diagnostic tool for understanding how strategy actually forms. It does not support the stronger claim that Honda's success proves emergence is superior to planning. The Honda case is instructive, but it is a single case with a contested interpretation, and later debate — the Honda Effect debate published in California Management Review in 1996 — complicated the simple narrative by showing that Honda's approach included substantial planning, learning, and leadership judgement, not only emergent adaptation.

The framework is useful. The Honda case illustrates it. Neither proves that planning is obsolete.

The Cross-Examination Exposes a Structural Weakness: Emergence Is Hard to Distinguish from Drift

The framework's first major weakness is that it does not provide a clean test for distinguishing emergent strategy from drift. A pattern that develops without prior intention can be learning, or it can be incoherence that gets rationalized after the fact. Mintzberg and Waters recognized this problem, but the framework does not resolve it. The distinction between emergent strategy and drift is analytical, and the analyst has to supply the judgment.

Ansoff's critique of the learning school has force here. If a firm abandons its plan and pursues something else, the framework can call that emergent strategy. But it can also be called failure to execute. The difference between the two is not determined by the framework. It is determined by whether the new pattern turned out to be coherent and successful. That is an outcome-based judgment, not a framework-based one. The framework risks relabelling failure as learning whenever the outcome happens to be favorable.

The three recurring failure modes I identify are:

  • Emergence versus drift — the framework does not specify how to distinguish a coherent pattern that emerged from incoherent activity that happened to produce a favorable result
  • Outcome bias — successful departures from plan tend to be called emergent strategy; unsuccessful ones tend to be called failure to execute; the framework is vulnerable to reading strategy backwards from results
  • The Honda Effect — the standard illustration is contested; the case that is most often used to prove the framework has been shown to be more complicated than the simple account suggests

My position is that the failures are structural to the framework's application, not to the framework itself. Mintzberg and Waters did not claim that the distinction could be applied mechanically. They claimed it was a useful lens. The problem is that in practice the lens is often used as if the answer were obvious, when it is not.

The cross-examination has established its strongest point: the framework is analytically useful but operationally under-specified. It tells you to look for both deliberate and emergent elements. It does not tell you how to tell the difference between learning and drift in the moment.

The Defense Rests on Diagnosis: The Framework Helps Firms See What They Are Actually Doing

The framework's defenders have a strong response. They do not claim the deliberate-emergent distinction produces mechanical answers. They claim it forces a question that most firms avoid: what strategy are we actually following, regardless of what we said we would do?

Mintzberg, Ahlstrand, and Lampel made this point explicitly in Strategy Safari. The learning school does not reject planning. It argues that strategy formation is often distributed across the organization, and that leadership's role includes recognizing, legitimizing, and codifying the patterns that emerge. That is a legitimate management function, and it is what the framework supports.

The framework delivers the most value under three conditions:

  • When the plan and reality diverge — the framework helps firms see the divergence instead of denying it
  • When front-line learning matters — the framework legitimizes what employees closest to customers already know
  • When strategy formation is ongoing — the framework treats strategy as a pattern that forms over time, not a document finalized in a planning cycle

A skeptic might argue that the defense concedes too much. If the framework cannot distinguish emergence from drift, then it is a description, not a tool. I take that objection seriously. But the defense has shown that the framework still does useful work where it was designed to be used. It forces leaders to attend to what is actually happening, not only what was planned. That discipline is valuable even if the framework does not resolve every judgment call.

The question for the verdict is not whether the framework can be applied mechanically. It is whether the framework earns its place in a manager's diagnostic toolkit.

The Verdict: A Useful Diagnostic That Is Often Overread and Under-Specified

Mintzberg and Waters introduced the deliberate-emergent distinction in 1985, and it remains a useful diagnostic for understanding how strategy actually forms. Its central insight — that realized strategy differs from intended strategy, and that the difference is where learning happens — is correct and valuable. The framework helps firms see what they are actually doing, regardless of what they said they would do.

But the framework is often overread as evidence that planning is obsolete, and it is under-specified as a tool. The Honda case, which is most often used to illustrate the framework, is more contested than the simple account suggests. The Honda Effect debate complicated the narrative by showing that Honda's approach included planning, learning, and leadership judgement, not only emergent adaptation. And the framework does not provide a clean test for distinguishing emergent strategy from drift, which means it can be used to rationalize failure as learning after the fact.

A defender might argue that the framework's continued use in strategy teaching and practice is at least consistent with continuing practical value. I accept that. Longevity can reflect teaching conventions as much as analytical superiority. My criticism is not that the deliberate-emergent distinction fails as a diagnostic. It is that firms applying the framework as a validation of emergent strategy over planning will misread what the framework was designed to do.

My recommendations for practitioners are these:

  • Use it as a diagnostic, not a validation — run the framework to understand where your realized strategy has diverged from your intended strategy, not to prove that emergence is superior to planning
  • Distinguish emergence from drift — ask whether the pattern you are seeing is coherent and learning-driven, or incoherent activity that happens to be producing a favorable result
  • Do not use Honda as a simple proof case — the Honda Effect debate showed the case is more complicated than the standard account suggests; use it as an illustration, not as a demonstration
  • Combine deliberate planning with ongoing learning — the framework does not require choosing between planning and adaptation; it requires attending to both
  • Treat strategy as a pattern, not a document — the framework's most useful contribution is that strategy is what the firm does over time, not only what the firm planned

Mintzberg's deliberate-emergent distinction is a useful diagnostic tool, but its central case is contested and its central question is harder to answer than its popularity suggests. The firms that use it well are the ones that understand what it can and cannot tell them.

Read Also on Kat-Syd Resources Hub

Porter's Five Forces: Deep Dive, Origins & Limits — The five competitive forces that shape industry profitability, and the criticisms the framework has attracted.

McKinsey 7S Framework: Deep Dive, Origins & Limits — Seven interdependent elements that determine organizational effectiveness.

The Stable-Dynamic Paradox in Modern Organization Design — Why firms must be stable enough to execute and fluid enough to adapt.

Written by Kateule Sydney — Researcher and Writer

© 2026 Kat-Syd Resources Hub. All rights reserved.

Kat-Syd Resources Hub — Educational case studies and analytical reference

You might also want to read

Porter's Five Forces: Deep Dive, Origins & Limits

Porter’s Five Forces is examined here as an industry-analysis framework for understanding competitive pressure and the distribution of economic value. This post traces the framework’s 1979 origins, tests its claims against case applications to East African Breweries and Shopee Indonesia, and evaluates recent conceptual extensions proposed for digital, algorithmic, and platform competition. The central argument is that Five Forces remains valuable within its proper scope, but is neither obsolete nor complete. By Kateule Sydney — Researcher and Writer | Research Audit: 2026-10 | Published by Kat-Syd Resources Hub Porter’s Five Forces is neither obsolete nor complete. It remains a strong framework for analysing industry structure and competitive pressure, but its conclusions should be supplemented when firm-level, ecosystem, technological, regulatory, and dynamic factors materially affect competition. Table of Contents Origins and Purpose What the Five Forces Actually Analyse ...

SWOT Analysis in Marketing: The Complete Framework for Strategic Market Assessment

Strengths, Weaknesses, Opportunities, and Threats — Mapped to Real Marketing Strategy, Case Studies, and Campaign Execution Last Verified: 2026-09-11 | Author: Kateule Sydney | Published by Kat-Syd Resources Hub Source: Kat-Syd Resources Hub / Unsplash Summary: SWOT Analysis remains the most widely used strategic framework in marketing because it forces disciplined thinking about internal capabilities and external forces. This comprehensive guide walks through every stage — the internal marketing audit, external market analysis, the SWOT/TOWS matrix, real-world case studies from Netflix, Apple, LEGO, Starbucks, and DTC brands, plus templates, workshop facilitation tips, and integration with PESTLE, Porter's Five Forces, and VRIO. Table of Contents Introduction — Why Every Marketing Strategy Starts with SWOT Chapter 1 — What Is SWOT Analysis in Marketing? Chapter 2 — Conducting...

Agile Productivity: Why Organizations Accumulate Activity Without Output

A playbook on the productivity paradox, institutional concentration, and the discipline of agile execution Last Verified: 2026-09-12 | Author: Kateule Sydney | Published by Kat-Syd Resources Hub The productivity paradox: organizations generate more activity than output Summary: Despite 43% of executives ranking productivity growth as their top priority, organizations continue to accumulate activity without commensurate output. This playbook examines the structural roots of organizational busyness, introduces institutional concentration as a counterweight, and demonstrates how integrating agility with disciplined focus creates a sustainable productivity model. Table of Contents Introduction — The Productivity Reckoning Chapter 1 — The Productivity Imperative: A Defining Challenge Chapter 2 — The Roots of Organizational Busyness Chapter 3 — Institutional Concentration as a Co...

Formal Planning Systems and Their Limits

This post is a deep dive into Mintzberg's distinction between strategic planning and strategic thinking, and the case for adaptive planning under uncertainty. The analysis is tested against two different adaptations of formal planning under changing conditions, including General Electric's planning evolution and Safaricom's layered planning model. By Kateule Sydney — Researcher and Writer | Last Verified: 2026-10-01 | Published by Kat-Syd Resources Hub Strategic planning versus strategic thinking: analytical discipline versus synthesis Table of Contents The Claim The Witnesses The Practice The Cross-Examination The Defense The Verdict References I Put the Planning-Adaptation Binary on Trial, and the Real Question Is Not Whether to Plan but How The framework I am examining is the distinction between strategic planning and strategic thinking, most clearly drawn by Henry Mintzberg in his 1994 Harvard Business Review article "The Fall and R...

Integrating Management Functions

Bringing together planning, organizing, staffing, directing, and controlling into an integrated framework for management practice. Last Verified: 2026-09-13 | Author: Kateule Sydney | Published by Kat-Syd Resources Hub Integrating the five management functions: planning, organizing, staffing, directing, and controlling. Summary: The integration of management functions represents the culmination of managerial practice, where planning, organizing, staffing, directing, and controlling operate as an interdependent system. This playbook examines how these functions interact dynamically, how managers can diagnose organizational challenges using established diagnostic frameworks, and how management capabilities develop through deliberate practice. Table of Contents Introduction — The Imperative of Integration Chapter 1 — The Interdependence of Management Functions Chapter 2 — Diagnosing ...