ORGANIZATIONAL DESIGN & DEVELOPMENT

5 ORGANIZATIONAL MODELS FOR HUMAN–AI COLLABORATION IN BUSINESS

Compare structures, choose a suitable model and design human–AI collaboration

Phillip LeConsultant in Organizational Restructuring and Development in the AI Era

Research and source review: 20 October 2026 · 5 original illustrations · 15 company examples

A GUIDE TO STRUCTURAL CHOICES

Choose a structure based on business objectives, how value is created and operating capabilities. Use the conditions in column 3 to screen options, then compare benefits, costs and solutions in column 5.

5 models15 company examples22 sourcesPeople and AI

Compare and choose

Select a card to filter models; select an illustration to enlarge it. Scroll the table horizontally when needed.

Quick guide Select a priority below to explore a reference model. Businesses can combine different models at different organizational levels.

5 / 5 models
Organizational model and illustrationModel definition and characteristicsConditions for adoptionIllustrative companiesBenefits, drawbacks and solutions
Functional

Prioritize expertise and efficiency

Selection question
Does a relatively unified business model need shared specialists and standardization?

Principle
Group people by specialty, such as sales, operations, finance and HR. Each person has one direct manager; enterprise-wide results are integrated at executive level.

Authority
Functional heads decide on capabilities, methods and resources within delegated scope. Cross-functional issues need a process owner or a shared decision mechanism.

Distinction
Cross-departmental collaboration does not automatically create a matrix. A matrix exists when substantive authority is distributed across multiple dimensions.

Framework sources [C1] [C3] [C5]

Industry and work
Technology and digital services with integrated products; also potentially suitable for businesses with relatively repeatable specialist processes.

Objectives and strategy
Improve professional quality, efficiency and consistency. Share capabilities rather than replicate a full set within every unit.

Scale and complexity
Often a straightforward starting structure for small or medium businesses. Large businesses can also use it if they have strong cross-functional integration. There is no fixed headcount threshold.

Budget
Functional duplication is generally lower than in a divisional structure. Budget for department heads, shared data and cross-functional coordination.

Culture and prerequisites
Respect expertise while sharing outcome objectives. Assign accountable owners to processes that cross departments.

Avoid a purely functional model when
Products or markets have substantially different business economics and require separate P&L owners.

Technology and digital services
Three documented company examples

Apple A
Company-level functional structure in a 2020 study. A documented historical example, not a verified 2026 organizational chart. [E1]

Airbnb A
The CEO described a shift to a functional structure in 2020 in a 2021 interview. Do not generalize this to the entire current organization. [E2]

GitLab A
The published handbook describes functional management and one formal manager, alongside cross-functional collaboration teams. [E3]

Benefits and how to realize them

1. Deeper specialist expertise
Use shared professional standards, technical guidance and capability-development programs.

2. Economies of scale
Share specialist teams and tools; allocate capacity according to actual demand.

3. Clear reporting lines
Publish the decision rights and performance expectations of each functional head.

Drawbacks and solutions

1. Departmental silos and broken handoffs
Solution Assign an end-to-end process owner; agree handoff commitments and shared outcome measures.

2. The CEO becomes a bottleneck
Solution Delegate according to impact; name the final decision-maker for cross-functional decisions and set resolution deadlines.

3. Technical optimization loses sight of customers
Solution Measure customer experience and end-to-end turnaround; form cross-functional teams for priority issues.

Performance measures
End-to-end turnaround; handoff errors; share of decisions escalated to the CEO; cost per conforming output.

Divisional

Prioritize markets and P&L accountability

Selection question
Do multiple products, customer groups or territories require their own objectives and P&L accountability?

Principle
Group activities by product, customer or geography. Each unit has the functions it needs, either internally or through shared services.

Authority
Unit leaders are accountable for business results within delegated authority. The corporate center retains portfolio strategy, capital allocation, common standards and oversight.

Distinction
A division means a business unit, not a finance or HR department. Each unit does not have to own every function separately.

Framework sources [C1] [C2] [C5]

Industry and work
Consumer goods and food businesses spanning multiple categories or regions. Units have sufficiently different customer needs, channels or business cycles.

