- Get link
- X
- Other Apps
The Stable-Dynamic Paradox in Modern Organization Design
Why the best organisations must be both stable and adaptable at the same time — and how they do it
Last Verified: 2026-09-16 | Author: Kateule Sydney | Published by Kat-Syd Resources Hub
The stable-dynamic paradox: organisations must maintain reliable operations while remaining adaptable to change.
Summary: Organisational design has traditionally treated stability and adaptability as opposing choices — either a firm is mechanistic and efficient, or it is organic and innovative. Modern organisations increasingly find that both are required simultaneously. This post examines the stable-dynamic paradox: why it exists, what organisational ambidexterity means, how firms structure themselves to be both reliable and adaptive, and what the historical record shows. Each section addresses the five core elements — why, what, when, who, and how — then closes with a blog analysis of pros and cons grounded in paired international and emerging-market cases.
Method: This post is written as case-based analytical writing. It does not claim personal experience. All cases are drawn from public sources and analysed through an original lens. Every section addresses the five core elements — why, what, when, who, and how — then closes with a blog analysis of pros and cons.
Introduction — The Paradox That Redefined Organisation Design
In 2013, the American technology company Adobe Systems announced that it would end the sale of perpetual software licences and move entirely to a subscription model. The move required two things simultaneously: the reliable operation of the existing Creative Suite product line that generated billions in annual revenue, and the rapid development of a new cloud-based platform (Creative Cloud) that would replace it. Adobe could not afford to stop either. It had to run the existing business at full execution speed while building its replacement. By 2023, Adobe’s annual revenue had grown from $4 billion to over $19 billion, and its cloud platform served over 30 million paying subscribers.
The stable-dynamic paradox is defined by Charles O’Reilly and Michael Tushman in “Organizational Ambidexterity: Past, Present, and Future” as “the tension between the need for organisations to exploit existing capabilities for efficiency and to explore new capabilities for innovation.” The paradox is not a problem to be solved but a tension to be managed. Organisations that resolve it entirely in favour of stability lose adaptability. Organisations that resolve it entirely in favour of adaptability lose the operational reliability that generates the resources for future adaptation.
This post examines four interlocking components of the stable-dynamic paradox:
- The paradox itself — what it is and why traditional organisation theory cannot resolve it
- Ambidexterity — the capacity to exploit existing capabilities and explore new ones simultaneously
- Structural solutions — the design choices that firms use to manage the paradox
- Leadership and contextual ambidexterity — how leaders create conditions for both stability and adaptation within the same organisation
The analysis draws on two academic traditions. The first is the contingency tradition established by Burns and Stalker, which treats mechanistic and organic structures as appropriate to different environments. The second is the ambidexterity tradition established by Duncan, refined by Tushman and O’Reilly, and extended by Gibson and Birkinshaw, which argues that the most effective organisations develop the capacity to be both. Where the two traditions conflict, the cases in this post favour the ambidexterity reading.
Chapter 1 — What the Stable-Dynamic Paradox Is and Why It Matters
Definition. The stable-dynamic paradox is defined by Wendy Smith and Marianne Lewis in “Toward a Theory of Paradox” as “contradictory yet interrelated elements that exist simultaneously and persist over time.” The definition contains three components that distinguish a paradox from an ordinary problem:
- Contradiction — the two elements appear to be in opposition
- Interrelation — the two elements depend on each other for their effect
- Persistence — the tension cannot be eliminated by choosing one side over the other
Explanation. Traditional organisation theory treated stability and adaptability as separate design choices. The contingency tradition assumed that the correct structure could be selected on the basis of the environment: stable environments called for mechanistic structures, and volatile environments called for organic ones. Subsequent research identified three reasons why this assumption fails:
- Multiple environments — firms face different environments in different product markets simultaneously; a single structural choice cannot match all of them
- Environmental change — environments shift faster than organisational structures can be redesigned; firms cannot re-structure every time the market moves
- Internal contradiction — exploration requires different processes, metrics, and incentives than exploitation; the two cannot be managed by the same system
The interpretive insight is that the stable-dynamic paradox is not a problem to be solved but a tension to be managed. The organisations that thrive are those that build mechanisms for managing the tension rather than choosing one side.
The Five Core Elements. The paradox must address five questions in a fixed order. Together they form the operational logic of the discipline.
- Why it is done that way — because organisations need both reliable execution of current operations and adaptability to future conditions; neither can be sacrificed for the other
- What is supposed to be done — build mechanisms that allow the organisation to exploit existing capabilities and explore new ones simultaneously
- When it is done — continuously; the tension is permanent, not episodic; the balance may shift as the organisation’s dominant challenge changes
- Who does what — senior leadership must protect both dimensions; separate units may be assigned different mandates; middle management must integrate across them
- How it is supposed to be done — through structural separation, contextual design, or leadership behaviour that recognises and manages the tension
Case study. The collapse of Blockbuster Video in the 2000s provides a case in point for the failure to manage the paradox. Blockbuster’s existing business — physical video rental stores — was highly profitable in the 1990s, generating over $5 billion in revenue at its peak in 2004. The company’s leadership chose to protect the existing business rather than invest in a digital alternative. When Netflix offered to sell itself to Blockbuster for $50 million in 2000, Blockbuster declined, and internal resistance to developing a competitive digital offering was strong because it threatened the profitability of the store-based model. By 2010, Blockbuster had filed for bankruptcy, and Netflix had grown to over 20 million subscribers. By contrast, Microsoft’s transition from perpetual software licences to a subscription-based cloud model in the 2010s demonstrates the alternative. The company maintained its legacy Office and Windows businesses while simultaneously building Azure, Office 365, and other cloud services. Under Satya Nadella’s leadership from 2014, Microsoft redesigned its organisational structure to support both businesses, and by 2024 Azure was generating over $60 billion in annual revenue while Office and Windows remained profitable.
Blog Analysis — Pros and Cons. The evidence from Blockbuster and Microsoft supports the following assessment.
- Pros: Organisations that manage the paradox (Microsoft) preserve existing capabilities while building new ones, and produce superior long-term outcomes. The paradox approach treats the tension as a source of strength rather than an either-or decision.
- Cons: Managing the paradox requires continuous senior leadership attention and is costly. Resources are diverted from the profitable existing business to fund the uncertain new one. Blockbuster’s decision to protect its existing business was rational in the short term; the failure mode is short-term rationality that produces long-term destruction.
Chapter 2 — Organisational Ambidexterity: Exploration and Exploitation
Definition. Organisational ambidexterity is defined by Charles O’Reilly and Michael Tushman in “The Ambidextrous Organization” as “the ability of an organisation to be aligned and efficient in its management of today’s business demands while simultaneously being adaptive to changes in the environment.” The term was first introduced by Robert Duncan in 1976, who distinguished between “initiating” and “implementing” innovation, and has been developed into one of the most influential frameworks in organisation theory.
Explanation. Ambidexterity is built on the distinction between two modes of organisational activity, defined by James March in 1991:
- Exploitation — refinement, efficiency, and execution of existing capabilities; produces incremental improvement
- Exploration — experimentation, discovery, and development of new capabilities; produces radical innovation
The interpretive insight is that exploitation and exploration require different organisational conditions, which is why managing both simultaneously is difficult. Exploitation requires efficiency, standardisation, and tight control. Exploration requires flexibility, experimentation, and tolerance for failure. The same processes, metrics, and incentives cannot support both. Ambidextrous organisations build mechanisms to separate the two modes while maintaining integration at the strategic level.
The Five Core Elements.
- Why it is done that way — because firms that only exploit eventually become obsolete, and firms that only explore eventually run out of resources to fund their experimentation
- What is supposed to be done — maintain the existing business at full execution speed while separately developing new capabilities that may eventually replace it
- When it is done — exploration is continuous, not episodic; exploitation is continuous; the allocation of resources between the two shifts as the strategic environment changes
- Who does what — exploration units are typically separated from the core business; senior leadership integrates across the two; exploitation units run on established processes
- How it is supposed to be done — through separation of exploratory and exploitative units, with integration at the senior leadership level
Case study. IBM’s transition from hardware to services in the 1990s provides a case in point. Under CEO Lou Gerstner, IBM maintained its mainframe and PC businesses while simultaneously building a global services business (IBM Global Services). The services business was structured separately from the hardware business, with its own leadership, metrics, and culture. By 2001, services accounted for over 40% of IBM’s revenue and had become the company’s primary growth engine. IBM’s subsequent transition into cloud and AI in the 2010s followed the same model, with IBM Cloud and Watson developed in units separate from the traditional businesses. By contrast, Eastman Kodak’s failure to build an ambidextrous structure contributed to its decline. Despite inventing the first digital camera in 1975, Kodak protected its film business against digital alternatives. When digital photography finally disrupted the market, Kodak had no separate organisational unit with the capability to develop a digital business. The company filed for bankruptcy in 2012.
Blog Analysis — Pros and Cons. The evidence from IBM and Kodak supports the following assessment.
- Pros: Ambidextrous organisations (IBM) develop the capability to survive multiple technology transitions because they build the new business while running the old one. The separation principle keeps exploration insulated from exploitation’s pressure for short-term results.
- Cons: Ambidexterity is expensive and difficult. Exploration units consume resources without producing revenue in the early years, and are often the first candidates for cost-cutting when the core business is under pressure. Kodak had the technology and the opportunity; what it lacked was the organisational commitment to protect exploration from exploitation.
Chapter 3 — Structural Solutions for Managing the Paradox
Definition. Structural solutions for managing the paradox are defined by Julian Birkinshaw and Cristina Gibson in “Building Ambidexterity into an Organization” as “the design choices that allow an organisation to simultaneously pursue incremental and radical innovation.” The literature identifies three structural approaches: structural separation, contextual ambidexterity, and sequential ambidexterity.
Explanation. Each structural approach makes a different trade-off:
- Structural separation — exploration units are set up as distinct organisational entities; clear separation, but risks isolation of the exploratory unit and integration failure at the top
- Contextual ambidexterity — individuals divide their time between exploration and exploitation within the same unit; flexible, but requires strong behavioural norms and cannot scale easily
- Sequential ambidexterity — the organisation alternates between exploration and exploitation across time; simple to manage, but can leave the firm exposed when rapid change occurs during an exploitation phase
The interpretive insight is that the choice between structural approaches is not a matter of preference but of fit. High-tech firms typically favour separation. Knowledge-intensive firms where individual judgment matters more than unit structure favour contextual ambidexterity. Firms in slower-moving industries may find sequential ambidexterity sufficient.
The Five Core Elements.
- Why it is done that way — because the paradox requires different mechanisms for exploitation and exploration; structure is the most reliable mechanism for maintaining both simultaneously
- What is supposed to be done — select the structural approach that matches the firm’s technology, market pace, and coordination capability
- When it is done — at major strategic transitions; when existing structures demonstrably fail to support both dimensions; on major environmental shift
- Who does what — senior leadership selects and protects the chosen structure; middle management operates the integration; unit-level managers run the exploration and exploitation activities
- How it is supposed to be done — through deliberate design, not accretion; with clear boundaries between exploration and exploitation units and clear integration mechanisms at the top
Case study. Amazon’s two-pizza team model and its associated structure provides a case in point. Amazon separates most business units into small autonomous teams (traditionally small enough to be fed by two pizzas), with each team owning a defined customer problem. The structure supports exploitation within each team while allowing new teams to be created for exploratory ventures such as AWS, Kindle, and Alexa. AWS was developed as a separate unit within Amazon, with its own leadership, metrics, and eventually its own branding. When AWS became successful, it was integrated into the Amazon structure without altering the underlying two-pizza team principle. By contrast, the Chinese technology company Tencent operates a different structural model. Tencent’s core business is gaming and social media (WeChat and QQ), and the company maintains separate business groups for each major product line. Exploration happens within these groups, with internal competition between teams encouraged. The company has produced several major innovations through this structure, including the WeChat Mini Programs platform and Tencent Cloud, but the model has also produced internal resource duplication and political friction between business groups.
Blog Analysis — Pros and Cons. The evidence from Amazon and Tencent supports the following assessment.
- Pros: The choice between structural separation (Amazon) and internal competition (Tencent) reflects the firm’s technology, market pace, and cultural norms. Both structures have produced sustained innovation across multiple technology transitions. The key is that each firm has chosen a structure that matches its context.
- Cons: Both structures have predictable costs. Amazon’s two-pizza team model can produce coordination problems as the number of teams grows, requiring investment in shared infrastructure. Tencent’s internal competition model produces resource duplication and organisational politics. The failure mode for both is when the structure that supported past innovation becomes the structure that blocks future innovation.
Chapter 4 — Leadership and Contextual Ambidexterity
Definition. Contextual ambidexterity is defined by Cristina Gibson and Julian Birkinshaw in “The Antecedents, Consequences, and Mediating Role of Organizational Ambidexterity” as “the behavioural capacity to simultaneously demonstrate alignment and adaptability across an entire business unit.” The definition shifts the location of ambidexterity from structure to leadership behaviour. Rather than separating exploration and exploitation into different units, contextual ambidexterity asks individual managers to do both within their own scope.
Explanation. Contextual ambidexterity requires four leadership conditions:
- Discipline — clear standards and expectations for both dimensions
- Stretch — ambitious goals that cannot be met through exploitation alone
- Support — resources and permission for exploratory activity within the operational unit
- Trust — the expectation that managers will use their judgment rather than being directed from above
The interpretive insight is that contextual ambidexterity shifts the management problem from structure to culture. The conditions are behavioural, not structural. They can be built into any structure, but they cannot be built into a structure that does not support them.
The Five Core Elements.
- Why it is done that way — because structural separation is not always feasible; some organisations cannot afford the overhead of separate exploration units and must develop the capacity to explore within the operational unit
- What is supposed to be done — build the four conditions for contextual ambidexterity into the behaviour and culture of the organisation
- When it is done — continuously; contextual ambidexterity is a behavioural capacity, not a periodic exercise; senior leadership must model it consistently
- Who does what — senior leadership creates the conditions and protects them; middle managers practice both exploitation and exploration within their scope; HR builds systems that reward both
- How it is supposed to be done — through leadership behaviour, cultural norms, and management systems that do not punish exploration when it produces failure
Case study. The Japanese electronics manufacturer Fujifilm provides a case in point for contextual ambidexterity. When film photography collapsed in the 2000s, Fujifilm had no separately structured digital business to fall back on. The company survived because it had developed, over decades, a culture in which managers were expected to develop new applications for existing chemical and imaging capabilities. The same film manufacturing expertise that had supported photographic film was applied to cosmetic chemicals, pharmaceutical compounds, and optical devices. By 2024, Fujifilm’s revenue was more than twice what it had been at the peak of its film business in the early 2000s. By contrast, Nokia’s transition from paper to rubber to telecommunications to mobile phones in the twentieth century had been based on structural separation and periodic reinvention. When Nokia attempted to transition from mobile phones to smartphones in 2010, it did not have the contextual capacity to explore new technologies within its existing operational units. The company’s mobile phone business was highly efficient at exploitation, but it could not explore. Nokia’s mobile phone business was sold to Microsoft in 2013.
Blog Analysis — Pros and Cons. The evidence from Fujifilm and Nokia supports the following assessment.
- Pros: Contextual ambidexterity (Fujifilm) allows organisations to explore within their operational units, avoiding the overhead of structural separation and the coordination problems that come with separate units. When the culture supports it, the same people who run the existing business can develop its replacement.
- Cons: Contextual ambidexterity is difficult to develop and impossible to retrofit. Organisations that have not built the four conditions over time cannot simply adopt them when the environment changes (Nokia). The failure mode is a firm that has invested in operational efficiency to the exclusion of behavioural capacity, and then discovers that it cannot explore when it needs to.
You Might Also Want to Read
Revenue Growth Playbook Series — A complete framework for turning strategy into sustained top-line growth.
Marketing Strategy Mastery Series — Positioning, differentiation, and the strategic decisions that precede execution.
B2B Marketing Mastery Series — Buyer committees, long sales cycles, and enterprise-grade operations.
Comments
Post a Comment