Designing Complex Organizations

Galbraith, J. R. (1973). Designing Complex Organizations. Addison-Wesley.

Type

Book

Intellectual base

Textbook

Year

1973

Link

https://archive.org/details/designingcomplex00galb

Cited from

economics_finance, mathematics, organizational_management, political_science

Cited by

10 citations across 10 artifacts.

Each citation links to the sentence it supports in the citing article.

Primes

• Closure
  • A team is closed under decision authority with respect to a designated class of decisions when the team can resolve any decision in that class without external escalation; jurisdictional closure is the analogous property for legal forums (a court is closed with respect to a class of cases when it can resolve any such case within its own procedures); and the design of organisational charters typically specifies the closure profile of each unit (which decisions are within the unit's authority, which require escalation), a discipline Galbraith (1973) develops in his canonical treatment of designing decision-authority structures.

    This sourceInformation-processing view of organizational design; develops self-contained tasks and the location of decision-making authority so that units can resolve decisions without escalation.

• Coordination
  • When does authority transfer?), a structural diagnosis Galbraith (1973) elaborated in his information-processing view of organizational design.

    This sourceDevelops the information-processing view of organizational design: task uncertainty raises the volume of information processed during execution, and the chosen partitioning determines how much coordination load the integration mechanism carries; catalogues design moves (slack resources, self-contained tasks, vertical information systems, lateral relations).

• Decomposition
  • Critical practice requires explicit reflection on what the chosen axis reveals and what it obscures, a trade-off Galbraith (1973) framed as the central design decision in his contingency theory of organizational structure.
• Delegation of Authority

  • This sourceDevelops the information-processing view of organizational design: task uncertainty raises information that must be processed during execution, and the partitioning determines coordination load; catalogues design moves (slack resources, self-contained tasks, vertical information systems, lateral relations).

• Division of Labor
  • Organizational design: Functional vs. matrix vs. divisional organization as alternative partitioning schemes; vertical specialization (hierarchy levels handling decisions of different scope) vs. horizontal specialization (functional departments handling different activities); Galbraith (1973) developing the organizational-design framework that treats coordination requirements as a direct function of partitioning choices, with the information-processing capacity of the integration mechanism setting an upper bound on how fine a partition can be productive.
• Layered Coordination & Oversight
  • The downward flow of strategy, policy, resources, priorities, and constraints from higher to lower tiers

    This sourceDevelops the information-processing view of organizational design: task uncertainty raises the volume of information that must be processed during execution, and the chosen partitioning determines how much coordination load the integration mechanism must carry. Catalogues design moves (slack resources, self-contained tasks, vertical information systems, lateral relations) that adjust the partition–coordination balance as uncertainty rises.

• Local Autonomy & Tiered Escalation
  • When local systems lack authority, information, or tools, escalation is not failure—it is the designed pathway for resource mobilization, what Galbraith (1973) formalizes as referral upward in his information-processing theory of organizations.

    This sourceDevelops the information-processing view of organizational design: task uncertainty raises the volume of information that must be processed during execution, and the chosen partitioning determines how much coordination load the integration mechanism must carry. Catalogues design moves (slack resources, self-contained tasks, vertical information systems, lateral relations) that adjust the partition–coordination balance as uncertainty rises.

• Oversight Capacity
  • The coordination load metric measuring communication frequency, decision density, or synchronization overhead associated with each direct sub-unit

    This sourceDevelops the information-processing view of organizational design: task uncertainty raises the volume of information that must be processed during execution, and the chosen partitioning determines how much coordination load the integration mechanism must carry. Catalogues design moves (slack resources, self-contained tasks, vertical information systems, lateral relations) that adjust the partition–coordination balance as uncertainty rises.

• Task Interdependence
  • The resource basis for dependencies (information dependency, physical artifact dependency, approval/decision dependency, shared-resource dependency, skill-complementarity dependency)

    This sourceDevelops the information-processing view of organizational design: task uncertainty raises the volume of information that must be processed during execution, and the chosen partitioning determines how much coordination load the integration mechanism must carry. Catalogues design moves (slack resources, self-contained tasks, vertical information systems, lateral relations) that adjust the partition–coordination balance as uncertainty rises.

Mechanisms

• Escalation to Authority
  • Chronic escalation trains teams to stop resolving anything themselves, floods senior queues, and can turn a solvable peer negotiation into a slow wait for a busy executive — sometimes just relocating the deadlock one level up rather than breaking it.

    This sourceExplains that referring too many exceptions upward can overload hierarchical decision capacity and delay responses.

Verification

Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.

Does it back the claim? Not recorded. Neither this nor any other of the 10 citations of this work carries a recorded support check.

Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.

See how references were verified.

Links previously used in the corpus

Before the registry existed this work was also linked 1 other way.

• https://books.google.com/books/about/Designing_Complex_Organizations.html?id=FUe3AAAAIAAJ ×1

Registry ID ref:4d79ee050f35 · see in the full table