Objectives and strategy
Expand portfolios and geographic reach, respond quickly to markets, and make revenue, cost and P&L accountability explicit.

Scale and complexity
Each unit needs sufficient work, resources and capable business management. Business diversity matters more than total headcount alone.

Budget
The business must sustain potentially duplicated management and functional costs. Use shared services to retain scale advantages; separate transition costs from recurring costs.

Culture and prerequisites
Provide unit-level performance reporting, cost-allocation rules and clear delegated authority. Encourage cooperation alongside business accountability.

Avoid this model when
Units are too small, serve the same market, or lack the resources and data for independent management.

Consumer goods and food
Three documented company examples

P&G A
The published structure uses category SBUs with performance accountability, supported by functions and shared services. It is not a purely divisional model. [E4]

Unilever A
The reviewed corporate page presents four category-based business groups. This is more recent than the earlier five-group model. [E5]

Nestlé A
Effective 1 January 2026: three geographic zones and two globally managed businesses, illustrating geographic divisions combined with business categories. [E6]

Benefits and how to realize them

1. Closer to market needs
Delegate portfolio, channel and service decisions within limits; track unit-level growth and retention.

2. Clear business accountability
Connect decision rights to P&L and capital employed; assess both results and the quality of growth.

3. Easier portfolio expansion
Standardize how units are established, integrated or reconfigured; retain capabilities that should be shared.

Drawbacks and solutions

1. Duplicated functions and costs
Solution Centralize services with scale benefits; publish the shared-service catalog, service levels and costs.

2. Internal competition and customer conflicts
Solution Define segments, account ownership and cooperation rules; include enterprise-wide benefit measures.

3. Inconsistent data and controls
Solution Use common data and reporting standards; clarify corporate and unit decision rights, with periodic reviews.

Performance measures
Profit and capital by unit; duplicated functional costs; local market decision time; shared-service utilization.

Matrix

Balance two management dimensions

Selection question
Must shared specialists also deliver results by project, product or territory?

Principle
Overlay two or more organizational dimensions, such as function and project, or product and geography. People or units carry clearly defined responsibilities across dimensions.

Authority
A matrix may be weak, balanced or strong depending on the actual authority of functional and project leaders. Clarify who decides on work, capability, budgets and performance reviews.

Distinction
Two lines on a chart are only notation. A matrix works through delegated authority and conflict-resolution mechanisms, not merely by adding another manager.

Framework sources [C3] [C5] [C6]

Industry and work
B2B industrial technology, equipment and digital infrastructure; multiple projects or markets sharing scarce specialist resources.

Objectives and strategy
Combine specialist depth with outcome accountability and market responsiveness; balance priorities that each have strategic importance.

Scale and complexity
Both dimensions need sufficient activity. Mature project and functional management matter most; a large workforce alone is insufficient.

Budget
Allow for coordination, capacity planning, decision meetings and portfolio tools. Do not select a matrix simply to reduce management headcount.

Culture and prerequisites
Shared priorities, resource-allocation schedules, dispute-resolution authority and joint performance reviews. Leaders must negotiate around common objectives.

Avoid this model when
Leaders disagree on objectives, routinely pass conflicts down to employees, or lack a mechanism for resolving disagreements between dimensions.

B2B industrial technology
Three documented company examples

Schneider Electric A
A VP of Operations described a matrix within their area of responsibility in a 2023 source. This does not classify the whole group under one structure. [E7]

Siemens B
A role in Smart Infrastructure Buildings refers to a global matrix organization. This is localized recruitment evidence from a 2025 indexed copy. [E8]

Ericsson B
A BCSS leadership role describes a multi-geography matrix context. This supports the unit-level environment, not a complete group authority chart. [E9]

Benefits and how to realize them

1. Share scarce specialists
Manage capacity centrally and agree allocation shares and priorities so specialists can serve multiple outcomes.

2. Balance two strategic dimensions
Create shared plans and measures across dimensions; make trade-off decisions transparent.

3. Cross-unit exchange and learning
Use professional forums and project outcomes to develop capabilities and reuse knowledge.

