A change affects another project. Who coordinates it?
Cross-project change impactInvolve the affected project owners before committing to the change. The originating team may understand its local benefit without seeing the wider portfolio consequence.
What to do now
- Identify affected projects and services
- Share the proposed change and timing
- Assess combined impacts and options
- Obtain a coordinated authorized decision
When to escalate
Escalate when
The change creates a conflict no single project can resolve.
Who decides
The authorized change decision maker
Example
An API change is coordinated with the consuming project's test and release plans.
Mistake to avoid
Approving locally and informing dependent teams afterward.
Prevent a repeat
Compare delivered changes with authorized decisions and keep the current baseline distinguishable from earlier versions.
Suggested ApprovedFlow setup
- Documents
- Approvals
- Tasks
Keep the change request, impact assessment and recorded decision together; update affected tasks only after the appropriate authorization. See the platform
Related cases
- How do we assess the impact of a change properly?Incomplete change analysis
- How do we keep change control lightweight for a small team?Proportionate change recording
- Nobody wants to own a risk outside their department. Who should take it?Cross-boundary risk ownership
- A change request has no budget impact listed. Is zero credible?Incomplete change impact