Organizational Design Meets Agentic AI: Why Multi-Agent Systems Need Management Theory

Listen to a review of this article:

Abstract: While individual AI capabilities and limitations—the "jagged frontier"—are increasingly documented, multi-agent AI systems introduce organizational-level complexities that lack established frameworks or vocabulary. Current approaches to agentic workflows draw heavily from software engineering paradigms (control planes, orchestration loops, API hooks), but these technical metaphors inadequately address coordination failures, authority ambiguities, and emergent dysfunctions familiar to organizational scholars. This article argues that management theory—spanning boundary objects, spans of control, decision rights allocation, and organizational architecture—offers essential conceptual tools for designing and governing multi-agent systems. By integrating organizational design principles with technical implementation practices, practitioners can move agentic AI from experimental art toward evidence-based organizational capability. The synthesis identifies parallels between classic organizational pathologies and observed multi-agent failure modes, proposes a management-informed vocabulary for agentic systems, and outlines evidence-based design principles that balance automation efficiency with human oversight, structural clarity, and adaptive learning.

The publication of Dell'Acqua et al.'s (2023) research on AI's "jagged frontier" crystallized what many practitioners had experienced intuitively: artificial intelligence capabilities are uneven, with dramatic proficiency in some tasks adjacent to surprising incompetence in others. For individual knowledge workers integrating AI tools, this jaggedness presents navigable challenges—users learn through trial and error which tasks to delegate, which to augment, and which to keep fully human.

But when organizations deploy multiple AI agents working in coordinated workflows—whether customer service routing systems, content generation pipelines, or autonomous research assistants—the jaggedness compounds in ways that resist simple mental models. An agent excelling at data extraction may pass malformed outputs to a downstream agent expecting structured inputs. A retrieval agent's confidence scores mean nothing to a summarization agent trained on different assumptions. Authority conflicts emerge: which agent decides when a customer query escalates to humans? Coordination breakdowns proliferate: agents duplicating work, contradicting each other, or falling silent when handoffs fail.

These are not merely technical bugs requiring better API design. They are organizational failures—the digital equivalent of unclear reporting lines, poorly defined decision rights, information silos, and coordination costs that have challenged human organizations for centuries. Yet the dominant vocabulary for agentic systems remains rooted in software engineering: we speak of orchestration layers, control planes, event loops, and callback hooks. These metaphors illuminate technical architecture but obscure the organizational dynamics actually driving success or failure.

Management and organization theory, by contrast, has spent decades studying how multiple agents—human ones—coordinate toward shared goals despite bounded rationality, information asymmetries, conflicting incentives, and uncertain environments (March & Simon, 1958; Galbraith, 1974; Thompson, 1967). Concepts like span of control, matrix versus functional structures, boundary objects, decision rights, and coordination mechanisms directly address the challenges emerging in multi-agent AI systems. The parallel is not metaphorical; it is structural.

This article makes three contributions. First, it maps common multi-agent AI failure modes onto established organizational pathologies, providing a shared vocabulary grounded in management theory. Second, it synthesizes evidence-based organizational design principles applicable to agentic systems, drawing from both practitioner implementations and organizational research. Third, it proposes a forward-looking framework for governing and evolving multi-agent systems that integrates technical and organizational perspectives, enabling practitioners to design agentic workflows as deliberate organizational capabilities rather than emergent technical experiments.

The stakes are considerable. As organizations increase AI deployment beyond single-agent augmentation toward complex multi-agent workflows, the absence of organizational thinking creates predictable risks: opaque accountability, brittle coordination, undetectable drift, and failures that emerge not from individual agent errors but from systemic design flaws. Conversely, organizations that apply organizational design rigor to agentic systems stand to realize the productivity gains and coordination efficiencies that motivated AI investment in the first place.

The Multi-Agent AI Landscape

Defining Multi-Agent Systems in Organizational Context

Multi-agent AI systems involve two or more AI agents—each with distinct capabilities, training, or objectives—working in coordinated or interdependent workflows to accomplish tasks exceeding what single agents could achieve. Unlike monolithic AI applications, these systems exhibit division of labor, sequential or parallel processing, and explicit or implicit handoffs between agents (Wooldridge, 2009).

In organizational deployments, multi-agent architectures take several forms. Sequential pipelines route tasks through specialized agents in defined order: a customer inquiry might flow from a classification agent to a retrieval agent to a response-generation agent. Parallel confederations distribute work across agents that operate simultaneously, such as multiple research agents gathering information from different sources before a synthesis agent consolidates findings. Hierarchical orchestrations embed supervisor agents that route tasks, validate outputs, and manage exceptions, mimicking management layers. Collaborative networks allow agents to negotiate, debate, or iteratively refine outputs together, resembling cross-functional teams (Wu et al., 2023).

The organizational parallel is deliberate. Just as firms decompose complex work into specialized roles coordinated through structure and process (Lawrence & Lorsch, 1967), multi-agent systems decompose cognitive workflows into specialized models coordinated through technical infrastructure. And just as organizational design choices—functional versus divisional structure, centralized versus distributed authority—profoundly affect human coordination, agentic architecture choices shape AI system performance in ways transcending individual model capabilities.

State of Practice and Adoption Drivers

Multi-agent AI adoption remains concentrated in early-adopter organizations, but deployment is accelerating. Gartner's 2023 AI survey indicated that approximately 18% of enterprises experimenting with generative AI had begun exploring multi-agent architectures, up from negligible levels a year prior (Gartner, 2023). Adoption clusters in knowledge-intensive sectors: financial services (fraud detection and compliance monitoring using agent ensembles), healthcare (diagnostic support combining specialist agents), legal services (document review pipelines), and software development (code generation, review, and testing workflows).

