To track delayed milestones across departments, maintain a shared list of commitments linked to unfinished dependencies and accountable owners. Group milestones that depend on the same team or approval. This helps executives see when several late projects require one cross-team decision rather than separate status escalations.
Use milestones with clear acceptance conditions#
A milestone should describe an observable result: approval granted, release accepted or customer setup completed. “Work mostly done” leaves too much room for different interpretations.
Keep the commitment date, current forecast and reason for a change distinct. If the original date is overwritten at every review, leadership loses the history needed to understand repeated slippage.
Include the fields needed for an executive decision#
| Field | Purpose |
|---|---|
| Milestone and accountable owner | Define the commitment |
| Committed date and current expectation | Expose slippage |
| Unfinished dependency | Identify the work preventing completion |
| Waiting team or decision owner | Find the next responsible action |
| Other affected projects | Expose a shared conflict |
| Decision needed and review date | Convert reporting into follow-up |
This is a reporting design you can apply to your records, not a claim that every field is a built-in portfolio column in Commandix.
Worked example: two projects share one approval#
In a hypothetical portfolio, a launch and a customer migration are both late. Their local reports show different blocked tasks, but both depend on the same technical approval team. A shared review reveals that the migration has complete inputs and a fixed customer window while the launch still needs a scope decision.
Leadership can protect the ready migration work and assign the launch scope decision. This is more specific than asking both project managers to recover their dates independently.
Review changes, not every task#
- Check newly exposed commitments.
- Open the dependencies whose dates or states changed.
- Group common bottlenecks.
- Resolve the priority or authority conflict.
- Retain the decision and the effect on deferred work.
Keep project owners responsible for detailed plans. The executive review should settle the decisions that cross those plans.
Follow the work in Commandix#
Commandix projects hold owners, dates and task views, including dependency context. Goals and Constraints help inspect related work across the company. Use that evidence beside the milestone record, and verify forecasts with the responsible team rather than treating them as guarantees.
Related guide: Find the shared bottlenecks behind a portfolio.
Frequently asked questions#
What is the difference between a due date and a milestone?#
A due date is a time commitment. A milestone also needs an explicit acceptance condition so everyone agrees what completion means.
How should we prioritize delayed milestones?#
Compare customer or business consequences, readiness and shared dependencies. A red status alone does not determine which milestone should receive capacity first.