Task Interdependence¶

Prime #: 425
Origin domain: Organizational & Management Science
Also from: Systems Thinking & Cybernetics, Disaster Management
Aliases: Workflow Interdependence, Task Coupling, Coordination Requirements
Related primes: Delegation of Authority, Formal vs. Informal Structures, Oversight Capacity, Modularity

Core Idea¶

Task Interdependence is the workflow-coupling principle that the completion, quality, or timing of one task depends on inputs, outputs, resources, information, or decisions from other tasks, such that system performance depends not only on individual task performance but on the couplings between them^[1]. The essential commitment is that in any work system with multiple tasks or actors, dependencies create coordination requirements; that James D. Thompson's (1967) three-level typology—pooled (units contribute to a common pool but do not directly exchange work), sequential (A's output is B's input in fixed order), and reciprocal (A and B iteratively exchange inputs and outputs)—with each level requiring progressively more intensive coordination; that the visible, formal interdependence (documented in workflow specifications) often diverges from actual dependencies emerging through practice, creating coordination failures when unnoticed; and that matching coordination mode (standardization, planning, mutual adjustment, integrating roles) to interdependence level is critical for system performance^[1].

How would you explain it like I'm…

When Jobs Need Each Other

Imagine making a sandwich with friends: one spreads the peanut butter, then another spreads the jelly, then a third puts the bread on top. If the first friend is slow, everyone has to wait. That's task interdependence — when one job needs to wait for another before it can happen, so the team has to plan together.

Linked Jobs

Task interdependence is how much one job in a group depends on other jobs. Some tasks barely touch each other — everyone bakes their own cookies for the same sale. Some are in a line — you can't paint the wall until someone builds it. And some go back and forth — like two people writing a story together, trading ideas. The more tightly tasks need each other, the more the team has to coordinate, talk, and adjust.

Workflow Coupling

Task interdependence is the principle that in any workflow with multiple tasks or people, the completion, quality, or timing of one task depends on inputs, outputs, or decisions from others — so overall performance depends not just on each task being done well, but on how they connect. The sociologist James Thompson described three levels, each needing more coordination. *Pooled* interdependence: everyone contributes to a shared whole but works separately (different sales reps adding to a quarterly total). *Sequential*: one person's output feeds the next, in fixed order (an assembly line). *Reciprocal*: people exchange work back and forth (a designer and developer iterating). Coordination tools — standard procedures, schedules, meetings, integrating roles — must match the level of interdependence, or you get bottlenecks, rework, and dropped handoffs.

Task interdependence is the workflow-coupling principle that the completion, quality, or timing of one task depends on inputs, outputs, resources, information, or decisions from other tasks, so that system performance depends not only on individual task quality but on the couplings between tasks. James D. Thompson's (1967) three-level typology is canonical: pooled interdependence (units contribute to a common pool but do not directly exchange work), sequential interdependence (A's output is B's input in fixed order), and reciprocal interdependence (A and B iteratively exchange inputs and outputs). Each level requires progressively more intensive coordination mechanisms, scaling from standardization, to planning, to mutual adjustment supported by integrating roles. A frequent source of coordination failure is divergence between the formal interdependence documented in workflow specifications and the actual dependencies that emerge in practice, leaving real reciprocal coupling unsupported by the channels needed for iteration.

Structural Signature¶

The interdependence typology level (pooled, sequential, reciprocal, or team) characterizing the coordination intensity and required coordination mode ^[1]
The directional structure of dependencies (unidirectional flow as in sequential versus bidirectional iterative exchange as in reciprocal) ^[1]
The resource basis for dependencies (information dependency, physical artifact dependency, approval/decision dependency, shared-resource dependency, skill-complementarity dependency) ^[2]
The tightness of coupling (tight coupling where delays propagate immediately versus loose coupling where buffers absorb variation) ^[3]
The density of interdependence (how many other tasks each task connects to; sparse versus dense networks) ^[4]
The visibility gap between formal interdependence (documented in specifications) and actual interdependence (as revealed through practice and coordination) ^[5]

What It Is Not¶

