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 Abstractions¶

Current abstraction Task Interdependence Prime

Parents (2) — more general patterns this builds on

Task Interdependence is a kind of Dependency Prime

Task interdependence is a specialization of dependency in which the directed reliance is between coupled tasks in a work system.
Task Interdependence is a decomposition of Network Prime

Task interdependence is the specific shape network takes when the nodes are tasks and the edges are workflow couplings of inputs, outputs, and resources.

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

Concurrent, Cross-Functional Collaboration Prime presupposes Task Interdependence

Concurrent cross-functional collaboration presupposes task interdependence because its simultaneous engagement is justified only when functional tasks have reciprocal couplings.
Coordination Prime presupposes Task Interdependence

Coordination presupposes task interdependence because the active alignment of actors is only required when their tasks are coupled through inputs, outputs, or shared resources.

Hierarchy paths (2) — routes to 2 parentless roots

Task Interdependence → Dependency

Show alternative path (1)

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 (8)

Concurrent Cross-Functional Integration: Integrate specialized perspectives in parallel through shared artifacts, live interfaces, synchronized decisions, and continuous recombination so conflicts appear while they are still cheap to resolve.
▸ Mechanisms (10)
- Big-Room Planning or Concurrent Set-Based Workshop
- Concurrent Engineering Workcell
- Cross-Functional Design Review
- Cross-Functional Swarm on Integration Constraint
- Dependency and Change Notification Board
- Integrated Product or Service Team
- Integrated Readiness and Release Review
- Integration Build or End-to-End Increment
- Interface Control Document and Contract Test
- Shared System Model or Digital Thread
Contribution Visibility Design: Make individual contributions visible enough that group work does not hide effort, free-riding, or overload.
▸ Mechanisms (9)
- Contribution Review Meeting
- Contribution Tracking Board
- Credit Taxonomy or Authorship Matrix
- Individual Deliverable Contract
- Peer Evaluation Process
- Shared Task Ownership Protocol
- Team Work Board
- Work Log or Activity Trace
- Workload Heatmap
Distributed Coordination Architecture: Design the outcome, authority, dependencies, interfaces, shared state, timing, commitments, exceptions, and feedback that let independently controlled actors produce a coherent collective result.
▸ Mechanisms (13)
- After-Action Coordination Review — Closes a coordination episode by extracting transferable lessons and transferring residual obligations, so the architecture improves and no commitment vanishes when the coalition disbands.
- Commitment and Dependency Register — Turns promises and the dependencies they create into stateful, addressable objects with owners, dependents, status, and closure evidence — durable coordination memory rather than scattered recollection.
- Coordination Decision Rights and Autonomy Matrix — Maps, for each class of coordinated decision, who may commit, decide, execute, veto, stop, and review — drawing the line between legitimate local autonomy and choices that require joint control.
- Coordination Health Review — A standing review that watches interface- and outcome-level health signals and re-tunes the coordination architecture before degradation hardens into failure.
- Dependency and Interaction Map — Charts the actual interdependencies and handoffs between actors — where one party's state changes another's feasible action — so coordination targets real coupling, not org-chart lines.
- Distributed Planning and Reconciliation Session — A working session where independently-planning actors reconcile competing claims on scarce shared resources into a jointly feasible set of commitments.
- Event-Driven Coordination Channel — Routes meaningful changes and exceptions to exactly the actors whose decisions depend on them, so coordination rides targeted signals instead of broadcast noise or constant shared-state polling.
- Exception and Escalation Protocol — The pre-agreed path for when normal coordination fails — declare the exception, contain harm, hand time-limited interim authority to a named role, route the decision, then review and close.
- Interface Control Document or Service Contract — Freezes one recurring exchange between two parties into an explicit contract — objects, semantics, guarantees, acknowledgment, and versioned change rules — so neither side has to renegotiate it.
- Joint Operating Agreement — Ratifies the shared outcome, the chosen coordination mode, and the incentive and cost-sharing terms into one versioned, authority-bearing agreement every party signs.
- Liaison and Integrator Role — A standing human role that spans a boundary — translating between parties, brokering competing claims on shared resources, and keeping the working relationship intact enough to keep coordinating.
- Shared Coordination Board — A single shared surface where every actor reads the same live picture — outcome, state, commitments, dependencies, capacity, exceptions — each field owned, dated, and confidence-tagged.
- Synchronization Checkpoint — A dependency-triggered readiness gate: before a coupled, hard-to-reverse transition, every required party confirms it is ready, and the gate can release, hold, or send everyone back to replan.
Integrated Work Partitioning: Make a joint activity scalable and learnable by dividing it into specialized work units, assigning them to distinct performers, and deliberately reconnecting their outputs.
▸ Mechanisms (10)
- Cross-Functional Workflow Board
- Dependency Matrix
- Handoff Protocol
- Integration Review
- Job Rotation or Cross-Training Program
- RACI or Responsibility Matrix
- Service-Level or Internal Service Agreement
- Swimlane Workflow Diagram
- Team or Role Charter
- Work Breakdown Structure
Responsibility Assignment for Action: Assign clear responsibility when group presence would otherwise diffuse action.
▸ Mechanisms (10)
- Emergency Role Assignment
- Escalation Protocol — Defines the threshold at which an agent's ordinary discretion runs out and the decision must be routed up to a higher or different authority.
- Explicit Task Assignment
- Incident Commander Role
- On-Call Ownership
- Public Commitment Board
- RACI-Like Ownership Matrix
- Runbook With Named Owner
- Shift Handoff Check
- Single-Threaded Owner
Shared-Benefit Contribution Governance: Turn willingness to help into reliable shared-benefit production by governing who contributes what, why, when, how it is seen, and how burden and benefit stay legitimate.
▸ Mechanisms (12)
- Collective Threshold Pledge — Makes each person's contribution binding only if enough others also commit — so no one has to move first into an empty room, and the effort either reaches critical mass or costs nobody.
- Contribution Board or Dashboard — Puts each contributor's effort on a shared display, so recognition is earned in the open and lopsided load or quiet free-riding becomes a visible fact before it festers.
- Cooperation Retrospective — A periodic, blameless look back at how the cooperation itself went — who carried what, who got left out, what strained — that adjusts the arrangement before the next cycle.
- Cooperative Contribution Charter — A written founding agreement that names the shared benefit, fixes who the contributors are, and states the fair-share rule everyone signs up to — the reference every later contribution and dispute is measured against.
- Graduated Free-Rider Response — An escalation ladder for under-contribution that opens with a gentle, private nudge and ratchets up only as it must — correcting free-riding without torching goodwill or over-punishing an honest lapse.
- Mutual Aid Roster — A living directory of who can help with what — standing offers, named backups, and the pathways to reach them — so aid is found by lookup instead of improvised in the moment.
- Participatory Budget or Resource Pool — Members pool their contributions into a common reserve and then decide together how it is spent — coupling a shared pot with participatory allocation so the resource is funded and governed by the same people.
- Peer Commitment Round — A recurring round in which each member, in turn, states aloud what they will contribute before the next cycle — turning private intention into a public, peer-witnessed commitment.
- Reciprocity Check-In — A recurring, low-stakes conversation that surfaces imbalance, overload, and changed capacity early — so strain is repaired before it hardens into resentment or quiet withdrawal.
- Rotating Stewardship Schedule — Rotates a single burdensome shared duty through the membership on a fixed schedule, so everyone takes a turn in the hot seat and no one is stuck there — with time off the rotation as built-in, protected rest.
- Time Bank or Service Credit System — Converts an hour of unlike help into a common credit anyone can earn now and spend later — turning scattered one-off favors into durable, accounted reciprocity.
- Working Group or Pod Structure — Splits a large body of contributors into small, semi-autonomous units — each owning a slice of the work and nesting inside the whole — so cooperation stays legible and accountable as numbers grow.
Specialization Boundary and Reintegration Design: Improve efficiency by narrowing roles or niches only where the gains exceed the coordination, brittleness, learning, and reintegration costs.
▸ Mechanisms (11)
- bus_factor_review
- coordination_cost_accounting
- dependency_heatmap
- handoff_contract_template
- integrator_role_assignment
- over_specialization_audit
- role_niche_charter
- role_recomposition_trigger_review
- rotation_and_cross_training_schedule
- specialist_generalist_portfolio_review
- specialization_boundary_workshop
Task Interdependence Mapping: Map how tasks depend on one another so coordination, handoffs, and communication match the actual workflow.
▸ Mechanisms (10)
- Coordination Meeting Cadence
- Critical Path Analysis
- Cross-Functional Workflow Mapping
- Dependency Mapping Session
- Dependency Matrix
- Escalation Review
- Handoff Protocol
- RACI Matrix
- Shared Workflow Board
- Workflow Diagram