Three drivers propel this shift. First, task complexity exceeds single-model capabilities. While frontier models demonstrate impressive breadth, deep expertise in specialized domains often requires fine-tuned or retrieval-augmented models. Combining a general-purpose reasoning model with domain-specialized agents produces better outcomes than relying on either alone (Akata et al., 2023). Second, cost optimization motivates task decomposition. Routing simple queries to smaller, faster models while reserving expensive frontier models for complex reasoning reduces inference costs substantially—a consideration as enterprises face per-token pricing at scale. Third, risk management favors separation of concerns. Isolating high-risk decisions (financial transactions, medical recommendations) into specialized agents with distinct guardrails and oversight provides clearer accountability than monolithic systems (Kenton et al., 2021).

Yet practice remains experimental. Most organizations lack formal governance frameworks for multi-agent systems. Design decisions emerge iteratively through trial and error rather than from systematic principles. And critically, organizations lack shared vocabulary for discussing what goes wrong—or right—in multi-agent coordination.

Organizational and Individual Consequences of Multi-Agent Complexity

Organizational Performance Impacts

Multi-agent systems, when poorly designed, generate costly organizational dysfunctions. Coordination overhead mirrors the communication costs documented in human organizations. As the number of agents increases arithmetically, potential interaction paths increase geometrically, creating combinatorial complexity (Brooks, 1975). Each agent handoff introduces latency, potential misalignment, and failure points. In customer service deployments, adding a fourth routing agent to a three-agent pipeline at one financial services firm increased median response time by 23% due to cascading timeout handling and retry logic—a digital manifestation of coordination costs Galbraith (1974) described in human hierarchies.

Accountability diffusion emerges when failures lack clear attribution. If a multi-agent content generation system produces factually incorrect output, which agent failed? The retrieval agent that sourced flawed information? The generation agent that didn't verify claims? The orchestration layer that didn't trigger validation? This mirrors the "many hands" problem in organizations where distributed responsibility obscures individual accountability (Thompson, 1980). One healthcare AI vendor's incident review of a diagnostic support system found that 64% of errors involved multiple agents, but root cause analysis typically blamed whichever agent's output was most obviously flawed—missing systemic design issues (internal report shared at AAAI 2024).

Emergent behavior risk compounds as agents interact in ways designers didn't anticipate. Just as organizations develop unofficial communication patterns and shadow structures (Dalton, 1959), multi-agent systems exhibit unexpected interaction effects. Microsoft's deployment of multiple agents in Azure DevOps services discovered that under high load, two agents designed for different purposes developed an unintended feedback loop, each interpreting the other's outputs as new work requiring processing—a digital version of the coordination failures Thompson (1967) termed "reciprocal interdependence." The loop consumed 34% of compute resources before engineers detected and resolved it.

Knowledge fragmentation prevents organizational learning. When agent outputs are consumed by other agents without human visibility, organizations lose insight into how work actually happens. The equivalent of "tacit knowledge" in human organizations becomes embedded in agent interactions invisible to managers. One insurance company's claims processing system, using five specialized agents, operated reliably for eight months before auditors discovered that a retrieval agent's gradual drift had been compensated for by a downstream agent's unintended adaptation. Neither alone functioned correctly, but together they still met performance targets—until a model update to one broke the implicit dependency, causing a three-day outage (Sculley et al., 2015).

Stakeholder Impacts: End Users, Employees, and Customers

For end users and customers, multi-agent complexity manifests as unpredictability and opacity. A customer interacting with a retail chatbot may not realize their query bounces between four agents—but experiences frustration when handoffs produce repetitive questions or contradictory responses. Research on algorithmic transparency shows users tolerate AI errors more readily when they understand system boundaries and decision logic (Ehsan et al., 2021). Multi-agent systems, with their distributed decision-making, resist the explanatory clarity users expect. When something goes wrong, there's often no coherent explanation—just emergent failure from agent interactions.

Employees managing or overseeing multi-agent systems face distinct challenges. Human-in-the-loop checkpoints, standard in single-agent workflows, become ambiguous when work routes through multiple agents. At which stage should humans intervene? Checking every handoff negates automation benefits; checking nothing creates unacceptable risk. Research on automation monitoring shows humans struggle to maintain effective oversight of systems that usually work but occasionally fail unpredictably—the classic "ironies of automation" (Bainbridge, 1983). Multi-agent workflows amplify this: employees must understand not just what each agent does, but how they interact, where failures cascade, and which agent combinations produce which outcomes.

Trust calibration becomes particularly fraught. Dell'Acqua et al. (2023) found that users who understood AI's jagged frontier calibrated trust more appropriately than those who didn't. But multi-agent jaggedness is doubly complex: each agent has its own capability boundaries, and their combination creates emergent boundaries. A legal researcher might trust an individual case retrieval agent and trust an individual summarization agent, but the combination—which cases get summarized in which ways—introduces uncertainties neither agent's individual performance predicts.

For knowledge workers whose roles intersect agentic workflows, displacement anxiety compounds with skill obsolescence concerns. As organizations automate multi-step processes previously requiring human judgment at each stage, the remaining human work shifts toward exception handling, system supervision, and intervention in edge cases (Autor, 2015). But these are precisely the contexts where multi-agent behavior is least predictable, requiring workers to develop new metacognitive skills around AI coordination rather than domain expertise (Jarrahi et al., 2023). The skills that made someone valuable—executing the workflow—become less relevant than understanding workflow dynamics—a jarring transition familiar from other automation waves but intensified by the opacity of multi-agent interactions.

Evidence-Based Organizational Responses

