Organigraph¶

A graphic map of an organization's work relationships and flows rather than only its reporting hierarchy.

Version: v1 · 2026-09-28 · History
Domain-specific #: 11145
Domain group: Professional & Organizational Practice
Origin domain: Organizational & Management Science
Subdomains: Organizational Design, Organizational Mapping → Organizational & Management Science

Core Idea¶

An organigraph changes the object of an organizational diagram. Instead of using rank and reporting as the main axes, it represents how work passes through functions, teams and external relationships. Mintzberg and Van der Heyden describe sets, chains, hubs and webs as useful connection forms. A real organization may combine these forms, and the map is selective rather than a complete causal model.

Their petrochemical-company example maps activity flows among exploration, refining, trading and retail. Their Electrocomponents case shows a distinct real managerial application: mapping business-to-business relationships suggested strategic possibilities. The article reports those interpretations and choices, not a controlled test that organigraphs improve performance. The abstraction helps managers notice work structure that a hierarchy chart can obscure while preserving that evidence limit.

Structural Signature¶

Sig role-phrases:

Organization as target — The real work system, not merely formal ranks, is what the map claims to describe. It is constitutive. Counterfactual: A generic network picture without a specific organization's work has no organigraph target.
Graphic medium — A spatial diagram holds selected activities and relationships for inspection. It is constitutive. Counterfactual: A prose management slogan alone is not an organigraph.
Activity units — Functions, people or groups appear by their actual contribution to work. It is constitutive. Counterfactual: Names and job titles alone reproduce an org chart rather than the work map.
Connection mapping — Flows or coordination relations are drawn as sets, chains, hubs or webs where useful. It is constitutive. Counterfactual: Unrelated boxes with no working relation do not reveal organizing structure.
Faithfulness boundary — The map selects work relations and omits details, so it must not be mistaken for a complete operational record. It is central. Counterfactual: One stylized figure cannot license every causal or performance inference.
Managerial interpretation — Viewers can compare the depicted work to strategic questions or redesign possibilities. It is central. Counterfactual: A diagram alone does not prove a particular business strategy is correct.

What It Is Not¶

Not an org chart with new styling. Reporting rank alone omits work flow.
Not one network topology. Sets, chains, hubs and webs can coexist.
Not a complete process model. A diagram selects relations relevant to a question.
Not proof of strategic success. A useful interpretation does not establish causal impact.
Closest near-miss. A formal organization chart can include connecting lines, but if those lines mean only who reports to whom while activities and work flows remain absent, it misses the organigraph's subject.

Scope of Application¶

Organizational diagnosis. Find work connections hidden by reporting charts.
Strategy discussion. Compare where customer value and capabilities actually reside.
Change design. Explore how units or external partners might connect differently.
Communication. Give teams a common map of important interdependencies.

Clarity¶

An organigraph maps what an organization does and how its work connects. The petrochemical-company diagram is a source-authored construction; Electrocomponents is a documented managerial use. It can include sets, chains, hubs and webs. A chart that shows only bosses and subordinates, even with many arrows, does not satisfy the work-relationship mapping test.

Manages Complexity¶

Actual organizations mix lateral coordination, sequential flows, focal hubs and loose sets, often with partners outside the formal hierarchy. A map compresses these relations but must choose what to leave out. Comparing it with an org chart reveals different questions; neither diagram alone demonstrates that a strategic decision will work.

Abstract Reasoning¶

Identify the organization and the work question.
List relevant activities and actors, including external partners.
Trace actual material, information or coordination relationships.
Choose set, chain, hub and web forms only where they fit.
State what the diagram omits and compare with formal authority.
Use the map to pose strategic hypotheses, then seek independent decision evidence.

Knowledge Transfer¶

The target–medium–mapping relation transfers to process maps and network visualizations, but an organigraph specifically maps organizational work rather than any graph. Using the same shapes for a biological network or hierarchy without activities is only analogy.

Examples¶

Canonical¶

The authors' petrochemical-company figure maps exploration and production, refining, trading, chemicals, wholesale, gas retail and outside vendors as interacting business activities. Its chains, hubs and cross-links make the route of work visible in a way a managerial reporting chart would not. It is a published source-authored diagrammatic construction; the article does not identify every department or establish operational performance from the figure.