Also a related prime in 27 archetypes

Alignment Governance and Dispute Resolution: Stabilize multi-actor systems by giving misalignments a legitimate forum, clear authority boundaries, and escalation/resolution paths before conflicts cascade.
Cadence Design: Establish a recurring rhythm for action, review, communication, or maintenance so important work happens reliably without constant re-decision.
Complexity Scaling Assessment: Assess how effort, cost, time, memory, or coordination burden grows as input size or system scale increases.
Composability Testing and Validation: Test whether components that work alone still work together, and use the results to define safe recombination boundaries.
Concurrency Control: Coordinate simultaneous processes so they can proceed in parallel without corrupting shared state, over-claiming shared resources, or blocking one another indefinitely.
Coordination and Synchronization Across Reentry Phases: Bring separated parts back together in the right order, at the right tempo, with shared state visibility and the ability to pause when reentry creates overload or unsafe coupling.
Coordination Scaffold Load Control: Keep the support machinery for coordination from becoming a second workload larger than the work it exists to coordinate.
Coupling Latency and Time-Delay Effects: Treat delay in coupled interactions as a design variable, not as background noise.
Cycle Phase Alignment: Align the phases of interacting cycles so handoffs, resources, and decisions arrive when they are usable.
Deadlock Prevention: Structure resource acquisition, authority, or sequencing so circular blocking cannot arise.