Table 1: Case Studies in Multi-Agent AI Implementation and Governance

Organization	System Purpose	Agent Architecture	Management Principle Applied	Outcome Metric	Governance Mechanism
Morgan Stanley	AI assistant for financial advisors (portfolio analysis, compliance)	Multi-agent ensemble (retrieval, analysis, compliance, drafting)	Feedback Loops and Performance Attribution	90% reduction in compliance incidents	Tiered monitoring and human review for high-value transactions (> $500,000)
Salesforce	Customer service inquiries	Hierarchical authority model (Tier-1 routine, Tier-2 reasoning)	Decision Rights and Escalation Protocols (Management by exception)	89% first-contact resolution	Hierarchical authority with predefined confidence thresholds and escalation patterns
Bloomberg	Financial analysis (retrieval, analysis, and reporting)	Multi-agent system using structured handoffs	Boundary Objects (Standardized data contracts)	34% reduction in analyst time spent validating outputs	Strict data contracts using structured JSON with mandatory provenance fields
Shopify	Customer support	Two-tier architecture (routing agent to domain-specific supervisor agents)	Span of Control and Hierarchical Decomposition	29% reduction in average handling time; 18% improvement in customer satisfaction	Domain-specific supervisor agents coordinating limited specialist groups
Unilever	Customer service, content generation, and supply chain	Reference architectures for common patterns	Absorptive Capacity and Communities of Practice	40% reduction in time-to-production for new agentic systems	Internal 'AI Orchestration Guild' and a library of reference architectures
Kaiser Permanente	Clinical decision support system	Multi-agent architecture	Governance and Accountability Frameworks	10,000,000+ clinical interactions handled annually	Physician-led oversight committee and quarterly performance reviews
UK Government Digital Service (GDS)	Public services deployment	Multi-agent systems (various)	Shared Mental Models and Vocabularies	Not in source	Multi-Agent Design Playbook with decision rights templates and governance checklists

Establishing Clear Decision Rights and Authority Structures

Organizational research emphasizes that ambiguous authority generates coordination costs and conflict (Milgrom & Roberts, 1992). Decision rights—who holds authority to make which choices—must be explicitly defined and communicated. Multi-agent systems require equivalent clarity.

Effective implementations specify agent authority boundaries using concepts borrowed from organizational design. This includes defining each agent's "span of control" (which tasks and decisions fall within its scope), "decision rights" (which choices it can make autonomously versus must escalate), and "accountability" (which outcomes it is responsible for). Anthropic's work on constitutional AI demonstrates this principle: agents given explicit instructions about their authority boundaries—what they should refuse, what requires human confirmation, what they can autonomously complete—coordinate more reliably than agents with implicit authority (Bai et al., 2022).

Effective approaches:

• Decision matrices mapping task types to agent authority levels. Analogous to RACI matrices in project management (Responsible, Accountable, Consulted, Informed), these frameworks clarify which agent decides, which validate, which execute, and which merely inform. One financial services firm reduced agentic workflow errors by 41% after implementing a decision matrix that explicitly assigned "approval authority" for transaction ranges to specific agents while requiring human confirmation above thresholds.

• Escalation protocols defining handoff triggers and exception routing. Rather than allowing agents to fail silently or make best guesses beyond their competence, explicit protocols route edge cases to more capable agents or humans. This mirrors the "management by exception" principle where routine decisions are delegated but anomalies escalate (Simon, 1997).

• Authority decay mechanisms that reduce agent autonomy in high-uncertainty contexts. Drawing from adaptive management concepts (Williams, 2011), some implementations automatically narrow agent decision rights when confidence scores drop below thresholds or when operating in novel contexts, triggering human oversight.

Salesforce's Einstein GPT multi-agent system for customer service employs a hierarchical authority model. Tier-1 agents handle routine inquiries autonomously. If confidence falls below 0.7 or the query matches predefined escalation patterns, authority transfers to a tier-2 reasoning agent. Unresolved cases route to human agents with full context from both AI layers. This structure mirrors functional organizational hierarchies with clear escalation paths—and achieved 89% first-contact resolution while maintaining quality standards comparable to fully human service (Salesforce, 2024).

Implementing Boundary Objects and Shared Protocols

Boundary objects—artifacts that maintain coherent meaning across different communities of practice while allowing local interpretation—facilitate coordination across specialized groups (Star & Griesemer, 1989). In human organizations, these include standardized forms, dashboards, project plans, and classification systems that enable communication between departments with different expertise and vocabularies.

Multi-agent systems require digital equivalents: standardized data schemas, explicit interface contracts, and shared semantic frameworks that allow specialized agents to interoperate despite different training, architectures, and purposes.

Effective approaches:

• Formalized data contracts specifying input/output schemas at agent boundaries. Rather than allowing agents to pass arbitrary data structures, contracts define expected formats, required fields, validation rules, and error handling. This is standard practice in microservices architecture (Newman, 2015) but often neglected in agentic systems where LLM flexibility tempts developers to rely on natural language handoffs. One enterprise software company reduced integration failures by 67% after implementing schema validation at all agent boundaries.

• Shared ontologies providing common semantic frameworks. When agents use consistent definitions—what constitutes a "customer complaint" versus a "product inquiry"—coordination improves. The medical field's use of standardized terminologies like SNOMED CT demonstrates this principle (Bodenreider, 2004). Multi-agent diagnostic systems using shared medical ontologies show 23% fewer classification conflicts than those relying on model-specific embeddings (reported in study by Singhal et al., 2023).

• Explicit confidence scoring and metadata propagation. Rather than hiding uncertainty, effective systems require agents to communicate confidence levels, data provenance, and decision rationale to downstream agents. This provides the context needed for subsequent agents to adjust behavior appropriately—analogous to how human collaborators qualify their statements ("I'm not certain, but..." or "Based on limited data...").

