Pattern 8: Task Sequencing and Dependencies
Overview
Coordination structures contain work items in dependency relationships, with some items requiring completion of others before they can begin or complete. Dependencies may be explicitly mapped and communicated, or may remain implicit and discovered during execution.
Task completion criteria may be defined and observable, or may be ambiguous and subject to interpretation. Sequencing may be determined by inherent technical constraints, organizational structures, or resource availability. The degree of dependency visibility affects execution planning and blocking frequency.
These structural features appear where work items cannot be executed independently and in arbitrary order—in stable operations, during cross-functional coordination, and when executing novel or complex work.
Observable Manifestations
Work items blocked from starting or progressing due to incomplete prerequisites
Completed work requiring repetition due to execution in non-viable sequence
Actors expressing uncertainty about which pending work item to begin next
Disagreements about whether work items meet completion criteria for handoff
Downstream work items unable to proceed while upstream items remain incomplete
Parallel work efforts discovering conflicts due to unrecognized dependencies
Dependencies becoming visible during execution rather than planning
Task sequences defined early and not updated as work characteristics evolve
Organizational boundaries creating dependency relationships not inherent to the work
Completion criteria for work items subject to differing interpretation by actors
Structural Conditions
Work items with technical or logical dependencies requiring specific execution sequences
Multiple actors or teams executing interdependent work items
Knowledge required to identify and map dependency relationships accurately
Communication channels through which dependency information can be transmitted
Work stability sufficient for dependency relationships to remain relevant during execution
Resource constraints requiring sequential rather than parallel execution
Organizational structures creating coordination requirements between work items
Mechanisms for determining and communicating task completion status
Boundaries
Not about individual planning ability or execution speed
Not implying poor project management, planning failure, or organizational dysfunction
Not explaining why specific dependency structures exist in particular contexts
Not evaluating whether particular dependency structures are appropriate for contexts
Not addressing optimal dependency explicitness for specific situations
Not distinguishing necessary from unnecessary sequencing constraints
Common Misattributions
Attributed to poor planning when dependency structures have not been mapped or communicated
Attributed to individual impatience when actors begin work unaware of prerequisite requirements
Attributed to quality problems when completion criteria are structurally ambiguous
Attributed to slow execution when dependencies create unavoidable sequential constraints
Attributed to lack of coordination when dependency information is not accessible to relevant actors
Attributed to resistance to process when sequencing constraints are discovered rather than anticipated
Attributed to technical debt when organizational structures impose artificial dependency relationships
The presence of this pattern does not imply poor planning, process failure, or required change. It describes observable dependency and sequencing structures that exist across many functional and successful organizations. Both explicit and implicit dependency management approaches persist in different organizational contexts for context-specific structural reasons.