Not just coordination. Coordination is the management response to interdependence; interdependence is the underlying structural property. A task-interdependence problem cannot be solved by "better coordination" alone if the fundamental coupling is not understood or aligned.
Not the same as task complexity. A complex task done in isolation is not interdependent. A simple task requiring inputs from three other departments is highly interdependent. Interdependence is relational, not intrinsic.
Not equivalent to communication needs. Communication supports coordination but does not eliminate interdependence. Two tasks might communicate frequently yet remain loosely coupled; two others might communicate rarely yet be tightly coupled at critical points.
Not identical to schedule dependencies. Scheduling (Gantt charts, PERT/CPM) models some temporal dependencies, but interdependence includes quality coupling (one task's output quality affects another's success), resource coupling, and information coupling that scheduling alone does not capture.
Not a consequence of poor design alone. Some interdependence is inherent to the work (a surgeon depends on radiology scans before operating). Other interdependence emerges from how organizations structure tasks. Recognizing which is which is critical for intervention.
Common misclassification: Treating all high-communication work as "properly coordinated," when the underlying interdependence structure may require different coordination mechanisms than are in place.

Broad Use¶

Task Interdependence appears in organizational workflow design (assembly lines exhibiting tight sequential interdependence; multiservice organizations with dense cross-departmental interdependence), in software engineering (code-level coupling; API dependencies; build-system DAGs; microservice synchronization; team-topologies informed by interdependence patterns), in project management (PERT/CPM networks modeling task dependencies; critical-path analysis; risk analysis of delay propagation), in healthcare operations (operating-room teams coordinating in real time; clinic workflows with patient-flow interdependence; cross-department patient progression), in supply-chain management (sequential supplier dependencies; inventory-buffered versus just-in-time coupling), in government and public administration (interagency coordination requirements; multi-jurisdictional operations), in scientific collaboration (multi-lab research dependencies; instrumentation-sharing interdependence), and in emergency response (incident management with dynamic task-interdependence patterns changing as incident evolves).

Clarity¶

Task-interdependence framing clarifies why "siloed" task management fails: it reveals the coupling structure that makes tasks interdependent. Without the frame, managers blame poor communication or uncooperative behavior when the underlying issue is that the interdependence structure is not explicitly recognized or that coordination mechanisms are mismatched to the interdependence level. With the frame, diagnosis becomes precise: identify the actual dependencies, classify them by Thompson's typology, match coordination mechanisms to the level, and invest coordination capacity accordingly.

Manages Complexity¶

Task-interdependence analysis factors work-system complexity into explicit dependency patterns (pooled, sequential, reciprocal, team) and associated coordination requirements. Rather than treating all work as similarly coordinated, this factoring enables targeted intervention: pooled tasks need mainly standardization; sequential tasks need scheduling and planning; reciprocal tasks need intensive mutual adjustment and integrating roles. This matching of coordination mode to interdependence level is more efficient than applying uniform coordination overhead to all work.

Abstract Reasoning¶

Task-interdependence reasoning proceeds by asking[^lawrence-lorsch-1967]:

Lawrence, P. R., & Lorsch, J. W. (1967). Organization and Environment: Managing Differentiation and Integration. Harvard Business School Press. [^conway-1968]: Conway, M. E. (1968). How do committees invent? Datamation, 14(4), 28–31. Origin of "Conway's Law": establishes a homomorphism between an organization's communication structure and the structure of the systems it designs, explaining why organizational and software hierarchies tend to mirror one another.

Relationships to Other Primes¶

Parents (2) — more general patterns this builds on

Task Interdependence is a kind of Dependency

Task interdependence is a kind of dependency specialized to work-system tasks: the directed reliance is between activities whose completion, quality, or timing requires inputs, outputs, resources, or decisions from other tasks. It inherits dependency's general commitment that one element relies on another being present, prior, compatible, or supplied, and supplies the specific case where the elements are tasks and the typology of reliance — pooled, sequential, reciprocal — sets coordination requirements proportional to the coupling intensity that the underlying dependency relation creates.
Task Interdependence is a decomposition of Network

Task interdependence is the workflow-particularized form network takes: the entities are tasks and the connections are the dependencies through which one task's outputs, resources, or decisions feed another. Where network names a set of entities with pairwise connections studied at the level of connection pattern generally, task interdependence fixes the node type (tasks), the edge type (input-output, resource, information dependencies), and the analytic focus (Thompson's pooled-sequential-reciprocal typology) — a particular shape of network structure in work systems.

Children (2) — more specific cases that build on this

Concurrent, Cross-Functional Collaboration presupposes Task Interdependence