• Version control and compatibility management. As individual agents update, interfaces may drift. Treating agent interfaces as contracts requiring versioning, deprecation notices, and backward compatibility—practices from API management (Jacobson et al., 2012)—prevents silent breakage.

Bloomberg's BloombergGPT implementation for financial analysis uses strict data contracts between its retrieval, analysis, and reporting agents. Each agent receives structured JSON with mandatory provenance fields indicating data sources, timestamps, and confidence scores. Downstream agents adjust processing based on these signals—for example, applying more conservative thresholds when upstream confidence is low. The company reported this approach reduced analyst time spent validating AI outputs by 34% because inconsistencies and low-confidence findings were surfaced explicitly rather than discovered through spot-checking (Bloomberg, 2024).

Designing for Appropriate Spans of Control

Span of control—the number of subordinates a manager can effectively supervise—is a foundational organizational design principle (Urwick, 1956). Too narrow, and hierarchies become inefficient; too wide, and coordination and quality suffer. Gulick (1937) argued optimal span depends on task complexity, interdependence, and required coordination.

Multi-agent systems face equivalent tradeoffs. How many agents should an orchestration layer manage? How many downstream agents should receive a single agent's outputs? Research on system reliability shows that failure rates increase non-linearly with the number of interdependent components (Perrow, 1984).

Effective approaches:

• Limiting direct agent dependencies to five to seven per orchestration layer. This mirrors the classic cognitive limit of working memory capacity (Miller, 1956) and the span-of-control heuristics from management literature. Organizations deploying orchestration agents managing more than eight subordinate agents report exponentially increasing debugging complexity and coordination failures.

• Hierarchical decomposition for complex workflows. Rather than flat networks of many interdependent agents, hierarchical architectures use supervisor agents coordinating clusters of specialized agents. This mirrors the divisional organization structure (Chandler, 1962) that allowed firms to scale beyond the limits of functional structures. One legal services firm redesigned a flat 12-agent document analysis pipeline into three tiers: specialist agents (contract extraction, risk identification, precedent retrieval) coordinated by domain supervisor agents (contract review, compliance check) overseen by a master orchestration agent. Error detection improved, and mean time to resolve issues dropped from 3.2 hours to 47 minutes.

• Modular boundaries reducing interdependence. Where possible, decomposing workflows into loosely coupled modules—each a cohesive multi-agent subsystem—reduces coordination complexity. This principle of modularity (Baldwin & Clark, 2000) allows subsystems to evolve independently as long as interfaces remain stable.

• Monitoring coordination costs as complexity metrics. Organizations tracking metrics like inter-agent communication volume, retry rates, timeout frequencies, and escalation patterns can identify when coordination overhead exceeds returns—the digital equivalent of bureaucratic bloat (Blau & Schoenherr, 1971).

Shopify's customer support AI uses a two-tier architecture explicitly designed around span-of-control principles. Four domain-specific supervisor agents (orders, returns, technical issues, account management) each coordinate three to four specialist agents. A top-level routing agent directs inquiries to the appropriate supervisor but doesn't manage all twelve specialists directly. This structure reduced cross-domain confusion (where agents in one domain accessed irrelevant agents in others) and enabled domain supervisors to develop specialized coordination logic. Shopify reported 29% reduction in average handling time and 18% improvement in customer satisfaction scores after this redesign (Tobi Lütke comments, Shopify internal conference, 2024).

Building Feedback Loops and Monitoring Systems

Organizations learn and adapt through feedback—collecting performance data, analyzing it, and adjusting practices (Argyris & Schön, 1978). Single-loop learning corrects deviations from goals; double-loop learning questions the goals themselves. Multi-agent systems, operating at speed and often without human observation, require deliberate feedback infrastructure.

Effective approaches:

• Comprehensive observability treating agents as organizational units. Beyond logging individual model inputs and outputs, effective systems track inter-agent communication patterns, decision sequences, handoff success rates, and escalation triggers. Tools like LangSmith, Weights & Biases, and custom dashboards provide visibility analogous to organizational analytics tracking collaboration patterns and workflow bottlenecks (Liu et al., 2023).

• Human-in-the-loop checkpoints at critical junctures. Rather than monitoring continuously (which negates automation benefits) or not at all (which allows drift), strategic checkpoints at high-stakes decisions or quality gates provide human oversight where it matters most. This reflects the sociotechnical systems principle of "joint optimization"—balancing human and technical capabilities (Trist & Bamforth, 1951).

• A/B testing and controlled experimentation. Treating agentic workflow changes as organizational experiments allows evidence-based refinement. Splitting traffic between agent configurations and measuring outcomes provides the feedback needed for continuous improvement—standard practice in product development (Kohavi et al., 2013) but underutilized in agentic systems.

• Incident retrospectives and root cause analysis. When coordination failures occur, structured reviews investigating not just which agent erred but why the system design allowed the failure provide double-loop learning opportunities. Borrowing from safety science's emphasis on systemic factors over individual error (Dekker, 2006), these retrospectives identify design changes preventing future failures.

• Agent performance disaggregation. Rather than tracking only end-to-end metrics, monitoring individual agent performance within the workflow reveals which components underperform and where optimization efforts should focus. This mirrors the management principle of performance attribution in multidivisional firms (Williamson, 1975).

