- Get link
- X
- Other Apps
Organizational Design Principles and Contingency Factors
How structure follows strategy, technology, size, and environment — and why there is no one best way to organise
Last Verified: 2026-09-16 | Author: Kateule Sydney | Published by Kat-Syd Resources Hub
Organisational design matches structure to the internal and external factors that determine how work can be coordinated.
Summary: Organisational design is the process by which a firm matches its structure to its strategy, technology, size, and environment. The contingency approach holds that there is no single best way to organise — the correct structure depends on the factors the organisation faces. This post examines the classical design principles, the contingency factors that modify them, and the recurring choices that any organisation must make. 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 Structure-Strategy Question
In 1962, the American business historian Alfred Chandler published Strategy and Structure, a study of four large American corporations — DuPont, General Motors, Standard Oil of New Jersey, and Sears — and their organisational transformations between 1920 and 1960. Chandler’s central finding was that each company changed its structure only after a change in strategy had created coordination problems that the old structure could not solve. DuPont moved from a functional structure to a divisional one when its diversification into multiple product lines made central coordination impossible. General Motors did the same under Alfred Sloan. The pattern was consistent: structure followed strategy, and it followed late — only after the mismatch had become visible in operational results.
Organisational design is defined by Richard Daft in Organization Theory and Design as “the process of constructing and adjusting an organisation’s structure to achieve its goals.” The definition contains two components that are frequently collapsed into one: construction (designing a structure for a new organisation or a new strategy) and adjustment (modifying an existing structure as conditions change). Most organisations spend their time on adjustment, because most organisational design problems appear as mismatches between what the structure supports and what the strategy requires.
This post examines four interlocking components of organisational design:
- Classical design principles — the rules of division of labour, unity of command, and scalar chain
- Structural archetypes — the functional, divisional, and matrix forms and their trade-offs
- Contingency factors — technology, size, and environment as determinants of structure
- Mechanistic and organic structures — the two endpoints on the spectrum of organisational form
The analysis draws on two academic traditions. The first is the classical tradition established by Fayol, Urwick, and Gulick, which treats organisational design as the application of universal principles. The second is the contingency tradition associated with Joan Woodward, Paul Lawrence, Jay Lorsch, and Tom Burns and G.M. Stalker, which holds that there is no universal principle and that structure must be matched to the specific context the organisation faces. Where the two traditions conflict, the cases in this post favour the contingency reading.
Chapter 1 — Classical Design Principles: Division of Labour and Unity of Command
Definition. The classical design principles are defined by Henri Fayol in General and Industrial Management (1916) and elaborated by Lyndall Urwick in The Elements of Administration (1943). The four foundational principles are:
- Division of labour — work is broken into specialised tasks to increase efficiency through repetition
- Unity of command — each employee reports to only one supervisor, avoiding conflicting instructions
- Scalar chain — an unbroken line of authority from the top of the organisation to the bottom
- Span of control — the number of subordinates a manager can effectively supervise
Explanation. The classical principles were treated as universal rules for most of the twentieth century. Subsequent research has shown that they apply conditionally rather than absolutely:
- Division of labour — increases efficiency to a point, beyond which specialisation produces boredom and coordination costs
- Unity of command — provides clarity but fails when a single task requires expertise from more than one function, as in matrix structures
- Scalar chain — enables accountability but slows information flow in large organisations
- Span of control — depends on task complexity; 5–9 direct reports is manageable for complex work, but 20–30 is workable for standardised work
The interpretive insight is that the classical principles are not wrong; they are incomplete. They describe the design logic that works under conditions of stability and predictability. When conditions are volatile, or when the work requires integration across functions, the same principles produce rigid structures that cannot respond.
The Five Core Elements. Classical design must address five questions in a fixed order. Together they form the operational logic of the discipline.
- Why it is done that way — because large-scale coordination requires clear lines of authority, defined roles, and limits on the number of relationships any one manager must maintain
- What is supposed to be done — divide work into specialised roles, establish unambiguous reporting relationships, and define the chain of command
- When it is done — at organisational founding; reviewed on restructuring; adjusted incrementally as the organisation grows and roles evolve
- Who does what — senior leadership sets overall design; HR supports with job architecture; line managers implement within their spans; employees operate within defined roles
- How it is supposed to be done — through documented organisation charts, job descriptions, and reporting relationships; not through informal understanding
Case study. The Boeing 737 MAX production system provides a case in point. Boeing’s design of its 737 assembly line followed classical principles: highly specialised work stations, clear reporting lines, and a single chain of command from the production floor to the programme director. In a stable environment, the structure produced among the fastest narrow-body aircraft assembly rates in the industry. When Boeing attempted to increase production from 42 to 57 aircraft per month in 2018–2019 without reconfiguring the structure, the assembly system could not support the increased rate. Work was standardised for the original rate, and the specialisation that had been designed for 42 units per month did not scale. The company subsequently slowed production and accepted delivery delays. By contrast, the Indian software services firm Wipro provides an illustration of the limits of classical design in knowledge work. Wipro’s traditional pyramid structure — many junior engineers supervised by few senior ones — worked well for standardised application development. When the firm attempted to shift into higher-value consulting and digital transformation work in the 2010s, the pyramid could not accommodate the cross-functional teams the new work required, and Wipro rebuilt parts of the organisation around matrix structures and cross-functional squads.
Blog Analysis — Pros and Cons. The evidence from Boeing and Wipro supports the following assessment.
- Pros: Classical principles produce clear accountability, predictable coordination, and efficient standardisation when the work is stable and the environment is predictable. Boeing’s assembly system at the original rate, and Wipro’s pyramid for application development, are both cases where classical design produced world-class results.
- Cons: Classical principles break down when conditions change. Boeing’s specialisation did not scale to higher production rates; Wipro’s pyramid could not support cross-functional consulting work. The failure mode is not the principles themselves but their application beyond the conditions for which they were designed.
Chapter 2 — Structural Archetypes: Functional, Divisional, and Matrix
Definition. Structural archetypes are defined by Richard Daft in Organization Theory and Design as “the recurring patterns of structure that organisations adopt to coordinate their activities.” Three archetypes dominate the literature:
- Functional structure — grouping by expertise (marketing, finance, operations) with a single chain of command
- Divisional structure — grouping by product, geography, or customer with each division having its own functional resources
- Matrix structure — dual reporting lines in which employees report both to a functional manager and to a project or product manager
Explanation. Each archetype solves a different coordination problem and creates a different failure mode:
- Functional — solves the problem of scale in a single business; fails when the organisation diversifies and each business needs different functional priorities
- Divisional — solves the problem of focus in a diversified business; fails when divisions duplicate resources and lose scale economies
- Matrix — solves the problem of competing priorities across two dimensions; fails when employees face conflicting directives with no clear resolution mechanism
The interpretive insight is that structural archetypes are not better or worse in the abstract. They are matched or mismatched to the coordination problem the organisation faces. Most large firms operate hybrid structures in which different business units use different archetypes simultaneously.
The Five Core Elements.
- Why it is done that way — because different strategies require different coordination priorities; the structure is chosen to support the strategy the firm is pursuing
- What is supposed to be done — select the archetype that best matches the organisation’s scope (single business or diversified), scale (small or large), and integration needs (simple or complex)
- When it is done — at organisational founding; at major diversification or refocusing; when the current structure demonstrably fails to support the current strategy
- Who does what — senior leadership selects the archetype; HR designs the roles and reporting relationships; line managers operate within the structure; support functions align their systems to the chosen form
- How it is supposed to be done — through deliberate design rather than accretion; through clear definition of reporting relationships and decision rights; through systems that match the structure
Case study. General Electric’s 2018 breakup of its legacy structure provides a case in point for the divisional archetype. GE operated for most of the twentieth century as a multidivisional conglomerate — power, aviation, healthcare, and finance each running as largely independent divisions with their own P&Ls. The structure worked when capital was cheap, growth was steady, and the company’s scale provided a financing advantage. Under pressure from activist investors and deteriorating financial performance, GE began dismantling the structure in 2018, eventually splitting into three independent companies (GE Aerospace, GE Vernova, and GE HealthCare) by 2024. The rationale was that the divisional archetype had become a source of cost rather than value. By contrast, the Indian IT services firm Infosys operates a hybrid structure that combines functional centres of excellence (for emerging technologies) with industry-focused business units (for banking, healthcare, retail). The structure allows Infosys to maintain deep technology expertise across the firm while competing in industries that require specialised knowledge. A 2023 study of Indian IT services firms found that this hybrid design correlated with higher revenue per employee than either pure functional or pure divisional structures.
Blog Analysis — Pros and Cons. The evidence from GE and Infosys supports the following assessment.
- Pros: Different structural archetypes solve different problems. GE’s divisional structure supported a strategy of running unrelated businesses at scale. Infosys’s hybrid structure supports a strategy of deep technology expertise delivered across industries. Both structures are internally coherent.
- Cons: Each archetype also has a predictable failure mode. GE’s divisional structure became a cost centre when market conditions changed, and the company dismantled it. Infosys’s hybrid structure requires continuous coordination between two dimensions and can produce conflicting priorities. Neither structure is permanent; both require adjustment as strategy evolves.
Chapter 3 — Contingency Factors: Technology, Size, and Environment
Definition. Contingency factors are defined by Joan Woodward in Industrial Organization: Theory and Practice (1965) as “the contextual variables that determine which organisational structure will be effective.” Woodward’s research on British manufacturing firms showed that the effectiveness of a given structure depended on the technology the firm used, not on the structure itself. The finding challenged the classical assumption that there was a single best way to organise.
Explanation. Three contingency factors have the strongest empirical support:
- Technology — unit and small-batch production favour organic structures; mass and large-batch production favour mechanistic structures; continuous-process production favour organic structures
- Size — larger organisations require more formalisation and greater hierarchy; the effect is consistent but diminishing above a certain scale
- Environment — stable environments favour mechanistic structures; volatile environments favour organic structures
The interpretive insight is that the correct structure is determined jointly by the three factors, and no single factor produces a complete answer. A large firm in a stable environment producing mass-market goods will need a mechanistic structure. A small firm in a volatile environment producing customised services will need an organic structure. Firms that fall between the extremes face design trade-offs that cannot be resolved by choosing one archetype over another.
The Five Core Elements.
- Why it is done that way — because the structure that works for one technology, size, or environment does not work for another; matching structure to context is the condition for effectiveness
- What is supposed to be done — assess the organisation’s technology, size, and environment; select a structure that matches the combination; adjust as any factor changes
- When it is done — at founding; on major technological change; on significant growth or contraction; on major environmental shift (new regulation, new competition)
- Who does what — senior leadership assesses contingency factors; HR and strategy functions propose structural adjustments; line managers provide input on operational requirements
- How it is supposed to be done — through systematic assessment of technology, size, and environment against structural options; not through adopting a fashionable structure regardless of context
Case study. Zara’s production system provides a case in point for the technology factor. Zara uses a partially automated cutting and finishing operation combined with manual sewing carried out by a network of subcontractors in Galicia, Spain. The technology is closer to small-batch production than to mass production, and Zara’s structure reflects this: decision-making authority is distributed to store managers who report demand signals twice weekly, and production decisions are made at the distribution centre level rather than at the corporate level. The result is a two-week cycle from design to shelf, compared with the industry average of six months. By contrast, Foxconn’s manufacturing operations provide a case for mass production technology. Foxconn’s assembly lines are highly automated, with standardised work procedures and clear chains of command. The structure is deliberately mechanistic because the technology is mass-production, and mechanistic structure matches it. The two companies could not adopt each other’s structures without losing the coordination advantages that each derives from its own.
Blog Analysis — Pros and Cons. The evidence from Zara and Foxconn supports the following assessment.
- Pros: The contingency approach gives managers a principled basis for choosing structure. Zara’s organic structure fits its small-batch technology and fast-cycle strategy; Foxconn’s mechanistic structure fits its mass-production technology and scale. Both structures produce competitive advantage in their respective contexts.
- Cons: The contingency approach is difficult to apply when the organisation operates in multiple contexts simultaneously. A firm producing mass-market goods in one market and customised goods in another cannot adopt a single structure that matches both. The failure mode is attempting to apply a single structural solution to an organisation that faces multiple contingent contexts.
Chapter 4 — Mechanistic and Organic Structures
Definition. Mechanistic and organic structures are defined by Tom Burns and G.M. Stalker in The Management of Innovation (1961) as two endpoints on a spectrum of organisational form. A mechanistic structure is characterised by “highly defined tasks, vertical communication, and centralised decision-making.” An organic structure is characterised by “adjusting and continually redefined tasks, lateral communication, and decentralised decision-making.”
Explanation. The two forms differ across six dimensions:
- Task definition — mechanistic: highly specialised and fixed; organic: broad and continually redefined
- Communication — mechanistic: vertical, following the chain of command; organic: lateral, following the information flow
- Decision-making — mechanistic: centralised at the top; organic: distributed to the point of information
- Authority — mechanistic: tied to position; organic: tied to expertise
- Rules — mechanistic: extensive and formalised; organic: minimal and informal
- Adaptation — mechanistic: slow, requires top-down change; organic: fast, happens through ongoing adjustment
The interpretive insight is that neither form is superior. Mechanistic structures produce efficiency and consistency. Organic structures produce flexibility and innovation. The correct form depends on whether the organisation’s primary challenge is execution or adaptation.
The Five Core Elements.
- Why it is done that way — because different challenges require different organisational forms; mechanistic structures maximise execution, and organic structures maximise adaptation
- What is supposed to be done — select the form that matches the organisation’s primary challenge; recognise that most organisations combine elements of both
- When it is done — at founding; on shift in the organisation’s dominant challenge (from scale to innovation, or vice versa); on major environmental change
- Who does what — senior leadership sets the design intent; HR designs systems that support the chosen form; line managers operate within the form; the workforce adapts to the expectations it sets
- How it is supposed to be done — through deliberate matching of structure to the organisation’s dominant challenge; not through partial adoption that produces the worst of both forms
Case study. The contrast between Tesla and Toyota illustrates the difference between the two forms in the same industry. Tesla operates with a strongly organic structure in its engineering and design functions: task definitions are fluid, decisions are distributed to engineering leads, communication is lateral, and the CEO intervenes directly in technical decisions. This organic structure supported Tesla’s rapid iteration during the Model 3 launch and its ability to redesign software and hardware systems over the air. By contrast, Toyota’s production system is the archetype of mechanistic design: standardised work procedures, clear chains of command, defined escalation paths, and rules that govern every significant operation. The mechanistic structure supports Toyota’s core objective of defect-free mass production at scale. Neither structure would work for the other company. Tesla cannot achieve Toyota’s production consistency with an organic structure; Toyota cannot achieve Tesla’s design velocity with a mechanistic one.
Blog Analysis — Pros and Cons. The evidence from Tesla and Toyota supports the following assessment.
- Pros: The mechanistic-organic spectrum gives managers a principled framework for matching structure to challenge. Tesla’s organic structure supports design velocity; Toyota’s mechanistic structure supports production consistency. Both structures produce competitive advantage in their respective domains.
- Cons: Both forms carry predictable failure modes. Organic structures struggle with scale and can produce coordination chaos as the organisation grows. Mechanistic structures struggle with change and can produce rigidity when the environment shifts. Most firms need both forms simultaneously in different parts of the organisation, and managing that coexistence is one of the most difficult challenges in organisational design.
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