How do we assess the impact of a change properly?
Incomplete change analysisTrace the proposed change across deliverables, dependencies, tests, training, operations, and commitments. Assess both the requested addition and the work it displaces.
What to do now
- Describe the requested outcome precisely
- Identify affected work and interfaces
- Estimate cost, schedule, and risk consequences
- Present options and a recommendation
When to escalate
Escalate when
The analysis exposes impacts beyond the team's authority or expertise.
Who decides
The authorized change decision maker
Example
Adding a new approval step affects permissions, notifications, training, testing, and turnaround time.
Mistake to avoid
Estimating only the visible implementation task.
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
- A change affects another project. Who coordinates it?Cross-project change impact
- The change request has no owner after approval. Who is responsible?Unassigned change implementation
- A change request has no budget impact listed. Is zero credible?Incomplete change impact
- We have many overdue tasks but little impact on delivery. What should we prioritize?Lateness without impact analysis