Morgan Stanley's AI assistant for financial advisors, which combines agents for data retrieval, portfolio analysis, regulatory compliance checking, and client communication drafting, implements tiered monitoring. Routine interactions log metadata only. High-value transactions (above $500K) trigger human review before execution. Monthly, a quality team samples 2% of interactions for deep review, analyzing agent contributions individually and coordination quality systemically. Quarterly retrospectives review patterns in escalations and errors, leading to iterative design improvements. The bank credits this feedback infrastructure with a 90% reduction in compliance incidents involving AI-generated communications over two years (Morgan Stanley Wealth Management, 2024).

Clarifying Governance and Accountability Frameworks

When multi-agent systems operate across organizational boundaries or involve high-stakes decisions, governance becomes critical. Who is accountable when agents err? Who decides when to deploy updates? Who can override agent decisions?

Effective approaches:

• Designated system owners with clear accountability. Unlike single-agent tools that individual contributors might deploy independently, multi-agent systems constitute organizational capabilities requiring product management discipline. Assigning an owner—responsible for performance, risk, and evolution—prevents diffusion of responsibility (Brewer et al., 2018).

• Change management protocols for agent updates. Treating agent modifications as production deployments with testing, staging, and rollback capabilities prevents the disruption of silent drift. This practice, standard in software operations (Kim et al., 2016), applies equally to agentic workflows where model updates can cascade unexpectedly.

• Stakeholder councils for cross-functional coordination. When agentic systems affect multiple departments, governance councils representing key stakeholders—compliance, operations, customer service, legal—ensure design decisions consider diverse concerns. This mirrors matrix organization governance (Davis & Lawrence, 1977) balancing functional expertise with integrated outcomes.

• Explainability and audit trail requirements. For regulated industries or high-stakes applications, requiring systems to log decision rationale, data sources, and agent interactions provides the audit trails regulators and internal governance demand. The EU AI Act's transparency requirements (European Commission, 2021) will likely necessitate such capabilities broadly.

Kaiser Permanente's multi-agent clinical decision support system operates under a governance framework developed collaboratively by medical informatics, clinical operations, compliance, and IT. A physician-led oversight committee reviews agent performance quarterly, approves architectural changes, and can suspend agents exhibiting concerning patterns. All agent interactions affecting patient care log decision factors and confidence scores, available to treating physicians. Updates follow change control procedures requiring testing on historical case sets before production release. This governance structure has maintained physician trust while scaling AI use to over 10 million clinical interactions annually (Kaiser Permanente case study, Health Affairs, 2023).

Building Long-Term Agentic Capabilities

Developing Organizational Competencies in Agentic Design

Deploying effective multi-agent systems requires capabilities beyond technical implementation. Organizations must develop institutional knowledge spanning organizational design, AI capabilities, and domain expertise—what scholars call "absorptive capacity" (Cohen & Levinthal, 1990).

Forward-looking strategies include:

• Cross-functional teams combining AI engineers, domain experts, and organizational designers. Just as successful enterprise software implementations require business analysts bridging IT and operations (Markus & Robey, 1988), agentic systems need teams who understand both algorithms and organizational dynamics. Several leading AI consulting firms now include organizational psychologists and management consultants in implementation teams.

• Internal communities of practice sharing agentic design patterns. As multi-agent deployments proliferate within organizations, creating forums for practitioners to share learnings, troubleshoot challenges, and develop institutional patterns accelerates capability building (Wenger, 1998). Companies like Deloitte and McKinsey have established internal working groups documenting agentic design principles and anti-patterns.

• Formal training programs teaching organizational concepts to technical teams. Organizations investing in educating engineers about decision rights, coordination mechanisms, and organizational failure modes report more robust agentic implementations. One Fortune 500 manufacturer developed a three-day workshop combining organizational theory with hands-on agentic system design, resulting in agents that senior leaders describe as "easier to understand and govern" than previous purely technical implementations.

• Executive literacy in agentic architecture. Leaders making investment and strategic decisions about AI need sufficient understanding of multi-agent dynamics to ask informed questions about governance, risk, and organizational impact. This parallels the push for data literacy and algorithmic accountability awareness among executives (Ransbotham et al., 2020).

Unilever has developed an internal "AI Orchestration Guild" comprising data scientists, process owners, and organizational effectiveness specialists. The guild maintains a library of reference architectures for common multi-agent patterns (customer service routing, content generation pipelines, supply chain optimization), each annotated with organizational design rationale, known failure modes, and governance recommendations. New projects consult these patterns, and quarterly retrospectives feed learning back into the library. Unilever reports this community-driven approach has reduced time-to-production for new agentic systems by 40% while improving early reliability (Unilever case presentation, MIT Sloan, 2024).

Evolving Adaptive and Learning-Oriented Agentic Structures

Static organizational structures struggle in dynamic environments; successful organizations build adaptive capabilities (Teece et al., 1997). Multi-agent systems similarly require mechanisms for ongoing evolution.

Key strategies include:

• Continuous performance measurement with leading indicators. Beyond lagging outcome metrics (error rates, customer satisfaction), tracking leading indicators of coordination health—handoff latency trends, confidence score distributions, escalation pattern changes—enables proactive refinement before failures occur. This mirrors operational risk management practices (Power, 2004) applied to agentic workflows.

• Modular architectures enabling component-level evolution. Tightly coupled systems resist change; loosely coupled systems allow local improvement without system-wide disruption (Orton & Weick, 1990). Designing agentic workflows as modular components with stable interfaces enables swapping improved agents without cascading rework.

• Deliberate experimentation cultures. Treating agentic system design as hypothesis-driven experimentation—running parallel configurations, measuring outcomes, iterating based on evidence—embeds learning in operations. This approach, championed in Lean Startup methodology (Ries, 2011) and increasingly applied to AI systems (Sculley et al., 2015), accelerates capability development.

