Project dashboards

Key Points

• Shows the right few metrics that drive decisions, not every data point.
• Combines schedule, cost, scope, quality, risks, and benefits in one view.
• Uses thresholds and color coding (e.g., RAG) to highlight exceptions.
• Supports drill-down from summary to detail for investigation.
• Refreshes on a defined cadence or real time, with clear data owners.
• Tailors views for different audiences such as executives, PMs, and teams.
• Aligns with governance rules, tolerances, and escalation paths.

Purpose of Analysis

Enable fast, evidence-based control of project performance and early risk response. Make it easy to spot trends, variances, and threshold breaches that require decisions.

• Confirm if the project is within agreed tolerances and forecast to meet objectives.
• Identify where to intervene, reallocate resources, or escalate issues.
• Communicate a consistent health story to stakeholders.

Method Steps

• Define audience and decisions: who uses the dashboard and what decisions it should enable.
• Select KPIs and thresholds: pick a minimal set linked to scope, schedule, cost, quality, risks, and benefits.
• Choose tooling: spreadsheet, BI platform, PPM tool, or agile board widgets.
• Design layout: place top KPIs and RAG at the top, trends in the middle, and drill-down links below.
• Connect data sources: schedules, cost systems, defect trackers, risk logs, and change records.
• Set refresh cadence and ownership: automate where possible and assign data stewards.
• Validate with users: test clarity, accuracy, and actionability before rollout.
• Operate and improve: review usage, refine KPIs, and retire vanity metrics.

Inputs Needed

• Approved baselines for scope, schedule, and cost.
• Current schedule progress, milestones, and critical path data.
• Cost actuals, commitments, and forecasts, including earned value measures.
• Quality results such as defect counts, test pass rates, and rework.
• Risk register and issue log with status and ownership.
• Change requests and cumulative impact on scope, time, and cost.
• Resource allocation, capacity, and utilization data.
• Benefits and value metrics where applicable.

Outputs Produced

• Current health indicators and RAG status by objective or workstream.
• Trend charts for schedule, cost, defects, and throughput.
• Exception alerts and threshold breach flags.
• Action items and ownership captured from dashboard reviews.
• Forecast views such as completion dates, EAC, and expected defect leakage.
• Exportable snapshots for governance meetings and audit trails.

Interpretation Tips

• Prioritize trends and rate-of-change over single-point values.
• Always check the baseline and tolerance context behind a red or amber status.
• Pair lagging indicators with leading ones such as backlog age or defect arrival rate.
• Validate data freshness to avoid acting on stale numbers.
• Drill down to root causes before prescribing corrective actions.
• Watch for metric trade-offs such as speed increasing defects or cost reductions risking scope.

Example

A weekly executive dashboard for a SaaS rollout shows RAG health, schedule variance, EAC vs. BAC, a burn-up of delivered features, defect trend by severity, top five risks, and change volume. The dashboard flags a rising defect trend and a one-week slip on the critical path. The sponsor approves adding a tester and deferring a low-value feature, restoring the forecast within tolerance.

Pitfalls

• Overloading with too many KPIs and unclear visuals.
• Relying on manual updates that cause delays and errors.
• Using KPIs that are not tied to objectives or decision rights.
• Ignoring forecast views and focusing only on historical data.
• One-size-fits-all views that do not meet stakeholder needs.
• Ambiguous thresholds leading to inconsistent status calls.
• Lack of data lineage and definitions, undermining trust.

PMP Example Question

During a governance review, the sponsor questions frequent status changes from green to amber. What should the project manager do to improve the dashboard's decision usefulness?

1. Reduce the number of metrics to only schedule and cost.
2. Add clear thresholds, data freshness indicators, and links to drill-down detail.
3. Switch to monthly updates to stabilize status signals.
4. Remove trend charts and show only current status.

Correct Answer: B — Add clear thresholds, data freshness indicators, and links to drill-down detail.

Explanation: Decision-ready dashboards need defined thresholds, transparent data currency, and traceability to details. This increases consistency and supports effective governance decisions.