We have many overdue tasks but little impact on delivery. What should we prioritize?
Lateness without impact analysisPrioritize according to consequence, not age alone. Review each overdue task's effect on critical outcomes, downstream work, risk exposure, and the ability to complete the project.
What to do now
- Confirm which overdue tasks are still needed
- Map their downstream impact
- Rank work by consequence and urgency
- Agree owners and realistic recovery dates
When to escalate
Escalate when
An overdue item blocks a critical outcome or unmanaged exposure.
Who decides
The project manager and relevant commitment owner
Example
A delayed logo update waits while the team resolves a data validation task that prevents launch.
Mistake to avoid
Treating a late cosmetic task like a blocked go-live prerequisite.
Prevent a repeat
Compare forecast versus actual results for comparable tasks, separating effort, elapsed time, waiting and scope change.
Suggested ApprovedFlow setup
- Tasks
- Timesheets
- Resources
Keep planned dates and assumptions with the affected task, compare recorded actuals, and attach the revised forecast for review. See the platform
Related cases
- Every task is on time, but the project is late. What are we missing?Missing schedule relationships
- How do we estimate work we have never done before?High-uncertainty estimation
- How do we assess the impact of a change properly?Incomplete change analysis
- How do we track the cumulative effect of many changes?Invisible aggregate change impact