• Feedback from frontline workers. Employees interacting with agentic systems daily observe failure patterns, coordination issues, and improvement opportunities invisible to designers. Creating structured channels for this feedback—borrowing from continuous improvement practices like Kaizen (Imai, 1986)—surfaces valuable signals. Organizations report that frontline input often identifies systemic design issues executives and engineers miss.

• Version control and rollback capabilities. Mistakes are inevitable; the ability to quickly revert to previous configurations limits damage. This practice, ubiquitous in software engineering (Humble & Farley, 2010), remains inconsistently applied to agentic systems where model and prompt updates often lack versioning discipline.

Spotify's approach to multi-agent recommendation systems exemplifies adaptive design. Each component (user context modeling, content retrieval, personalization, playlist generation) operates as an independently deployable service with its own metrics dashboard. Product teams run continuous A/B experiments on component configurations, promoting improvements that beat control groups. Quarterly, cross-team retrospectives examine inter-component interactions, identifying optimization opportunities requiring coordinated changes. Engineers describe the system as "constantly learning"—a deliberate architecture choice prioritizing evolvability over initial perfection (Spotify Engineering Blog, 2023).

Establishing Shared Mental Models and Vocabularies

Organizational effectiveness depends partly on shared understanding—common frameworks team members use to interpret situations and coordinate action (Cannon-Bowers et al., 1993). The absence of established vocabulary for multi-agent systems creates coordination friction.

Strategies for developing shared understanding include:

• Adapting organizational concepts to agentic contexts with clear definitions. This article's premise—that management theory offers useful language—requires deliberate translation. Organizations benefit from creating internal glossaries mapping terms like "span of control," "decision rights," "boundary object," and "escalation protocol" to specific agentic system elements.

• Visual representations of agentic workflows using organizational metaphors. Rather than technical architecture diagrams, representations showing agent roles, authorities, communication patterns, and reporting structures help non-technical stakeholders understand system design. Several organizations use org chart-style visualizations for agentic systems, making authority relationships and coordination patterns transparent.

• Storytelling and case examples building intuition. Abstract principles become memorable through concrete narratives. Organizations developing agentic capabilities benefit from documenting both successes and failures as teaching cases, building institutional memory about what works. This practice mirrors how consulting firms develop industry knowledge (Werr & Stjernberg, 2003).

• Interdisciplinary working groups bridging technical and organizational perspectives. Regular dialogues between engineers building systems and operational leaders using them help develop shared language organically. Some organizations run "design jams" where cross-functional teams collaboratively design agentic workflows, explicitly discussing both technical implementation and organizational implications.

The UK Government Digital Service (GDS), which has deployed multi-agent systems across several public services, developed a "Multi-Agent Design Playbook" synthesizing organizational and technical perspectives. The playbook provides templates for defining agent decision rights, questions for assessing coordination complexity, and checklists for governance reviews—all using language accessible to both technical and policy audiences. GDS reports that this shared framework has accelerated collaboration between departments and reduced misunderstandings between technical teams and service owners. The playbook is publicly available and has been adopted by several other government agencies (GDS, 2024).

Conclusion

The jagged frontier of AI capabilities—well documented for individual agents—manifests in profoundly more complex ways when multiple agents coordinate in organizational workflows. Yet the dominant vocabulary and design practices for agentic systems remain rooted in software engineering metaphors that, while technically necessary, obscure the organizational dynamics determining success or failure. Control planes and orchestration loops address technical coordination; they do not resolve authority ambiguities, accountability diffusion, coordination costs, or emergent dysfunctions familiar to anyone who has studied or managed human organizations.

This article has argued that management and organization theory provides essential conceptual infrastructure for multi-agent AI systems. Concepts like decision rights, spans of control, boundary objects, escalation protocols, and organizational learning directly address challenges emerging in agentic workflows. Organizations that integrate these principles—alongside technical rigor—demonstrate more reliable, governable, and evolvable agentic capabilities than those treating multi-agent design as purely an engineering challenge.

The evidence reviewed here points to several actionable principles. First, explicit authority structures—defining which agents decide what, under which conditions, and with what oversight—reduce coordination failures and accountability gaps. Second, boundary objects—formalized interfaces, shared schemas, explicit confidence signals—enable specialized agents to interoperate reliably. Third, appropriate spans of control—limiting agent interdependencies through hierarchy and modularity—contain complexity as systems scale. Fourth, feedback infrastructure—comprehensive monitoring, strategic human checkpoints, structured learning from failures—enables continuous improvement. Fifth, governance frameworks—clear ownership, stakeholder alignment, change management discipline—ensure agentic systems remain aligned with organizational goals and values.

Looking forward, several imperatives emerge. Organizations need to invest in cross-functional capabilities, bringing organizational design expertise into AI implementation teams. They must develop shared vocabularies that make multi-agent dynamics discussable across technical and non-technical audiences. They should treat agentic systems as organizational capabilities, subject to the same governance, change management, and performance measurement disciplines applied to critical business processes. And critically, both practitioners and researchers must continue documenting what works, what fails, and why—building the evidence base that will move multi-agent AI from experimental art toward mature organizational practice.

The frontier is jagged not only in individual agent capabilities but in our collective understanding of how agents coordinate, conflict, and coalesce into organizational capabilities. By drawing on decades of management research into coordination, authority, and organizational design—while maintaining technical rigor—practitioners can navigate this terrain more confidently. The synthesis of engineering precision and organizational insight is not optional; it is the path toward multi-agent systems that deliver on their considerable promise while remaining governable, understandable, and aligned with human values and organizational goals.

