"What gets measured gets managed" -- this famous quote from Peter Drucker also holds true for project management. Yet many project managers fly blind: they have a gut feeling about how the project is going, but no hard numbers. The result? Problems are detected too late, budgets are silently exceeded, and timelines slip unnoticed -- until it's too late.
In this guide, you'll learn which 15 KPIs really make a difference in project management. For each KPI, we provide the formula, the target value, and a practical example. At the end, we show you how to build a KPI dashboard that works -- and how AI in project management can automate KPI tracking.
A metric is any measurable value (e.g. "number of completed tasks"). A KPI (Key Performance Indicator) is a metric that is directly relevant to the project goal. Not every metric is a KPI -- but every KPI is a metric. Focus on the vital few that truly drive your project's success.
Why KPIs Are Essential in Project Management
Projects without KPIs are like driving without a dashboard: you know you're moving, but not how fast, how much fuel is left, or whether the engine is overheating. According to the Standish Group CHAOS Report, only 35% of all projects are completed successfully. Projects with systematic KPI tracking have a 2.5x higher success rate.
Good project KPIs deliver three things:
- Early warning system: Problems are detected before they become critical
- Decision-making basis: Objective data instead of gut feelings
- Communication tool: Stakeholders see the project status at a glance
Less is more. Too many KPIs lead to information overload and loss of focus. Start with the "Big 3" (SPI, CPI, milestone hit rate) and add project-specific KPIs as needed. Every KPI must trigger a concrete action when the target value is not met.
Time KPIs: Is the Project on Schedule?
Time KPIs answer the most fundamental project management question: Will we finish on time? The following five KPIs give you a precise view of schedule adherence.
Schedule Performance Index (SPI)
The SPI is the standard metric for schedule adherence in earned value management. It shows the ratio of work actually completed to work planned -- regardless of costs.
Target: SPI ≥ 1.0 Warning: SPI < 0.9
Example: By week 8, you planned to have completed work worth 80,000 EUR (PV). In reality, you completed work worth 68,000 EUR (EV). SPI = 68,000 / 80,000 = 0.85 -- the project is 15% behind schedule.
Practical tip: An SPI below 0.9 rarely recovers without active intervention. At this point, schedule recovery measures or scope adjustments should be discussed with stakeholders.
Milestone Hit Rate
Simpler than SPI and often more intuitive for stakeholders: What percentage of milestones were achieved on time? This KPI is particularly effective in combination with SPI, as it shows whether the delays are systemic or limited to individual milestones.
Target: ≥ 80% Warning: < 60%
Example: 10 milestones were due, 7 were hit on time. Milestone hit rate = 70%. The three missed milestones should be analyzed: Are they on the critical path? Are they from the same phase?
Schedule Variance (SV)
While SPI shows a ratio, the schedule variance gives you the absolute deviation in monetary terms. This is useful for communicating to management: "We are 12,000 EUR worth of work behind schedule."
Target: SV ≥ 0 Warning: SV < -10% of PV
Cycle Time
The cycle time measures how long it takes from the start of a task to its completion. Particularly relevant in agile projects. A rising cycle time is an early warning signal for bottlenecks, blockers, or scope creep.
Target: stable or decreasing trend Warning: increasing trend over 3+ sprints
On-Time Completion Rate
Measures the percentage of tasks completed by their deadline. Similar to the milestone hit rate, but at the task level. A dropping on-time rate often points to overly optimistic estimates or resource conflicts.
Target: ≥ 75% Warning: < 60%
Cost KPIs: Is the Budget Under Control?
Budget overruns are among the most common reasons for project failure. These cost KPIs give you full transparency about project expenditures -- and can be combined well with budget planning tips.
Cost Performance Index (CPI)
The CPI is the counterpart to SPI for costs: it shows whether you are getting value for money. A CPI of 0.8 means you are only getting 80 cents of value for every euro spent.
Target: CPI ≥ 1.0 Warning: CPI < 0.9
Example: You have completed work worth 68,000 EUR (EV), but spent 85,000 EUR (AC). CPI = 68,000 / 85,000 = 0.80 -- the project is 20% over budget.
Key insight: Studies show that a CPI established by the 20% completion mark of a project rarely improves by more than 10% by the end. An early low CPI is a strong predictor of budget overruns.
Budget Utilization
A simpler alternative to CPI: What percentage of the total budget has been spent? Compared against the project progress (e.g. 60% of the budget spent at 50% completion = potential overrun).
Target: proportional to project progress Warning: > 10 percentage points ahead of progress
Estimate at Completion (EAC)
The EAC projects the expected total cost at project completion based on current performance. This gives management a realistic forecast instead of the original budget figure.
Target: EAC ≤ BAC Warning: EAC > BAC + 10%
Example: Total budget (BAC) is 200,000 EUR, CPI is 0.80. EAC = 200,000 / 0.80 = 250,000 EUR. At the current rate, the project will cost 50,000 EUR more than planned.
Quality KPIs: Does the Result Meet Expectations?
A project can be on time and on budget -- and still fail if the quality isn't right. These KPIs measure whether the deliverables actually meet the requirements.
Defect Rate / Error Rate
Counts the number of defects per deliverable or per sprint. Particularly important in IT projects, but also applicable to other areas (e.g. error rate in process documentation).
Target: decreasing trend Warning: increasing trend over 3+ periods
Requirements Coverage
Measures how many of the defined requirements have been implemented. Protects against scope creep (new requirements being added) and scope gaps (requirements being "forgotten").
Target: 100% of must-haves at go-live Warning: < 90% of must-haves at 80% project time
Stakeholder Satisfaction
A qualitative KPI measured through regular surveys (e.g. NPS or simple 1-5 scale). Often the "truth check" for all other KPIs: a project can look great on all quantitative metrics but still face resistance if stakeholders feel uninvolved.
Target: ≥ 4.0 Warning: < 3.0 or declining trend
Team KPIs: How Productive Is the Team?
Team KPIs are the most sensitive metrics in project management. Used correctly, they identify bottlenecks and help with capacity planning. Used incorrectly, they destroy trust and motivation. Important: Team KPIs should always be used at the team level, never for evaluating individuals.
Team Velocity
The classic agile KPI: how many story points (or tasks) does the team complete per sprint? Velocity is a planning tool, not a performance metric. It helps predict how much the team can accomplish in the next sprint.
Target: stable, within +/- 20% of average Warning: decline over 3+ sprints
Practical tip: Do not compare velocity across teams. Story points are team-specific estimates. One team's "5" is not the same as another team's "5".
Resource Utilization
Measures how much of the available capacity is actually being used for project work. Too low indicates inefficiency; too high leads to burnout and quality problems.
Target: 70-85% Warning: > 95% (burnout risk) or < 50% (inefficiency)
Why not 100%? People need time for communication, meetings, administrative tasks, and learning. A utilization rate above 90% almost always leads to quality problems and employee turnover.
Risk KPIs: How Well Are Risks Managed?
Risk KPIs are often neglected but are among the strongest predictors of project success. Projects that actively track risks have demonstrably fewer surprises.
Risk Exposure
The total monetary risk the project is exposed to. Calculated as the sum of all individual risks (probability × impact). Gives management a clear picture: "Our current risk exposure is 45,000 EUR."
Target: decreasing over time Warning: increasing or > 20% of budget
Risk Response Rate
Measures how many of the identified risks have a defined mitigation plan. A high number of identified risks with no response plans is worse than fewer risks with clear mitigation strategies.
Target: 100% for high/critical risks Warning: < 80% for high risks
Building a KPI Dashboard: The 5-Step Guide
KPIs are only useful if they are visible, up-to-date, and actionable. Here's how to build an effective KPI dashboard in five steps:
Step 1: Select the right KPIs
Start with the "Big 3": SPI, CPI, and milestone hit rate. Then add 2-5 project-specific KPIs depending on your project type (IT project? Add defect rate. Agile project? Add velocity).
Step 2: Define target values and thresholds
Every KPI needs a target value (green), a warning threshold (amber), and a critical threshold (red). Without thresholds, a KPI is just a number -- it doesn't tell you whether action is needed.
Step 3: Determine data sources and update frequency
Where does the data come from? How often is it updated? For SPI/CPI, weekly updates are recommended. For stakeholder satisfaction, monthly is sufficient. Automation is key: manual KPI tracking is the number one reason why KPI dashboards are abandoned.
Step 4: Visualize effectively
Use traffic light colors (red/amber/green), trend lines, and progress bars. Avoid pie charts (hard to read) and 3D effects (distort perception). The golden rule: a stakeholder should understand the project status in under 10 seconds.
Step 5: Act on the data
The most important step and the one most often neglected: define what happens when a KPI turns amber or red. Who gets notified? What meeting is triggered? What decisions need to be made? A KPI dashboard without defined actions is decoration.
PathHub AI automatically suggests relevant KPIs based on the project type and generates target values from its experience database. This eliminates the guesswork in steps 1 and 2.
5 Mistakes When Using Project KPIs
Mistake 1: Too many KPIs
If everything is a KPI, nothing is. More than 10 KPIs per project leads to information overload. Nobody reads a 30-metric dashboard. Focus on the vital few.
Mistake 2: Vanity metrics
"Number of meetings held" or "pages of documentation written" look good but don't indicate project success. Every KPI should answer the question: "If this metric changes, would we make a different decision?"
Mistake 3: Only measuring at the end
KPIs that are only calculated at project completion are useless for course corrections. KPIs must be tracked continuously -- ideally weekly for time and cost KPIs.
Mistake 4: Using KPIs as a weapon
If KPIs are used to assign blame, teams will game the metrics. KPIs should be a learning tool, not a punitive instrument. Transparency only works in a psychologically safe environment.
Mistake 5: No action on red KPIs
The most common KPI mistake: the dashboard shows red, but nobody takes action. Either the threshold is wrong (and should be adjusted), or there is a problem that must be addressed immediately. Red KPIs that stay red for weeks are a sign of dysfunctional project governance.
KPI Tools and Automation
Manual KPI tracking -- collecting data from spreadsheets, calculating formulas, creating presentations -- is the number one reason why KPI dashboards fail. Automation is the key to sustainable KPI usage.
| Approach | Pros | Cons | Best for |
|---|---|---|---|
| Excel / Google Sheets | Flexible, familiar | Manual, error-prone, not real-time | Small projects, initial setup |
| PM tools (Jira, Asana, Monday) | Integrated, real-time data | Limited KPI selection, complex setup | Running projects with existing tools |
| BI tools (Power BI, Tableau) | Powerful visualization, cross-project | Expensive, needs data engineering | Large organizations, portfolio view |
| AI-powered (PathHub AI) | Automatic KPI suggestion, anomaly detection | Newer approach | Quick project setup, intelligent alerts |
The trend is moving clearly toward AI-powered KPI tracking: instead of manually defining KPIs and thresholds, AI suggests the right metrics based on the project type and automatically alerts when anomalies are detected. Learn more about AI in project management.
Conclusion: KPIs as a Navigation System for Your Project
Project KPIs are not bureaucratic overhead -- they are your navigation system. Without them, you're driving blind. With the right KPIs, you detect problems early, make better decisions, and communicate clearly with stakeholders.
The key takeaways:
- Start with the "Big 3": SPI, CPI, and milestone hit rate cover 80% of your needs
- Less is more: 5-8 KPIs per project, each with a clear target value and defined actions
- Automate: Manual KPI tracking dies within weeks. Use tools that automatically collect and visualize data
- Act: A KPI without consequences is decoration. Define what happens at amber and red thresholds
- Learn: Use KPIs for continuous improvement, not for punishment
The easiest start? Create a project in PathHub AI and let the AI suggest the right KPIs with target values. It takes 30 seconds and gives you a KPI framework you can immediately put to use.