Integration has no single owner. Who should coordinate it?
Unowned integrated outcomeAssign a coordinating owner with authority to convene teams and manage shared readiness. Technical responsibility remains with specialists, but someone must own the end-to-end acceptance view.
What to do now
- Define the integrated outcome
- Map component owners and interfaces
- Assign coordination and acceptance responsibilities
- Review end-to-end evidence regularly
When to escalate
Escalate when
No role can resolve a cross-component readiness conflict.
Who decides
The accountable integration or dependency owner
Example
A program integration lead coordinates shared tests while component owners fix their own defects.
Mistake to avoid
Assuming the last team in the chain automatically owns all integration.
Prevent a repeat
Verify dependency completion with the consuming team and test the integrated outcome early enough to act.
Suggested ApprovedFlow setup
- Tasks
- Documents
- Projects
Keep dependency owners, required evidence and dates with linked work records, confirming supported link behavior in the current build. See the platform
Related cases
- How do we coordinate cutover tasks across several teams?Unintegrated cutover sequence
- Can we use a mock to unblock a dependency?Controlled provisional interface
- An urgent issue has no clear owner. What do we do now?Unowned urgent issue
- Who owns integration in a hybrid program?Missing end-to-end accountability