Build a project performance dashboard around the decisions made when a milestone slips. Show the commitment, unfinished dependencies, waiting age and accountable owners. Each summary should open the records behind it. Begin with one project so you can verify the numbers before copying the dashboard across the portfolio.
Start with the decision and its audience#
A project manager needs task detail. An executive needs the exposed commitment and the tradeoff requiring authority. Put the latter first and provide a path into the former. Avoid squeezing every operational measure onto the first screen.
Define one action the dashboard should support, such as prioritizing a shared reviewer or settling an approval. This gives you a reason to include each field.
Use a metric specification before building charts#
| Metric | Definition to record | Useful follow-up |
|---|---|---|
| Overdue work | Included states and due-date rule | Which missed item affects the milestone? |
| Blocked work | Explicit blocked state and reason | Who can remove the dependency? |
| Waiting age | Start event and elapsed-time convention | Which ready request has waited longest? |
| Completed work | Completion rule and period | Did the critical deliverable finish? |
Include filters, refresh time and known exclusions. Readers should not need to guess why their task count differs from the summary.
Example: a green completion rate hides a late approval#
In a hypothetical project, nine small tasks are complete and one approval remains. A 90% completion figure can be accurate while the customer commitment is still at risk. Place the approval and its consequence beside the progress number.
The dashboard now supports a specific question: who can decide, and what evidence do they need? It avoids encouraging the team to close more small tasks to make the percentage look healthier.
Validate the dashboard against source records#
- Select a sample of included and excluded tasks.
- Recalculate each displayed count.
- Test an overdue blocked task and a cancelled task.
- Check access for the intended reader.
- Confirm that the drilldown preserves the same filters.
- Review missing dates and stale status updates.
Repeat this check after changing status definitions or data mappings. Consistent definitions matter more than adding another chart.
Use Commandix as the working record#
Commandix’s dashboard links to goals and department work. Project and task views provide the detail for a delay review. Use Constraints when the evidence suggests a shared bottleneck. Keep the business outcome beside task completion so the reporting does not confuse activity with delivery.
Related guide: Track delayed milestones across departments.
Frequently asked questions#
How many metrics should be on the dashboard?#
Use the smallest set that supports the decision. Add a metric only when someone can explain what action a change in it should trigger.
Should every overdue task be red?#
Overdue status is useful, but priority should also reflect the task’s effect on the milestone, its dependencies and the business consequence.