Greiner’s Growth Model
Organizations tend to grow through alternating periods of relatively calm evolution and disruptive crisis, and the very practices that successfully resolved one crisis, tighter direction, more delegation, more coordination, become the constraint that produces the next one.
What Is It?
Organizational theorist Larry Greiner proposed the model in a 1972 Harvard Business Review article, “Evolution and Revolution as Organizations Grow,” describing organizational growth as a sequence of five phases, each a period of relatively stable evolution dominated by a particular management style, ending in a crisis that has to be resolved before the organization can keep growing. An early, informal organization grows through creativity and founder energy until it hits a crisis of leadership, needing professional management; adopting stronger direction and formal systems produces growth through direction until it hits a crisis of autonomy, as lower-level managers chafe against centralized control; delegating more authority produces growth through delegation until it hits a crisis of control, as leadership loses visibility into an increasingly autonomous organization; adding coordination mechanisms, formal planning, shared services, produces growth through coordination until it hits a crisis of red tape, as the coordinating systems themselves become bureaucratic obstacles; and resolving that crisis through more collaborative, cross-functional, less formal management produces growth through collaboration, which Greiner left with an open question mark for the next crisis. In a 1998 Harvard Business Review retrospective, Greiner speculated about what might follow, including the psychological strain of sustained intense teamwork, rather than laying out a clean, named sixth phase, the tidy “Phase 6: alliances and networks” versions that circulate in some later diagrams are tidier than what Greiner’s own update actually said. The model’s central insight isn’t the specific number or names of the phases, it’s the pattern that each phase’s successful solution contains the seed of the next crisis, the very practices that solved the prior problem become, at a larger scale, the constraint that produces the next one. Greiner also treated the sequence itself fairly seriously, cautioning that skipping a phase’s developmental work could leave an organization without capabilities it would need later, so the sequence is best read as his proposed pattern rather than something he himself framed as loosely optional.
Why Does It Matter?
Leaders often treat organizational strain, a crisis of control, mounting bureaucracy, autonomy conflicts, as evidence something has gone wrong or that specific individuals are failing, when Greiner’s framework suggests some recurring strain can arise from the interaction between organizational growth and management practices that no longer fit the organization’s current scale, and that the practices that got an organization to its current size are often exactly what has to change to get it further. This reframes organizational pain from “we’re doing something wrong” to “we’re running into the limits of the solution that got us here,” a genuinely different diagnostic starting point.
What Changes Once You See It?
You start treating a specific kind of organizational strain, formalization strain, coordination strain, autonomy strain, as a clue that the organization may be encountering the limits of its current management pattern, rather than jumping straight to blaming individuals or specific decisions, and rather than diagnosing a specific numbered phase with false certainty. You get more skeptical of a leadership team that keeps reaching for the same solution that worked at an earlier size, more direction, more delegation, more process, without asking whether the organization has actually outgrown that particular lever, and without asking what problem that same solution might create if the organization keeps growing while still relying on it. You also start expecting that resolving one crisis will eventually produce a new one, rather than assuming a successful reorganization is a permanent fix.
Common Misunderstandings
- It isn’t a strict, universal sequence every organization passes through in exactly the same way. Greiner proposed it as a developmental sequence and was fairly explicit that skipping a phase’s work could leave capability gaps, but the evidence doesn’t justify treating that sequence as a universal law every organization must follow identically, industry, ownership structure, and external conditions all shape how growth actually unfolds.
- It doesn’t mean growth itself is the only variable that matters. Industry dynamics, technology change, ownership and governance structure, and market conditions all shape how an organization evolves, not size and age alone.
- It isn’t a claim that more formal structure or more delegation is always the right answer. The model’s insight is that the same solution that resolves one crisis tends to eventually become the source of the next one, not that any particular practice is universally correct.
- It isn’t based on longitudinal, controlled empirical research across a representative sample of organizations. It’s an influential synthesis of organizational growth literature and case-based observation, useful for organizing how to think about growth-related strain, not a rigorously tested predictive model, and Greiner himself described the phases as approximations rather than a precise, universal corporate life cycle.
Diagnostic Question
Is the friction we’re experiencing partly being produced by the management practices that previously enabled our growth?
Explore Further
Field Notes
- None yet.
Related Field Guide
Origin
Larry E. Greiner, “Evolution and Revolution as Organizations Grow,” Harvard Business Review (1972); revisited in a 1998 Harvard Business Review retrospective that speculated about what might follow the collaboration phase without laying out a settled sixth phase.