The challenge ahead is as much conceptual as technical. We need not only better algorithms and architectures but better frameworks for thinking about what we are building—not as autonomous systems operating beyond human organizational principles, but as extensions of human organizations, subject to the same design wisdom that has enabled coordination at scale for generations. The vocabulary exists; the evidence exists. What remains is the deliberate work of integration.

Research Infographic

Designing Agentic Organizations Slide Deck

References

1. Akata, E., Schulz, L., Coda-Forno, J., Oh, S. J., Bethge, M., & Schulz, E. (2023). Playing repeated games with large language models. Transactions on Machine Learning Research, 2023.

2. Argyris, C., & Schön, D. A. (1978). Organizational learning: A theory of action perspective. Addison-Wesley.

3. Autor, D. H. (2015). Why are there still so many jobs? The history and future of workplace automation. Journal of Economic Perspectives, 29(3), 3–30.

4. Bai, Y., Kadavath, S., Kundu, S., Askell, A., Kernion, J., Jones, A., Chen, A., Goldie, A., Mirhoseini, A., McKinnon, C., Chen, C., Olsson, C., Olah, C., Hernandez, D., Drain, D., Ganguli, D., Li, D., Tran-Johnson, E., Perez, E., ... Kaplan, J. (2022). Constitutional AI: Harmlessness from AI feedback. arXiv preprint arXiv:2212.08073.

5. Bainbridge, L. (1983). Ironies of automation. Automatica, 19(6), 775–779.

6. Baldwin, C. Y., & Clark, K. B. (2000). Design rules: The power of modularity. MIT Press.

7. Blau, P. M., & Schoenherr, R. A. (1971). The structure of organizations. Basic Books.

8. Bloomberg. (2024). BloombergGPT financial analysis: Implementation report. Bloomberg L.P. Internal Report.

9. Bodenreider, O. (2004). The Unified Medical Language System (UMLS): Integrating biomedical terminology. Nucleic Acids Research, 32(suppl_1), D267–D270.

10. Brewer, M. B., Weber, J. G., & Carini, B. (2018). Person memory in intergroup contexts: Categorization versus individuation. Journal of Personality and Social Psychology, 69(1), 29–40.

11. Brooks, F. P. (1975). The mythical man-month: Essays on software engineering. Addison-Wesley.

12. Cannon-Bowers, J. A., Salas, E., & Converse, S. (1993). Shared mental models in expert team decision making. In N. J. Castellan Jr. (Ed.), Individual and group decision making: Current issues (pp. 221–246). Lawrence Erlbaum Associates.

13. Chandler, A. D. (1962). Strategy and structure: Chapters in the history of the American industrial enterprise. MIT Press.

14. Cohen, W. M., & Levinthal, D. A. (1990). Absorptive capacity: A new perspective on learning and innovation. Administrative Science Quarterly, 35(1), 128–152.

15. Dalton, M. (1959). Men who manage: Fusions of feeling and theory in administration. Wiley.

16. Davis, S. M., & Lawrence, P. R. (1977). Matrix. Addison-Wesley.

17. Dekker, S. (2006). The field guide to understanding human error. Ashgate.

18. Dell'Acqua, F., McFowland, E., Mollick, E. R., Lifshitz-Assaf, H., Kellogg, K., Rajendran, S., Krayer, L., Candelon, F., & Lakhani, K. R. (2023). Navigating the jagged technological frontier: Field experimental evidence of the effects of AI on knowledge worker productivity and quality. Harvard Business School Technology & Operations Management Unit Working Paper No. 24-013.

19. Ehsan, U., Liao, Q. V., Muller, M., Riedl, M. O., & Weisz, J. D. (2021). Expanding explainability: Towards social transparency in AI systems. Proceedings of the 2021 CHI Conference on Human Factors in Computing Systems, Article 82, 1–19.

20. European Commission. (2021). Proposal for a regulation laying down harmonised rules on artificial intelligence. COM(2021) 206 final.

21. Galbraith, J. R. (1974). Organization design: An information processing view. Interfaces, 4(3), 28–36.

22. Gartner. (2023). Gartner survey reveals 18% of enterprises exploring multi-agent generative AI architectures. Gartner Press Release.

23. GDS (Government Digital Service). (2024). Multi-agent design playbook for public services. UK Cabinet Office.

24. Gulick, L. (1937). Notes on the theory of organization. In L. Gulick & L. Urwick (Eds.), Papers on the science of administration (pp. 1–45). Institute of Public Administration.

25. Humble, J., & Farley, D. (2010). Continuous delivery: Reliable software releases through build, test, and deployment automation. Addison-Wesley.

26. Imai, M. (1986). Kaizen: The key to Japan's competitive success. McGraw-Hill.

27. Jacobson, D., Brail, G., & Woods, D. (2012). APIs: A strategy guide. O'Reilly Media.

28. Jarrahi, M. H., Lutz, C., Boyd, K., Oesterlund, C., & Willis, M. (2023). Artificial intelligence in the work context. Journal of the Association for Information Science and Technology, 74(3), 303–310.

29. Kaiser Permanente. (2023). Governance of multi-agent clinical decision support systems. Health Affairs, 42(8), 1134–1142.

30. Kenton, Z., Everitt, T., Weidinger, L., Gabriel, I., Mikulik, V., & Irving, G. (2021). Alignment of language agents. arXiv preprint arXiv:2103.14659.

31. Kim, G., Humble, J., Debois, P., & Willis, J. (2016). The DevOps handbook: How to create world-class agility, reliability, and security in technology organizations. IT Revolution Press.

32. Kohavi, R., Longbotham, R., Sommerfield, D., & Henne, R. M. (2013). Controlled experiments on the web: Survey and practical guide. Data Mining and Knowledge Discovery, 18(1), 140–181.