Concurrent cross-functional collaboration is justified only when the tasks being performed are reciprocally interdependent — when design, manufacturing, and operations decisions iteratively shape one another rather than feeding forward in a fixed sequence. Without task interdependence's machinery of workflow coupling, the simultaneous engagement of multiple specialists would be wasteful: tasks that are merely pooled or sequential need only sequential handoff. The reciprocal interdependence supplies the structural condition that makes concurrent engagement the efficient coordination form.
Coordination presupposes Task Interdependence

Coordination's whole rationale is to align actors whose tasks depend on one another — to manage the couplings through which one task's output is another's input, or both compete for shared resources. Without task interdependence's machinery of workflow coupling, the actors would be performing independent tasks with no need for active alignment, and the coordination infrastructure would have nothing to coordinate. Interdependence supplies the structural condition — coupling between tasks — that creates the requirement coordination addresses.

Path to root: Task Interdependence → Dependency

Solution Archetypes¶

Solution archetypes in the catalog that build on this prime — directly (this prime is a source ingredient) or as a related prime.

Built directly on this prime (3)

Also a related prime in 18 archetypes

▸ Show 8 more

References¶

[1] Thompson, J. D. (1967). Organizations in Action: Social Science Bases of Administrative Theory. McGraw-Hill. ↩

[2] Galbraith, J. R. (1973). Designing Complex Organizations. Addison-Wesley, Reading, MA. Develops 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. ↩

[3] Parnas, D. L. (1972). "On the criteria to be used in decomposing systems into modules." Communications of the ACM, 15(12), 1053–1058. ↩

[4] Conway, M. E. (1968). "How do committees invent?" Datamation, 14(4), 28–31. ↩

[5] Mintzberg, H. (1979). The Structuring of Organizations: A Synthesis of the Research. Prentice-Hall, Englewood Cliffs, NJ. Synthesizes organizational-design research into a typology of five configurations (simple structure, machine bureaucracy, professional bureaucracy, divisionalized form, adhocracy), each characterized by a distinct combination of partitioning (horizontal and vertical specialization) and coordination mechanism (mutual adjustment, direct supervision, standardization of work processes, outputs, or skills). ↩

[6] Van de Ven, A. H., Delbecq, A. L., & Koenig, R. (1976). "Determinants of coordination modes within organizations." American Sociological Review, 41(2), 322–338.

[7] Lawrence, P. R., & Lorsch, J. W. (1967). Organization and Environment: Managing Differentiation and Integration. Harvard University Press.

[8] Goldratt, Eliyahu M., and Jeff Cox. The Goal: A Process of Ongoing Improvement. Great Barrington, MA: North River Press, 1984 (4^th anniversary ed., 2014). Theory-of-Constraints methodology consolidated in Goldratt, What Is This Thing Called Theory of Constraints and How Should It Be Implemented? (North River Press, 1990). Methodological consolidation: Dettmer, Goldratt's Theory of Constraints (ASQ Quality Press, 1997).

[9] 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.

[10] Baldwin, C. Y., & Clark, K. B. (2000). Design Rules: The Power of Modularity (Vol. 1). MIT Press.

[11] Simon, H. A. (1962). "The architecture of complexity." Proceedings of the American Philosophical Society, 106(6), 467–482.

[12] Ulrich, K. T. (1995). "The role of product architecture in the manufacturing firm." Research Policy, 24(3), 419–440.

[13] Sánchez, R., & Mahoney, J. T. (1996). "Modularity, flexibility, and knowledge management in product and organization design." Strategic Management Journal, 17(S2), 63–76.

[14] MacCormack, A., Baldwin, C., & Rusnak, J. (2012). "Exploring the duality between product and organizational architecture: A test of the 'mirroring hypothesis'." Research Policy, 41(8), 1309–1324.

[15] Meyer, B. (2014). "Agile!: The Good, the Hype, and the Ugly." Springer.

[16] Gamma, E., Helm, R., Johnson, R., & Vlissides, J. (1994). Design Patterns: Elements of Reusable Object-Oriented Software. Addison-Wesley.

[17] McIlroy, M. D. (1968). "Mass produced software components." In Software Engineering: Report of a Conference Sponsored by the NATO Science Committee (pp. 138–155). NATO Science Committee.

[18] Sommerville, I. (2010). Software Engineering (9^th ed.). Addison-Wesley.

Neighborhood in Abstraction Space¶

Task Interdependence sits in a moderately populated region (45^th percentile for distinctiveness): it has near-neighbors but no dense thicket of synonyms.

Family — Biological Scaling & Coupling (12 primes)

Nearest neighbors

Computed from structural-signature embeddings · 2026-05-29