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 highlights how tasks within a group or system rely on each other's outputs, creating webs of dependencies that shape communication, coordination, and workflow sequencing.

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.

Broad Use

• Assembly Lines: One station's output becomes the next station's input; a delay in one spot halts the entire line.

• Software Projects: Frontend tasks depend on API readiness, while QA depends on stable builds.

• Event Planning: Caterers can't finalize menus until a venue is confirmed, marketing can't finalize ads until sponsors commit.

• Healthcare Teams: A surgeon depends on radiology scans, anesthesia prep, and nurse scheduling to proceed effectively.

Clarity

Reveals that tasks are rarely siloed; their interconnections can create bottlenecks if not managed or scheduled carefully.

Manages Complexity

Mapping and controlling task linkages (e.g., via Gantt charts or dependency trackers) helps avoid cascading delays or conflicts, enabling smoother collaboration.

Abstract Reasoning

Demonstrates that in complex systems, the structure of who needs what from whom—and in which order—fundamentally shapes efficiency and outcomes.

Knowledge Transfer

• Sociotechnical Systems: Even if each domain is well-designed, ignoring cross-domain interdependencies can cause friction at integration points.

• Multi-Agency Projects: Government or NGO initiatives often fail if interdependencies among departments aren't spelled out.

Example

A film production is riddled with task interdependencies—costume design depends on casting decisions, set design depends on script changes, sound editing depends on final scene edits, etc.

Relationships to Other Primes

Parents (2) — more general patterns this builds on

• Task Interdependence is a kind of Dependency — 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 — 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 presupposes Task Interdependence — Concurrent cross-functional collaboration presupposes task interdependence because its simultaneous engagement is justified only when functional tasks have reciprocal couplings.
• Coordination 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.

Path to root: Task Interdependence → Dependency

Not to Be Confused With

• Task Interdependence is not Concurrent, Cross-Functional Collaboration because Task Interdependence is the workflow-coupling where completion of one task depends on another; Concurrent, Cross-Functional Collaboration is an organizing principle for parallel work across functions—interdependence is the underlying coupling, collaboration is the management response.
• Task Interdependence is not Concurrency because Task Interdependence is the coupling of task completions; Concurrency is managing multiple parallel processes—interdependence is workflow coupling, concurrency is parallel execution.
• Task Interdependence is not Coupling because Task Interdependence is workflow-level coupling between task completions; Coupling is subsystem variable linkage strength—interdependence is task-level, coupling is systems-level.
• Task Interdependence is not Coordination because Task Interdependence is the workflow coupling where task completion depends on another; Coordination is active alignment of actors or processes—interdependence is the underlying condition, coordination is the management response.