Drawbacks and solutions

1. Conflicting instructions from two managers
Solution Allocate authority by decision type. Assign one final decision-maker per decision, a deadline and an escalation route for deadlocks.

2. Project overload and excessive coordination meetings
Solution Make capacity visible, limit work in progress, and retain only meetings that produce specific decisions.

3. Inconsistent employee evaluations
Solution Agree objectives at the start of the review period, combine feedback from both dimensions and name the final evaluation owner.

Performance measures
Conflict-resolution time; simultaneous projects per person; coordination hours; commitment fulfillment across both dimensions.

Team-based

Prioritize speed and end-to-end outcomes

Selection question
Can a cross-functional team own a product, service or end-to-end outcome?

Principle
Organize around cross-functional teams with a clear mission, customer and output. Each team has the capabilities to perform most of its assigned workflow.

Authority
Delegate prioritization and execution within boundaries. Establish outcome accountability, people management and professional standards.

Distinction
A temporary collaboration team does not mean that the entire business has a team-based structure. Autonomy does not mean deciding everything independently or dispensing with management.

Framework sources [C1] [C2] [C7]

Industry and work
Software and digital services where products can be divided into ownership domains and improved frequently through customer feedback.

Objectives and strategy
Shorten time to market, reduce handoffs and strengthen end-to-end accountability. Prioritize rapid learning and customer experience.

Scale and complexity
Each team needs sufficient delivery capability and manageable external dependencies. Start with one team if appropriate; a company-wide change is not required.

Budget
Give teams relatively stable capacity. Budget for shared platforms, training and handover time. Costs can rise if every team rebuilds everything independently.

Culture and prerequisites
Leaders genuinely delegate. Objectives are measurable, feedback data is available, and quality standards and team boundaries are clear.

Avoid this model when
Teams are autonomous in name only, with every task requiring another department’s permission or leaders withholding prioritization rights and resources.

Software and digital services
Three documented company examples

Amazon and AWS A
Small teams own products or services end to end. This operating approach applies in suitable contexts; not every department works identically. [E10]

Atlassian A
A 2019 article with leadership input describes teams combining design, engineering and product. The evidence is time-specific. [E11]

Spotify A
A 2020 engineering source describes autonomous squads and coordination of shared changes. The historic Spotify chart is not a current universal standard. [E12]

Benefits and how to realize them

1. Fewer handoffs and faster delivery
Give teams end-to-end outcomes and sufficient skills and decision rights for routine work.

2. Closer customer focus
Provide access to usage data and feedback; run small experiments to validate value before scaling.

3. Stronger ownership
Assess value, quality and operations; retain accountability after a product goes live.

Drawbacks and solutions

1. Duplicated tools and standards
Solution Use shared platforms and professional communities; specify what teams may choose and what must be shared.

2. Dependencies between teams create bottlenecks
Solution Redesign boundaries around value streams; agree interfaces, service commitments and dependency owners.

3. Weak professional development or individual accountability
Solution Provide people managers, professional coaching and capability frameworks. State the responsibilities of each team role.

Performance measures
Time from idea to use; defects and rework; customer outcomes; share of work waiting on other teams.

Network

Prioritize core capabilities and partner coordination

Selection question
Does advantage come from core capabilities and coordination, while independent partners can perform many links in the value chain?

Principle
A central coordinating unit connects internal capabilities and external partners, including manufacturing, logistics, technology or services. Value is created through a network of relationships.

Authority
Independent partners are coordinated through contracts, service commitments, standards and data. A partnership link is not an employee reporting line.

Distinction
Outsourcing one activity does not establish that the entire business has a network structure. Define the value-chain scope being assessed.

Framework sources [C2] [C4] [C5]

Industry and work
Sportswear and footwear brands with external manufacturing and logistics networks. Outputs can be specified and quality assessed.

Objectives and strategy
Focus on design, brand or customer relationships; access partner capabilities and adjust capacity to demand.

Scale and complexity
There is no fixed internal headcount threshold. Partner-management, quality and continuity capabilities must match network complexity.

