Strategy and Structure Make Each Other is an essay on the relationship between strategy and organizational structure for leadership teams restructuring to pursue a new strategy. It shows why a structure designed only to execute today's strategy can block the conversations the next strategy needs.
The structure a company already has, from its reporting lines to its meetings, budgets and performance measures, decides which strategies its leaders can see and which ones the company can act on. Business schools and strategy textbooks teach the opposite order: choose the strategy first, then design a structure to deliver it. A leadership team that follows that sequence agrees on a new strategy and, within weeks, approves a new organization chart. The chart changes who reports to whom, and the rest of the structure goes on deciding what the company notices next and how well it delivers.
A new organization chart leaves the old way of working in place
When leaders call for more speed, flexibility or innovation, the first change they announce is often a new organization chart. A reorganization is visible, fits on one slide and can be announced immediately.
The governance forums, the policies, the budgets and the measures people are judged by stay as they were after a reorganization, and those elements pull the organization back toward the way it worked before. In our experience, the new chart soon describes old habits under new names.
An unchanged structure can cancel one team's gains
The surrounding structure also pulls back a single team that changes how it works. We saw that happen in the ecommerce group of a big-box furniture retailer. The group's software engineering team had completed an Agile transformation, and the teams around it stayed as they were. Upstream, marketing still worked in a functional silo and specified each new initiative in full before handing it to engineering. Downstream, quality testing reported to a different leader and ran a waterfall delivery process. No forum brought the three teams together to plan the work.
Across the ecommerce group, the mismatch added delay, coordination cost and friction, and the transformation's promised benefits never appeared. In our judgment, the useful measure of a redesign is the flow of work across the whole group, from the first idea in marketing to the tested release, because the slowest unchanged stage sets the pace for the whole flow.
Structure decides which strategies a company can see
The strategy-first sequence has hardened into orthodoxy, and in our view teaching it keeps producing redesigns that change the chart and leave results where they were. The rule that structure follows strategy began as a description of how large American firms reorganized as they grew between the 1910s and the 1950s. Strategy textbooks turned the description into a method: formulate the strategy, then implement it, with organization design listed under implementation. In that method, strategy is an input handed down finished from the top, and structure is the container that receives it. Business schools teach the method to each new class of managers, many of whom repeat it in their own redesigns. The rule suits a company executing a settled strategy. A company that needs its next strategy finds that the rule leaves out what its existing structure decides.
Structure decides who talks to whom, how often and about what. A company organized around the parts of its current products sees improvements to each part quickly. That company is slow to see a change in how those parts fit together. Its reporting lines, its meetings and the reports that decide what reaches leaders were built for the product as it was, so they can hide that kind of change.
Strategy often forms in conversation before it appears in any plan. Someone sees a customer behaving differently, raises it with a colleague in another function, and a new option emerges between them. When the structure keeps those two people apart, the conversation does not happen and the option never forms.
Strategy and structure change each other in turn. A major strategic choice, such as entering a new market, changes the organization that made it, and the organization then sets the range of choices its leaders can see next. Structure follows strategy, and strategy follows structure, in a loop that keeps running.
An efficient structure can block the conversations a new strategy needs
Companies designed for efficient operations route attention to cost, throughput and process control. Each function builds deep specialist expertise, hand-offs between functions are standardized, and management forums review variance against plan.
We have seen the loop matter most when such a company sets out to offer new products and services. Its structure offers no place for the conversations that could widen the company's options. What the service desk learns about customers stays at the service desk. No forum exists where an unproven idea can be discussed without being judged against this quarter's targets.
A company that pursues efficient operations and new products at once needs two kinds of unit, each run by its own rules. The core business works best with tightly specified roles and vertical control. The exploratory unit needs looser roles, lateral conversation and shared judgment. It also needs a link to the core business through the senior leadership team, so what it learns reaches the people who decide where money goes.
Design the structure so the next strategy can emerge
A leadership team that designs for the loop asks two questions when it redesigns: "Which structure will execute this strategy?" and "Which conversations will this structure make easy, which will it make hard, and which strategies will we stop seeing as a result?"
In our experience, the answers point to three design choices. Exploration gets room inside the structure, with clear links to the core business, so new options can be tried while current operations run. Conversations across functions, such as marketing with engineering, become part of the design, with their own forums, decision rights and measures, because new strategy often forms in those conversations. Structure is revisited in small steps after each major strategic choice, because the loop turns again with each choice.
A leadership team that asks both questions before it draws the new chart is designing the organization that will choose its next strategy.
To see how leadership teams put these ideas to work, explore the talk Redesigned to Disrupt: How Successful Organizations Explore New Value While Running What Works, or request a briefing.
Questions leaders ask about strategy and structure
Does structure follow strategy?
Yes, and strategy also follows structure, in a continuing loop. A major strategic choice changes the organization that made it. Its reporting lines, meetings, budgets and measures then decide which strategies its leaders can see next. In our view, the rule that strategy comes first suits a company executing a settled strategy and leaves out what its structure decides.
Why doesn't a reorganization change how a company works?
A reorganization redraws the organization chart, which changes who reports to whom and leaves the rest of the structure in place. The governance forums, policies, budgets and performance measures stay as they were, and those elements pull the organization back toward its old way of working. In our experience, the new chart soon describes old habits under new names.
How should leaders design structure for a new strategy?
Leaders should design a structure that executes the current strategy and lets the next one emerge. In our experience, exploration needs room inside the structure, linked to the core business, so new options can be tried while operations run. Conversations across functions need their own forums, decision rights and measures, because new strategy often forms in those conversations.
References (7)
- Alfred D. Chandler Jr., Strategy and Structure: Chapters in the History of the American Industrial Enterprise, MIT Press, 1962. The origin of the rule that structure follows strategy.
- Rebecca M. Henderson and Kim B. Clark, "Architectural Innovation: The Reconfiguration of Existing Product Technologies and the Failure of Established Firms," Administrative Science Quarterly 35, no. 1 (1990), pages 9 to 30. https://doi.org/10.2307/2393549
- Ralph D. Stacey, Complex Responsive Processes in Organizations: Learning and Knowledge Creation, Routledge, 2001. https://www.routledge.com/Complex-Responsive-Processes-in-Organizations-Learning-and-Knowledge-Creation/Stacey/p/book/9780415249195
- David J. Hall and Maurice A. Saias, "Strategy Follows Structure!" Strategic Management Journal 1, no. 2 (1980), pages 149 to 163. https://doi.org/10.1002/smj.4250010205
- James G. March, "Exploration and Exploitation in Organizational Learning," Organization Science 2, no. 1 (1991), pages 71 to 87. https://doi.org/10.1287/orsc.2.1.71
- Tom Burns and G. M. Stalker, The Management of Innovation, Tavistock, 1961. Revised edition, Oxford University Press, 1994.
- Charles A. O'Reilly III and Michael L. Tushman, "The Ambidextrous Organization," Harvard Business Review, April 2004, pages 74 to 81. https://hbr.org/2004/04/the-ambidextrous-organization

