The debate between shareholder primacy and stakeholder theory concerns the legal obligations of corporate directors. Introduction A corporation is never just a machine for making money. It is a legal institution, a social system, and a vehicle for allocating power, risk, and responsibility. That is why one of the most important debates in corporate governance continues to divide scholars, executives, regulators, and investors: should corporations exist primarily to maximize shareholder value, or should they balance the interests of all the people and institutions affected by their actions? This debate is commonly framed as shareholder primacy vs. stakeholder theory. Shareholder primacy says the corporation's central obligation is to its owners, the shareholders. Stakeholder theory says the corporation owes duties to a wider circle of affected parties, including employees, customers, suppliers, creditors, communities, and sometimes society at large. This is not a purely academ...
This post covers delegation and vertical coordination: how authority is passed down the hierarchy, how that authority is coordinated across levels, and why the two must be designed together. The analysis draws on paired international and emerging-market cases, including Google and Safaricom, to show how the balance is managed in practice.
By Kateule Sydney — Researcher and Writer | Last Verified: 2026-09-29 | Published by Kat-Syd Resources Hub
Delegation and vertical coordination: passing authority down and keeping the levels aligned
Table of Contents
Delegation Is the Transfer of Authority
Delegation is the process by which a manager assigns responsibility for a task and grants the authority needed to complete it. It is not the same as assigning work. Assigning work without authority produces frustration; delegating without accountability produces drift. Henri Fayol, in General and Industrial Management (19176), treated authority and responsibility as inseparable, and argued that responsibility must match authority for the structure to function.
Three elements must travel together for delegation to work:
- Responsibility — the duty to complete the task and produce the result
- Authority — the power to make the decisions and commit the resources the task requires
- Accountability — the obligation to report and answer for the outcome
Most failed delegation keeps responsibility with the subordinate, authority with the manager, and accountability vague. That combination produces managers who complain they cannot let go and subordinates who complain they cannot act.
Delegation takes four common forms, each with a different scope:
- Task delegation — specific duties handed over with clear instructions and a defined deadline
- Decision delegation — the subordinate is trusted to decide within agreed limits
- Project delegation — whole workstreams owned end to end, with resources attached
- Strategic delegation — authority over a domain, with the manager setting the frame rather than the task
The interpretive insight is that delegation is a structural decision, not a personal favour. Firms that treat it as a favour end up with authority concentrated at the top and capability concentrated nowhere.
Vertical Coordination Holds the Levels Together
Vertical coordination is the set of mechanisms that align decisions, information, and goals across the levels of a hierarchy. It exists because delegation alone produces divergence: units given authority will optimize locally unless something pulls them back to the firm’s overall direction. Jay Galbraith, in Designing Organizations, treated vertical coordination as the counterweight to decentralization, without which delegation becomes fragmentation.
Coordination relies on three structural mechanisms:
- Hierarchical reporting — the formal chain through which decisions are escalated and approved
- Rules and standards — shared procedures that remove the need for case-by-case escalation
- Planning and budgeting — the targets and resource envelopes that align units to the same priorities
Key point: delegation and coordination are two halves of one design. Authority handed down without coordination produces units pulling in different directions, and coordination without delegation produces bottlenecks at the top.
Three additional coordination devices are used as the firm grows:
- Liaison roles — individuals whose job is to connect two levels or functions
- Task forces and committees — temporary groups that resolve cross-level issues
- Integrating managers — senior roles whose authority cuts across the vertical chain
The interpretive insight is that coordination is not resistance to delegation. It is what makes delegation safe at scale, because it gives senior management a way to steer without taking authority back.
Case Study
Google and Safaricom show two very different applications of delegation paired with vertical coordination, each matched to the firm’s operating environment.
Google delegates significant decision authority to engineering teams and product groups, but it pairs that delegation with strong vertical coordination through OKRs, hiring committees, and design reviews. Authority is handed down; alignment is pulled back up through shared objectives and structured review. Safaricom operates a regulated national network where reliability, compliance, and customer impact require tight coordination across levels. Delegation is real but bounded: regional and functional leaders hold operating authority within rules, standards, and escalation paths that keep decisions consistent with national service levels and regulatory obligations.
The two cases show that delegation is not a matter of how much authority to give away. It is a matter of how much authority to give away and how to coordinate it, and the answer depends on the risk profile of the work and the speed at which decisions must be made.
Why Delegation Fails Without Coordination
Delegation fails when the authority handed down is not matched by information, incentives, or a mechanism to re-align. The failure is structural, not personal. Managers who try harder on delegation without fixing coordination get faster local decisions and slower overall execution, because the units optimize for their own metrics.
The four recurring failure patterns are:
- Authority-information gap — units can decide but lack the data to decide well
- Authority-incentive gap — units are measured on local targets that conflict with firm priorities
- Authority-capability gap — the unit lacks the skills to use the authority well
- Authority-accountability gap — no one is clearly answerable for the outcome
A fifth failure sits outside the handover itself and appears later in the delegation cycle, once the manager has stopped paying attention.
The full set of failures is:
- Re-centralization — leadership takes authority back after a visible failure, undoing the design
- Information overload — leadership demands so much reporting that the delegated speed advantage disappears
- Shadow authority — informal power centers override the formal decision rights that were delegated
Each failure is preventable through coordination design, and each is expensive to fix once it has set. The discipline is to match authority with the information, incentives, capabilities, and accountability the decision requires, and to keep matching them as conditions change.
Design Levers for Delegation and Coordination
The design levers are the specific choices that determine how much authority moves down the hierarchy and how strongly the levels are pulled back into alignment. Henry Mintzberg, in Structure in Fives, identified standardization, formalization, and liaison devices as the primary coordination mechanisms, and argued that their mix defines the organization’s structure more than its org chart does.
The levers are not interchangeable. Choosing one over the others has different costs, different speed, and different effects on managerial workload.
The three primary design levers are:
- Decision rights allocation — which decisions belong at which level, made explicit rather than left to interpretation
- Information architecture — the dashboards, reporting, and data flows that give each level what it needs to decide well
- Alignment mechanisms — the objectives, budgets, and review rhythms that keep delegated decisions pointed at the same direction
Firms that get delegation right treat it as a design question, not a management style question. They define decision rights, invest in the information flow to support them, and build alignment mechanisms that let leadership steer without reversing the delegation. That is the discipline the case evidence supports, and it is the discipline that separates firms that scale well from firms that stall.
Conclusion
The case evidence from Google and Safaricom establishes that delegation and vertical coordination are not competing choices but complementary halves of one design. Firms that delegate without coordinating get fragmentation, and firms that coordinate without delegating get bottlenecks.
My position is that delegation is a structural decision with measurable consequences. It works when responsibility, authority, and accountability travel together, and it works at scale only when coordination mechanisms are strong enough to align the units that now hold the authority.
The standard treatment of delegation undersells three things: the failure modes that appear when coordination is missing, the specific design levers that hold delegation and coordination together, and the cost of re-centralizing after a visible failure. Delegation is not a personality trait. It is a design choice, and it can be measured, tuned, and held.
My recommendations follow from that conclusion:
- Define decision rights explicitly — state which decisions belong at which level rather than leaving them to be renegotiated case by case
- Move responsibility, authority, and accountability together — do not hand over duties without the power and the reporting line that make them real
- Invest in the information flow — give each level the data required to decide well, because authority without information produces poor decisions
- Build alignment mechanisms that steer without reversing — use objectives, budgets, and review rhythms to keep delegated decisions pointed in the same direction
- Resist re-centralization after a visible failure — fix the coordination gap that caused it rather than pulling authority back up
Delegation is not a matter of how much authority to give away. It is a matter of how much to give away and how to hold the levels together once it has moved, and the firms that design both halves outperform the firms that only design one.
References
Read Also on Kat-Syd Resources Hub
Management Principles Series: Planning, Organizing, Staffing, Directing & Controlling — Foundational management functions that govern how firms plan, organise, and control.
Functional Management — The Pillars — How core business functions including HR and operations are organised and measured.
Agency and Employment Law Series — The legal foundations of employment relationships and agency.
Written by Kateule Sydney — Researcher and Writer
© 2026 Kat-Syd Resources Hub. All rights reserved.
Kat-Syd Resources Hub — Educational case studies and analytical reference