Budget
Owned production assets may be reduced, but include the full cost of partners, integration, oversight, inventory, rework and contingencies.

Culture and prerequisites
Capable partners, clear standards and data rights. Retain core capabilities and an accountable end-to-end owner internally.

Avoid this model when
An outsourced activity determines proprietary advantage but quality is hard to measure, partners are difficult to replace or dependency risks remain uncontrolled.

Sportswear and footwear
Three documented company examples

NIKE A
The fiscal 2026 annual report describes most products as manufactured by independent contractors. This evidences a supply-chain network. [E13]

adidas A
The 2025 report describes outsourcing almost all production to independent partners, combined with a logistics network. [E14]

PUMA A
The 2025 report describes a business that designs products and coordinates external manufacturing, suppliers and logistics. [E15]

Benefits and how to realize them

1. Focus on differentiating capabilities
Identify and invest in capabilities that must remain internal; select partners for activities that can be purchased or jointly delivered.

2. Flexible capacity expansion
Agree volume flexibility and output standards; maintain insight into partner capacity.

3. Access external expertise
Co-develop capabilities and share necessary standards and data; evaluate end-to-end results.

Drawbacks and solutions

1. Partner dependence and supply disruption
Solution Diversify sources where appropriate; establish alternatives, rehearse transfers and monitor critical dependencies.

2. Inconsistent quality or knowledge leakage
Solution Specify outputs, inspection and traceability; apply task-based data permissions and protect core capabilities.

3. Hidden costs and accountability gaps
Solution Measure total cost and end-to-end service. Retain a value-chain owner, error-resolution rules and cross-partner coordination mechanisms.

Performance measures
On-time, in-full delivery; partner defects; total cost to serve; partner dependence; time to activate a fallback option.

A and B indicate the level of source confirmation. A is a direct description at the source date; B is localized evidence. Select a source code to review its scope and timing. Illustrations explain principles, not staffing levels.

Prerequisites to check before scoring

ModelRequired conditionsIf conditions are missing
FunctionalCross-functional integration mechanisms and an end-to-end process owner.If a process owner is missing, first design handoffs and final decision rights.
DivisionalUnits with sufficient resources, capable business management and separate performance data.If resources or data are insufficient, retain functional management and pilot unit-level accountability first.
MatrixDecision-based authority, capacity plans and an escalation route for disagreements.If absent, do not recommend immediate implementation. Build capabilities or run a limited pilot.
Team-basedTeams can own outcomes and have sufficient skills and prioritization authority.Resolve dependencies and delegate authority; simply renaming departments as teams is insufficient.
NetworkMeasurable outputs, capable partners, continuity plans and a value-chain owner.Retain critical work internally or pilot one manageable link in the chain.

An evidence-based selection process

  1. Define the design level. Specify whether the scope is the company, business unit, function, product or partner chain. Establish the baseline and objectives within the same scope.
  2. Gather evidence. Objectives and customers; product portfolio; value streams; decision rights; workload and capacity; management capabilities; data; costs and practical constraints.
  3. Screen mandatory prerequisites. Do not recommend immediate implementation of an option that fails the prerequisite checks. Record what must change to qualify.
  4. Compare at least two feasible options. Options may combine a base structure with teams, shared services or a network within a defined scope. Include improving the current structure as an alternative.
  5. Score with evidence and test sensitivity. Adjust weights to reflect strategy and check whether rankings change. An overall score does not replace mandatory prerequisites.
  6. Pilot and measure before and after. Choose scope, ownership, budget and a suitable evaluation cycle. An 8–12 week pilot may be appropriate if the work cycle allows; this is an implementation suggestion, not a mandatory standard.

A proposed advisory scoring scale

Use a 0–4 scale: 0 = clearly conflicts with objectives or does not meet requirements; 1 = major changes required; 2 = usable after gaps are addressed; 3 = suitable with supporting evidence; 4 = strong fit supported by pilot results or operating data. If information is missing, record “insufficient data”; do not automatically assign zero or produce a recommendation score.