Mapped back: Organization as target → depicted petrochemical company; Graphic medium → authors' organigraph exhibit; Activity units → exploration, refining, trading and retail functions; Connection mapping → flows and cross-links among functions and vendors; Faithfulness boundary → selected operational relationships, not every work detail; Managerial interpretation → view interdependence beyond reporting lines.

Applied / In Practice¶

Mintzberg and Van der Heyden report that an organigraph made with British distributor Electrocomponents brought its business-to-business relationships into focus. Managers used that interpretation when considering expansion in Asia and increased Internet business. This is an attested company use of the mapping method, not experimental evidence that the diagram by itself caused those strategic outcomes.

Mapped back: Organization as target → Electrocomponents' distribution business; Graphic medium → authors' company-specific organigraph; Activity units → distribution and customer-facing work; Connection mapping → business-to-business relationship structure; Faithfulness boundary → strategic view, not all operations or causal proof; Managerial interpretation → Asia and Internet expansion possibilities.

Structural Tensions¶

T1 — Work Fidelity versus Diagram Legibility. Showing every interaction overwhelms a map, while too few conceal the work system.

Diagnostic: Which connections matter for the strategic question?

T2 — Formal Authority versus Actual Coordination. Reporting accountability matters, but an authority chart may hide lateral flows and hubs.

Diagnostic: Which view answers the present organizational question?

T3 — Diagnosis versus Causal Attribution. A map can reveal possibilities without proving that redrawing it caused later business performance.

Diagnostic: What decision evidence exists beyond the picture?

Structural–Framed Character¶

The approved DAG parent is Representation: an organigraph selectively maps an organization's actual work into a visual medium, preserving chosen activities and connection relations while omitting detail. It is not simply an org chart or a claim that reporting rank is irrelevant.

Evaluative weight: It may reveal coordination problems, but diagram quality depends on fidelity and use. Human-practice-bound: High, because analysts select work boundaries, relation types, and viewing purpose. Institutional origin: Management research named the form; no particular firm or diagram software is necessary. Vocabulary travels: Sets, chains, hubs, and webs may describe other targets, but this node maps organizational work. Import versus recognize: One recognizes an organigraph by target–medium mapping of real activities and connections; a generic network drawing imports only shapes.

Its character: A purpose-built organizational representation with portable mapping logic and a work-flow target.

Structural Core vs. Domain Accent¶

Skeletal core. A target system is represented by a selective relation-preserving map. Domain-bound accent. Organizational activities, workflows, teams, partners and managerial interpretation make the medium an organigraph. Transfer boundary. A generic network drawing without a real organization's work and faithful connection mapping is not this subtype.

This entry is a kind of Representation.

Parent: representation. Target, diagram medium, relation mapping, selective faithfulness and operational interpretation satisfy the prime signature.
Neighbor: organizational structure. The work arrangement is the target; the organigraph is a particular representational map of it.

Relationships to Other Abstractions¶

Current abstraction Organigraph Domain-specific

Parents (1) — more general patterns this builds on

Organigraph is a kind of Representation Prime

Organigraph is a strict kind of Representation: A graphic map of an organization's work relationships and flows rather than only its reporting hierarchy.

Hierarchy path (1) — routes to 1 parentless root

Organigraph → Representation → Abstraction

Neighborhood in Abstraction Space¶

Organigraph sits in a crowded region of the domain-specific corpus (34^th percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.

Family — Organizational Patterns & Management Concepts (29 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-08

Not to Be Confused With¶

Organizational chart. Tell: Emphasizes rank and reporting rather than actual work connections.
Process flowchart. Tell: May trace one process without mapping the broader organization's mixed relation forms.
Social network diagram. Tell: May map interpersonal ties rather than organizational functions and work.
Business model canvas. Tell: Records value propositions and resources with a different structured medium.

References¶

Mintzberg and Van der Heyden, “Organigraphs: Drawing How Companies Really Work,” Harvard Business Review (1999) — original account, diagram vocabulary and company case.
Authors' article PDF — petrochemical organigraph exhibit and Electrocomponents discussion.