- Get link
- X
- Other Apps
Delegation and Vertical Coordination
How authority moves down an organisation, and how vertical coordination holds that movement together
Last Verified: 2026-09-16 | Author: Kateule Sydney | Published by Kat-Syd Resources Hub
Delegation and vertical coordination determine how authority, information, and accountability flow through an organisation.
Summary: Delegation and vertical coordination are the two mechanisms by which authority and information move through an organisational hierarchy. This post examines what delegation is, how vertical coordination differs from horizontal coordination, why organisations oscillate between centralisation and decentralisation, and what the historical record shows about the trade-offs. 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 Coordination Problem
In 2015, the Chinese technology conglomerate Alibaba reorganised its business into a structure of semi-autonomous business units, each with its own CEO, its own P&L, and its own operational decisions. Founder Jack Ma framed the change as a response to scale: the company had grown to over 30,000 employees across multiple business lines, and central coordination from Hangzhou had become a bottleneck. Five years later, in 2020, the company reversed part of that decentralisation, pulling certain functions back to the group level to coordinate responses to regulatory changes. The oscillation was not a failure of management. It was a demonstration of the fundamental trade-off that delegation and vertical coordination exist to manage.
Delegation is defined by Henri Fayol in General and Industrial Management as “the act of entrusting a subordinate with authority and responsibility for the performance of a defined task.” Vertical coordination is defined by Harold Koontz and Heinz Weihrich in Essentials of Management as “the process of integrating the activities of different levels of the organisational hierarchy toward common objectives.” The two are not opposites. Delegation moves authority down. Vertical coordination ensures the outcomes of that movement remain aligned with organisational purpose.
This post examines four interlocking components of delegation and vertical coordination:
- What delegation is — and how it differs from abdication, assignment, and merely transferring work
- Vertical coordination — the mechanisms through which hierarchical alignment is maintained
- Centralisation and decentralisation — the recurring oscillation and what drives it
- Authority, span of control, and chain of command — the structural constraints that shape delegation
The analysis draws on two academic traditions. The first is the classical management tradition established by Fayol and refined by Koontz and O’Donnell, which treats delegation as a structural mechanism for making large organisations governable. The second is the information-processing tradition associated with Jay Galbraith and Herbert Simon, which examines why organisations centralise or decentralise depending on the kind of coordination problem they face. Where the two traditions conflict, the cases in this post favour the information-processing reading.
Chapter 1 — Delegation: What It Is and What It Is Not
Definition. Delegation is defined by Henri Fayol in General and Industrial Management as “the act of entrusting a subordinate with authority and responsibility for the performance approvals of a defined task.” The definition contains three elements that distinguish delegation from adjacent management practices:
- Authority — the subordinate is given the power to make decisions within a defined scope
- Responsibility — the subordinate is accountable for the outcome of those decisions
- Defined scope — delegation is bounded; it does not transfer every authority of the delegating manager
Explanation. Delegation is frequently confused with three adjacent practices. The distinction matters because each produces a different result. A manager who thinks they are delegating but is actually doing one of the other three will not achieve the outcomes that delegation is meant to produce.
- Assignment — transferring a task without transferring authority; the subordinate executes but does not decide
- Abdication — transferring both authority and accountability without retaining oversight; the manager has withdrawn rather than delegated
- Consultation — seeking input while retaining both authority and accountability; the manager has informed themselves but not transferred anything
- Delegation — transferring defined authority and responsibility while retaining accountability for the overall outcome
The interpretive insight is that delegation is not the same as giving work away. A manager who delegates remains accountable to their own superior for the result. This is why delegation, properly understood, is a discipline rather than a relief.
The Five Core Elements. Delegation must address five questions in a fixed order. Together they form the operational logic of the discipline.
- Why it is done that way — because no single manager can make every decision within their span; delegation extends decision-making capacity to where the necessary information is
- What is supposed to be done — transfer defined authority and responsibility for a specific task or function to a subordinate who has the capability and the information to decide
- When it is done — when the volume or complexity of decisions exceeds what the manager can handle; when the subordinate has both capability and the information to decide
- Who does what — the delegating manager defines scope, provides resources, and reviews outcomes; the subordinate decides, executes, and reports
- How it is supposed to be done — through clear specification of authority and limits, resource support, and periodic review; not through vague assignments or silent withdrawal
Case study. Netflix’s “Freedom and Responsibility” culture document, published in 2009 and updated several times since, describes one of the most explicit delegation frameworks in modern corporate practice. The company abolished formal vacation policies, travel approval processes, and expense reporting in favour of a single guiding principle: act in Netflix’s best interest. Employees were given decision authority on the assumption that they could be trusted to use it well, with the company accepting that a small number of poor decisions would cost less than the overhead. By contrast, the now-defunct American retailer Sears provides an illustration of delegation failure. In the 2000s, under CEO Eddie Lampert, Sears centralised decision authority into a small group of executives while simultaneously delegating operational responsibility to store managers without the corresponding authority over inventory, staffing, or pricing. Managers were accountable for store performance but had no control over the variables that determined it. Sales and customer satisfaction declined, and the company filed for bankruptcy in 2018.
Blog Analysis — Pros and Cons. The evidence from Netflix and Sears supports the following assessment.
- Pros: When delegation is done with clear scope, resource support, and a culture that accepts occasional failure as the cost of decision speed (Netflix), it extends the decision-making capacity of the organisation and increases commitment. Employees given genuine authority behave more like owners.
- Cons: When delegation is done without authority (Sears), it becomes responsibility without power. Managers are held accountable for outcomes they cannot influence, which produces either learned helplessness or the quiet departure of capable employees. The failure mode is not delegation itself but delegation without the corresponding transfer of authority and resources.
Chapter 2 — Vertical Coordination: Mechanisms and Trade-offs
Definition. Vertical coordination is defined by Harold Koontz and Heinz Weihrich in Essentials of Management as “the process of integrating the activities of different levels of the organisational hierarchy toward common objectives.” The definition identifies the specific purpose of vertical coordination: it is not the flow of commands downward, but the integration of activity across levels. Vertical coordination makes hierarchy function as a system rather than a sequence of separate layers.
Explanation. Vertical coordination operates through four mechanisms, each of which has different costs and different effects:
- Formal authority — hierarchy of reporting relationships; low-cost but slow when decisions require escalation
- Rules and procedures — standardised responses to recurring situations; fast but rigid when situations change
- Planning and goal-setting — cascade of objectives from the top; aligns direction but can produce goal decay at lower levels
- Information systems — data flowing upward and dashboard reporting downward; gives senior leadership visibility but can overwhelm with volume
The interpretive insight is that no single mechanism is sufficient. Organisations that rely only on formal authority produce slow decisions. Organisations that rely only on rules produce rigidity. Organisations that rely only on planning produce goal decay. Organisations that rely only on information systems produce dashboards without accountability. Vertical coordination succeeds when multiple mechanisms are layered.
The Five Core Elements.
- Why it is done that way — because delegation without coordination produces divergence; each unit optimises for its own objectives rather than the organisation’s
- What is supposed to be done — integrate the decisions and activities of different hierarchical levels toward common objectives
- When it is done — continuously through rules and systems; periodically through planning cycles and review meetings; on trigger events through escalation
- Who does what — senior leadership sets direction and reviews; middle management translates and aligns; frontline executes and reports; support functions maintain systems and rules
- How it is supposed to be done — through layered mechanisms: authority, rules, planning, and information systems working together rather than any one alone
Case study. Toyota’s production system provides one of the most studied examples of layered vertical coordination. The company coordinates across levels through three mechanisms simultaneously: standardised work procedures at the operational level, andon cord escalation when a worker identifies a defect, and daily production review meetings at the plant level. Frontline workers have the authority to stop the line; supervisors are required to resolve the issue within a fixed time or escalate; plant management reviews every line stop daily. The result is a system in which vertical coordination is not a hierarchy of command but a set of layered loops operating at different speeds. By contrast, the collapse of the American energy company Enron in 2001 illustrates what happens when vertical coordination mechanisms fail. Enron’s formal authority structure vested enormous decision authority in a small group of senior executives. Rules and procedures were deliberately thin, planning processes were short-term and incentive-driven, and information systems were controlled by the same executives who made the decisions. When the underlying financial engineering failed, no coordination mechanism existed to surface the problem upward or apply correction downward.
Blog Analysis — Pros and Cons. The evidence from Toyota and Enron supports the following assessment.
- Pros: Layered vertical coordination (Toyota) allows an organisation to combine speed at the operational level with alignment at the strategic level. Frontline decisions can be made quickly without losing the ability to surface patterns upward when they matter.
- Cons: When vertical coordination collapses into a single mechanism (Enron’s concentration of authority, information, and decision-making in the same small group), the organisation loses the ability to detect and correct its own errors. The failure mode is not hierarchy itself but the absence of layered coordination within the hierarchy.
Chapter 3 — Centralisation and Decentralisation in Practice
Definition. Centralisation is defined by Harold Koontz in Management as “the tendency to concentrate decision-making authority at the upper levels of the organisation.” Decentralisation is defined by the same source as “the tendency to disperse decision-making authority throughout the organisation.” The two are not opposed positions but points on a spectrum. Every organisation is at some point on that spectrum at any given time, and most large organisations are at different points for different decisions.
Explanation. The oscillation between centralisation and decentralisation is a recurring pattern in organisational history. Three forces drive the oscillation:
- Scale — growing organisations decentralise to maintain decision speed and local responsiveness
- Coordination failure — decentralised organisations that lose alignment re-centralise to regain coherence
- Environment — stable environments favour centralisation for efficiency; volatile environments favour decentralisation for adaptability
The interpretive insight is that the centralisation-decentralisation question is not answerable in the abstract. The correct answer depends on the kind of coordination problem the organisation faces, which varies by function, by market, and by period. Organisations that treat centralisation or decentralisation as a permanent principle rather than a contingent choice consistently make errors of one kind or the other.
The Five Core Elements.
- Why it is done that way — because different decisions require different proximity to information; some decisions are best made centrally, others are best made locally
- What is supposed to be done — allocate decision rights to the level where the relevant information and the appropriate accountability come together
- When it is done — reviewed continuously as the organisation grows, enters new markets, or faces new regulatory environments; formally re-examined on major restructuring
- Who does what — senior leadership sets the overall allocation of decision rights; function heads and unit leaders propose adjustments; support functions implement the resulting systems
- How it is supposed to be done — through decisions on the decision-rights question rather than principles of the form “we centralise” or “we decentralise”
Case study. Apple’s organisational structure is one of the most studied cases of sustained centralisation in a large company. The company is organised functionally rather than by business unit, meaning that a single engineering function oversees both the iPhone and the Mac, a single design team oversees all product development, and a single marketing function oversees all geographies. Steve Jobs’ stated rationale was that functional centralisation kept product coherence at a time when competitors were fragmenting into incompatible lines. The structure has been maintained under Tim Cook, and Apple continued to report the highest operating margins in the consumer electronics industry through 2024. By contrast, Alphabet’s structure is the clearest recent example of sustained decentralisation at scale. Under the Alphabet restructuring of 2015, the company separated Google from other businesses such as Waymo, Verily, and DeepMind, each operating with its own CEO, board, and decision rights. The structure allowed each subsidiary to pursue long-horizon strategies in different industries without competing for the same internal resources.
Blog Analysis — Pros and Cons. The evidence from Apple and Alphabet supports the following assessment.
- Pros: Both highly centralised (Apple) and highly decentralised (Alphabet) organisations can succeed at scale when the structure matches the strategy. Apple’s centralisation supports a strategy of tightly integrated products; Alphabet’s decentralisation supports a strategy of independent bets in unrelated industries.
- Cons: Both structures carry predictable costs. Centralisation (Apple) slows response to local market conditions and concentrates risk in a small group of senior decision-makers. Decentralisation (Alphabet) requires enormous investment in coordination mechanisms and creates political pressure when subsidiaries compete for attention and capital. Neither structure is universally correct, and both have required periodic adjustment.
Chapter 4 — Authority, Span of Control, and Chain of Command
Definition. Authority is defined by Chester Barnard in The Functions of the Executive as “the character of a communication in a formal organisation by virtue of which it is accepted by a contributor to the organisation as governing the action he contributes.” The definition is deliberately permissive rather than coercive. Authority in Barnard’s sense exists only when the subordinate accepts it; a command that is not accepted is not authoritative, regardless of the position of the person issuing it. Span of control is defined by Lyndall Urwick as the number of subordinates a single manager can effectively supervise. Chain of command is defined by the same source as the unbroken line of authority from the highest executive to the lowest subordinate.
Explanation. The three structural constraints on delegation operate together, and each limits the others:
- Authority — the acceptance-based right to decide; cannot be exercised beyond the scope in which it is accepted
- Span of control — the number of direct reports a manager can supervise effectively; typically 5–9 for complex work, higher for standardised work
- Chain of command — the unbroken line of authority; enables accountability but slows the flow of information across levels
The interpretive insight is that the structural constraints are not administrative rules but consequences of human cognitive limits. Span of control exists because a manager cannot supervise an unlimited number of people. Chain of command exists because accountability requires a defined line of answerability. Authority is limited by acceptance because a command is only effective if the recipient is willing to comply.
The Five Core Elements.
- Why it is done that way — because organisations require clear lines of accountability and cannot function if every decision must be made at the top; the constraints make delegation governable
- What is supposed to be done — define authority scopes clearly, keep spans of control within supervisory capacity, and maintain unbroken chains of command for accountability
- When it is done — at organisational design; reviewed on restructuring; adjusted as organisational scale and complexity change
- Who does what — senior leadership sets structural design; HR supports with job architecture; managers operate within defined spans and chains; employees accept or do not accept authority in practice
- How it is supposed to be done — through documented organisational structures, job descriptions, and defined decision rights rather than reliance on informal understanding
Case study. The Indian conglomerate Tata Group provides a case in point for the deliberate management of span of control and chain of command. Tata operates over 100 companies across multiple industries, with a central holding company (Tata Sons) that sets strategic direction and a small number of shared services. Individual company CEOs have authority over their own operations, but capital allocation, major acquisitions, and brand management are governed through the holding company. The structure allows Tata to maintain consistency across a portfolio of unrelated businesses while preserving operational autonomy at the company level. By contrast, the 2018 implosion of the British construction and facilities management company Carillion illustrates the failure that occurs when chain of command and span of control are mismanaged. Carillion grew through acquisition to operate in the UK, Canada, the Middle East, and the Caribbean, with a sprawling structure of joint ventures and subcontracts. By the time of its collapse, the company had over 450 subsidiary and joint-venture entities, with unclear lines of accountability and frequent gaps between decision authority and operational responsibility. The UK parliamentary inquiry into the collapse identified the absence of a clear chain of command as one of the primary causes.
Blog Analysis — Pros and Cons. The evidence from Tata Group and Carillion supports the following assessment.
- Pros: When span of control and chain of command are deliberately managed (Tata), an organisation can operate at scale across diverse activities without losing accountability. Clear structural constraints make delegation governable.
- Cons: When the constraints are neglected (Carillion’s 450+ entities with unclear accountability), the organisation loses the ability to coordinate effectively. The failure mode is not hierarchy itself but the absence of clearly defined authority, span, and chain of command. Documentation that exists is not the same as coordination that works.
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