CriterionSuggested weightValidation question
Fit with objectives and competitive approach25%Which two or three strategic priorities does the model support, and what trade-offs does it require?
Fit with value streams and customers20%Who owns the end-to-end outcome? How many handoffs, dependencies and waiting points remain?
Leadership capability and decision rights15%Can managers and units competently exercise the authority delegated to them?
Total cost within budget10%Is there sufficient funding and capacity for transition and operation? Have hidden costs been included?
Quality and risk controls10%Are oversight, business continuity and data protection adequate for the work?
Speed and adaptability10%How quickly can work priorities change while maintaining quality?
Culture and collaboration capability5%Do behaviors, incentives and trust support the proposed structure?
Data readiness and AI collaboration5%Are suitable data, accountable owners and AI output measures available?

Fit score out of 100 = sum of (weight × criterion score / 4)

Weights total 100. This is a proposed decision aid, not a scientifically validated scale. Agree weights before scoring; record evidence and assessors for every score. Do not interpret fit scores as probabilities of success.

Budget comprehensively and measure performance

For the same evaluation period, total costs include transition, management staffing, tools and data, training, coordination, shared services, partners, AI, and estimable losses from poor quality or disruption. Compare options under consistent volume and quality assumptions; separate one-off and recurring costs and avoid double counting.

Use a balanced set of measures: processing and decision time; conforming output per resource; quality and rework; customer outcomes; management or coordination costs; and workforce capability and workload. Establish baselines, targets, data sources and accountable owners. Record changes in demand, staffing or technology when comparing before and after, so improvements are not attributed solely to the new chart.

AI collaboration across all five models

AI may be represented as a coordinating entity with a name, tasks, capabilities and service commitments, such as an “AI Coordination Unit.” Place it within the chosen base structure. Every task still requires a human business owner and an authorized approver. This is a design proposed by the author, not a claim that all 15 example companies use the same AI arrangement.

Base structureProposed AI placement and collaboration
FunctionalA shared AI coordination unit serves functions, each with a business contact. Apply data- and task-specific permissions; avoid making AI another approval layer.
DivisionalShared AI platforms and policies; business units own use cases and results. Avoid duplicate tool purchases and incompatible data standards across units.
MatrixAI consolidates plans, resource loads and conflict alerts for both dimensions. It does not independently resolve authority disputes; retain human ownership and decision logs.
Team-basedEach team uses task-specific AI agents connected to a shared AI coordination unit. Measure conforming outputs and turnaround; do not assess productivity solely by the number of AI-generated tasks.
NetworkAI supports demand, schedule and quality coordination between partners. Share only authorized data, retain a value-chain owner and provide continuity arrangements for AI or partner disruption.

AI entity information fields ID and name; service scope; tasks and outputs; human owner; operating unit; data sources and access rights; action permissions and escalation points; service commitments; costs; acceptance criteria; logs; fallback arrangements.

Scope and use of sources

This advisory comparison draws on five reference diagrams from the book How Business Works (pages 68–77), five foundational websites C1–C5, supplementary sources C6–C7, and 15 company examples E1–E15. Historical percentages in the book are not reused as current data. Model descriptions are synthesized; adoption conditions, solutions, measures and scoring methods are practical proposals that require validation in each business.

  • These five models are reference types within this comparison, not an exhaustive catalog of organizational structures. Centralization and decentralization are design dimensions that can accompany any of the five.
  • There is no universal headcount, budget or management-layer threshold across industries. Cost comparisons describe cost mechanisms, not quotations or standard rates.
  • Each model is illustrated by one representative industry cluster and three companies. This is not a complete list of applicable industries. Businesses within the same industry can use different models.
  • A indicates a direct description by the company or a leader at the date stated in the source. B indicates localized evidence from role descriptions or recruitment. These labels assess support for a claim, not company quality.
  • Older sources provide dated examples, not claims that structures remain unchanged on 20 October 2026. Network examples support the value-chain model, not the entire internal reporting structure.

Sources and supporting evidence

[C1] McKinsey
Getting organizational redesign right
2015 · Accessed 20 October 2026

Design around strategy, diagnose the current state, define roles before people and measure outcomes.

