When projects repeatedly miss deadlines, compare where unfinished work is waiting across projects. A shared reviewer, incomplete input or approval rule may explain several late dates. Start with the handoff holding up the next milestone, confirm the reason with its owner, then test one change before adding people.
Separate a late task from a recurring bottleneck#
A missed due date describes a symptom. A bottleneck is a step whose limited ability to handle the incoming work restricts progress toward your chosen result. One overdue task can matter enormously, but a recurring queue across several projects deserves a different response from an isolated absence.
Pick a delivery commitment and follow its unfinished dependencies backward. Record when each item became ready, who could accept it and what prevented that acceptance. Review ready work separately from requests that still lack a decision or usable input.
Check these four causes before changing the deadline#
- Too much active work: several projects compete for the same person. Choose a shared order and pause lower-priority starts.
- Incomplete inputs: work returns to its originator. Clarify acceptance criteria before releasing more requests.
- Approval delay: finished work waits for a decision. Confirm who has authority and when decisions happen.
- Qualified capacity shortage: ready, prioritized work waits even after interruptions and rework are addressed. Evaluate added capacity at that step.
Hiring for the wrong cause can increase the volume entering the queue. Moving the deadline without changing the cause can make the next review look exactly like this one.
Worked example: three releases waiting for security review#
In this hypothetical example, development is complete on three releases, but all need the same security reviewer. Two review requests lack threat-model details. The third is ready, yet loses its reserved review time to interruptions.
The first action is to repair the two incomplete requests and protect the ready review. Count accepted reviews and measure the age of ready requests at the next review. If clean work still arrives faster than reviews finish, additional qualified review capacity becomes a stronger option.
Use a short recovery checklist#
- Name the milestone, commitment date and business consequence.
- List the unfinished work required to reach it.
- Group waiting items by handoff, person or decision.
- Confirm the strongest explanation and one plausible alternative.
- Assign a change, an owner and a review date.
- Compare waiting age and completed milestones with the baseline.
Keep the definition of completion stable. Closing administrative tasks while the customer delivery remains blocked will make the count look better without repairing the commitment.
How Commandix supports a project-delay review#
Commandix links project work, goals, owners and dependencies. Its Constraints view presents a possible bottleneck with supporting records and confidence. Use those records to test the explanation with the teams involved. Track the response, then compare task movement in Flow Analytics. Software does not establish the root cause on its own.
Related guide: How to tell if your team needs more staff.
Frequently asked questions#
Why are projects late when everyone is busy?#
People can be busy on work that does not unblock the next milestone. Compare shared dependencies, waiting time and priorities before treating workload as proof of a staffing shortage.
What should I measure first?#
Start with the age and number of ready items waiting at the suspected bottleneck, plus completed milestones. Keep the time period and work type consistent.