▸ Show 17 more

Dependency Exposure: Reveal hidden dependencies so risks, obligations, failure paths, and coordination needs become visible before they cause failure.
Goal Congruence Alignment: Align local objectives, metrics, and incentives with system-level goals so units do not optimize against the whole.
Group Cohesion Calibration: Build enough shared identity, trust, mutual obligation, and coordination rhythm for members to act as a group while preserving voice, permeability, and ethical boundaries.
Head-of-Line Blocking Relief: Prevent one blocked or slow item at the front of a queue from delaying everything behind it.
Holonic Autonomy Nesting: Design nested units as autonomous local wholes and dependent parts at the same time, with explicit boundaries, interfaces, escalation paths, and cross-level invariants.
Iterative Reciprocity and Repeated Interaction: Make cooperation durable by ensuring actors meet again, remember what each contributed, and condition future help, trust, access, or obligation on prior contribution behavior.
Knowledge Map Navigation: Create and use a map of a knowledge domain so people can locate concepts, gaps, dependencies, and learning paths.
Necessary-Condition Closure Design: Make all non-substitutable success conditions explicit, verify each one, and treat the weakest missing condition as the blocker rather than averaging it away.
Net-Additive Contribution Intake: Accept, reshape, redirect, defer, or decline well-intended contributions according to their full net value, available sponsorship, and effect on protected primary work.
Organization–Artifact Topology Alignment: When the structure of a produced artifact is likely to mirror the collective that built it, map both topologies and redesign either the artifact boundaries, the team boundaries, or the communication paths instead of letting the mirror form accidentally.
Pivotal Participation Leverage Mapping: Map who or what becomes decisive because the collective outcome fails without it, then manage that pivotal leverage without confusing nominal size with real marginal contribution.
Role-Expectation Conflict Reconciliation: Make incompatible role expectations visible and govern which duty controls, what must be redesigned, and when a person needs recusal, substitution, support, sequencing, or release.
Schema Conflict Resolution: Resolve conflicts when different schemas classify or interpret the same reality differently.
Shared Mental Model Alignment: Align team members' understanding of the system, roles, risks, and plan so joint action becomes reliable.
Shared-Input Variety Platform Design: Produce varied outputs more cheaply by sharing the inputs they can truly hold in common while protecting the differences that still matter.
Symmetry Breaking for Differentiation: Deliberately break equivalence among similar options so roles, structure, or direction can emerge.
Synergistic Combination Design: Combine elements so their interaction produces more value than isolated implementation.

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 among the more crowded primes in the catalog (39^th percentile for distinctiveness): several abstractions describe nearly the same structure, so a description that fits it will tend to fit its neighbors too — transporting it usually means disambiguating within this family rather than landing on it exactly.

Family — Capacity Limits & Attention (19 primes)

Nearest neighbors

Coupling — 0.73
Attention — 0.73
Concurrency — 0.72
Oversight Capacity — 0.71
Cognitive Load — 0.71

Computed from structural-signature embeddings · 2026-07-26