[C2] BCG
Organization Design
Service page, accessed 2026 · Reviewed 20 October 2026

Start with performance gaps; design behaviors, accountabilities and implementation mechanisms together.

[C3] Bain
Who has the D
2006 · Accessed 20 October 2026

RAPID decision roles; reporting lines alone do not establish who decides.

[C4] Deloitte
Operating Model Transformation
Accessed in 2026 · Reviewed 20 October 2026

Operating models encompass work, processes, technology and the people or digital entities performing it.

[C5] Galbraith Management Consultants
Star Model
Accessed in 2026 · Reviewed 20 October 2026

Align strategy, structure, processes, rewards and people.

[C6] Galbraith Management Consultants
Designing Matrix Organizations that Actually Work
Book introduction, 2012 · Accessed 20 October 2026

Matrices require aligned coordination, planning, objectives and rewards.

[C7] Atlassian
Discover the Spotify model
Accessed in 2026 · Reviewed 20 October 2026

Autonomous teams and professional communities; avoid copying labels without the supporting culture.

[E1] Apple
How Apple Is Organized for Innovation
HBR 2020, copy provided by Apple · Accessed 20 October 2026

Functional organization and expert leadership at the time of the article.

[E2] McKinsey and Brian Chesky
The 21st century corporation a conversation with Brian Chesky of Airbnb
2021, describing the 2020 change · Accessed 20 October 2026

A direct CEO interview about Airbnb’s transition to a functional organization in 2020.

[E3] GitLab
No Matrix Organization
Published handbook, accessed 2026 · Reviewed 20 October 2026

Self-described functional management with one formal manager.

[E4] P&G
Corporate Structure
Published structure page, accessed 2026 · Reviewed 20 October 2026

Category-based SBUs, performance accountability and market-support arrangements.

[E5] Unilever
At a glance
Published page, accessed 2026 · Reviewed 20 October 2026

Four category-based business groups on the reviewed page, rather than the older five-group chart.

[E6] Nestlé
2025 Operating segments and information by products restated
23 March 2026, effective 1 January 2026 · Accessed 20 October 2026

Three geographic zones and two globally managed businesses; describes organization as well as segment figures.

[E7] Schneider Electric
Leadership How to create a Great Team
9 June 2023 · Accessed 20 October 2026

An Operations leader describes a matrix within their own area of responsibility.

[E8] Siemens
Head of Lifecycle Digital and Software Smart Infrastructure Buildings
Recruitment posting indexed in 2025 · Accessed 20 October 2026

A role description refers to a global matrix; localized evidence from an indexed copy, not a group-wide chart.

[E9] Ericsson
Head of Marketing and Communications BCSS
Recruitment page, accessed 2026 · Reviewed 20 October 2026

A multi-geography matrix context at BCSS, evidenced within the scope of the role.

[E10] AWS
Amazon Two Pizza Teams
Published page, accessed 2026 · Reviewed 20 October 2026

Cross-functional teams own a service end to end; the source also discusses limits and duplication risks.

[E11] Atlassian
How should you structure your engineering team
28 August 2019 · Accessed 20 October 2026

Leadership describes teams combining design, engineering and product; a time-specific example.

[E12] Spotify Engineering
Tech Migrations the Spotify Way
2020 · Accessed 20 October 2026

Autonomous engineering teams and coordinated shared changes; does not establish that the 2012 chart remains unchanged today.

[E13] NIKE
Form 10 K fiscal 2026
Fiscal year ended 31 May 2026 · Accessed 20 October 2026

Most manufacturing is performed by independent contractors, supporting the value-creation network example.

[E14] adidas
Sourcing and Supply Chain Annual Report 2025
2025 report · Accessed 20 October 2026

Almost all production is outsourced to independent partners alongside logistics coordination.

[E15] PUMA
Strategy business model and value chain Annual Report 2025
2025 report · Accessed 20 October 2026

The brand owner coordinates external manufacturers, suppliers and logistics.

Reference diagrams: Functional, Divisional, Matrix, Team-based and Network structures from the book How Business Works. The illustrations in the comparison are a new set of vector graphics created by Evera.