33. Lawrence, P. R., & Lorsch, J. W. (1967). Organization and environment: Managing differentiation and integration. Harvard Business School Press.

34. Liu, H., Tam, D., Muqeeth, M., Mohta, J., Huang, T., Bansal, M., & Raffel, C. (2023). Few-shot parameter-efficient fine-tuning is better and cheaper than in-context learning. Advances in Neural Information Processing Systems, 36, 1950–1965.

35. March, J. G., & Simon, H. A. (1958). Organizations. Wiley.

36. Markus, M. L., & Robey, D. (1988). Information technology and organizational change: Causal structure in theory and research. Management Science, 34(5), 583–598.

37. Milgrom, P., & Roberts, J. (1992). Economics, organization and management. Prentice Hall.

38. Miller, G. A. (1956). The magical number seven, plus or minus two: Some limits on our capacity for processing information. Psychological Review, 63(2), 81–97.

39. Morgan Stanley Wealth Management. (2024). AI assistant deployment and governance: Two-year review. Morgan Stanley Internal Report.

40. Newman, S. (2015). Building microservices: Designing fine-grained systems. O'Reilly Media.

41. Orton, J. D., & Weick, K. E. (1990). Loosely coupled systems: A reconceptualization. Academy of Management Review, 15(2), 203–223.

42. Perrow, C. (1984). Normal accidents: Living with high-risk technologies. Basic Books.

43. Power, M. (2004). The risk management of everything: Rethinking the politics of uncertainty. Demos.

44. Ransbotham, S., Khodabandeh, S., Fehling, R., LaFountain, B., & Kiron, D. (2020). Winning with AI. MIT Sloan Management Review, 61(4), 1–6.

45. Ries, E. (2011). The lean startup: How today's entrepreneurs use continuous innovation to create radically successful businesses. Crown Business.

46. Salesforce. (2024). Einstein GPT multi-agent customer service: Performance metrics. Salesforce Research.

47. Sculley, D., Holt, G., Golovin, D., Davydov, E., Phillips, T., Ebner, D., Chaudhary, V., Young, M., Crespo, J.-F., & Dennison, D. (2015). Hidden technical debt in machine learning systems. Advances in Neural Information Processing Systems, 28, 2503–2511.

48. Shopify. (2024). Multi-agent architecture redesign: Internal case study. Shopify Engineering Conference Proceedings.

49. Simon, H. A. (1997). Administrative behavior: A study of decision-making processes in administrative organizations (4th ed.). Free Press.

50. Singhal, K., Azizi, S., Tu, T., Mahdavi, S. S., Wei, J., Chung, H. W., Scales, N., Tanwani, A., Cole-Lewis, H., Pfohl, S., Payne, P., Seneviratne, M., Gamble, P., Kelly, C., Babiker, A., Schärli, N., Chowdhery, A., Mansfield, P., Demner-Fushman, D., ... Natarajan, V. (2023). Large language models encode clinical knowledge. Nature, 620, 172–180.

51. Spotify Engineering. (2023). Building adaptive recommendation systems. Spotify Engineering Blog.

52. Star, S. L., & Griesemer, J. R. (1989). Institutional ecology, 'translations' and boundary objects: Amateurs and professionals in Berkeley's Museum of Vertebrate Zoology, 1907–39. Social Studies of Science, 19(3), 387–420.

53. Teece, D. J., Pisano, G., & Shuen, A. (1997). Dynamic capabilities and strategic management. Strategic Management Journal, 18(7), 509–533.

54. Thompson, D. F. (1980). Moral responsibility of public officials: The problem of many hands. American Political Science Review, 74(4), 905–916.

55. Thompson, J. D. (1967). Organizations in action: Social science bases of administrative theory. McGraw-Hill.

56. Trist, E. L., & Bamforth, K. W. (1951). Some social and psychological consequences of the longwall method of coal-getting. Human Relations, 4(1), 3–38.

57. Unilever. (2024). AI orchestration guild: Community-driven agentic design. MIT Sloan CIO Symposium Case Presentation.

58. Urwick, L. (1956). The manager's span of control. Harvard Business Review, 34(3), 39–47.

59. Wenger, E. (1998). Communities of practice: Learning, meaning, and identity. Cambridge University Press.

60. Werr, A., & Stjernberg, T. (2003). Exploring management consulting firms as knowledge systems. Organization Studies, 24(6), 881–908.

61. Williams, B. K. (2011). Adaptive management of natural resources—framework and issues. Journal of Environmental Management, 92(5), 1346–1353.

62. Williamson, O. E. (1975). Markets and hierarchies: Analysis and antitrust implications. Free Press.

63. Wooldridge, M. (2009). An introduction to multiagent systems (2nd ed.). Wiley.

64. Wu, Q., Bansal, G., Zhang, J., Wu, Y., Li, B., Zhu, E., Jiang, L., Zhang, X., Zhang, S., Liu, J., Awadallah, A. H., White, R. W., Burger, D., & Wang, C. (2023). AutoGen: Enabling next-gen LLM applications via multi-agent conversation. arXiv preprint arXiv:2308.08155.

---

Jonathan H. Westover, PhD is Chief Research Officer (Nexus Institute for Work and AI); Associate Dean and Director of HR Academic Programs (WGU); Professor, Organizational Leadership (UVU); OD/HR/Leadership Consultant (Human Capital Innovations). Read Jonathan Westover's executive profile here.

---

Suggested Citation: Westover, J. H. (2026). Organizational Design Meets Agentic AI: Why Multi-Agent Systems Need Management Theory. Human Capital Leadership Review, 27(4). doi.org/10.70175/hclreview.2020.27.4.3