I've seen project dashboards with 40 indicators nobody looked at, and two-page weekly reports the sponsor opened without reading. The problem isn't lack of data: it's an excess of metrics that don't drive any decision. This guide lists only the metrics that, in my direct experience, actually change the behaviour of whoever reads them.
1. Schedule Performance Index (SPI) and Cost Performance Index (CPI). Derived from Earned Value Management, SPI and CPI remain the most reliable indicators for projects with defined budget and schedule. SPI below 1.0 indicates delay, CPI below 1.0 indicates budget overrun. The real value isn't the isolated number but the trend: an SPI dropping week over week is a much more useful warning signal than a single negative data point.
2. Burn rate and runway (for fixed-budget projects). How much budget you're consuming per week versus how much is left. For long-timeline projects, this indicator anticipates a budget problem weeks earlier than a traditional cost-consumption report.
3. Lead time and cycle time (for Kanban/continuous-flow teams). For flow-based teams (support, operations, maintenance), velocity and burndown make no sense. Lead time (from task entry to exit) and cycle time (from actual work start to exit) are the correct metrics because they reflect the real experience of the stakeholder waiting for the outcome.
4. Percentage of milestones hit on-time vs replanned. It's not enough to check if a milestone was hit: what counts is how many times it was replanned before it was. A milestone hit after three replans signals an estimation or execution problem that a simple 'hit yes/no' hides completely.
5. The report the sponsor actually reads. The format that works best in my experience is a single page structured as follows: overall status (green/yellow/red) at the top, three bullets on what changed since last week, risks that require a decision within 7 days, and nothing else. Any additional detail should be available on request, not included by default — the report's purpose is to drive decisions, not to demonstrate how much work has been done.
FAQ. How many KPIs should a project dashboard have? Between 4 and 6 for the sponsor/board level. The operational team can monitor more at the detail level, but upward synthesis must stay essential. Is EVM (Earned Value Management) still relevant in 2026 with agile methodologies? Yes, in adapted form: many agile teams apply EVM at the release or program level, even if not at the individual sprint level.
If your current project reporting produces data but not decisions, let's book a call: I'll help you redesign an essential KPI set and a report format the sponsor actually reads.
