Tracking project performance beyond on-time and on-budget

"On time, on budget, in scope." For decades, that's been the definition of project success. It's easy to measure and easy to report. It's also incomplete. A project can hit all three and still fail to deliver anything the business values, and a project that runs late can still be the best investment in the portfolio.

Project performance tracking needs a wider lens. Delivery measures still matter, but they're one part of a bigger picture.

Four layers of project performance

Think of performance in four layers, each answering a different question:

Most organizations track the first layer thoroughly, the second partially, and the last two barely at all. Yet adoption and outcome are where value is actually created. See Outcome metrics vs. output metrics.

Choose measures at approval

The time to decide how you'll track performance is when the investment is approved, not after it's delivered. At approval, record:

• Delivery commitment: the forecast range and the committed date.
• Quality expectations: acceptance criteria and any operational targets.
• Adoption target: who should use it, and how many, by when.
• Outcome target: the objective measure, baseline, target and date.

With these defined up front, tracking becomes recording actuals against known targets rather than inventing measures after the fact. See Benefits realization.

Track the right layer at the right time

Each layer becomes relevant at a different point:

• During delivery: delivery measures, with early warnings. See Leading indicators of project trouble.
• At release: quality and acceptance.
• First 30 to 60 days: adoption.
• 90 to 180 days: outcome.

A single status color can't capture this. An initiative might be finished on delivery, healthy on quality, weak on adoption, and too early to judge on outcome. Each of those needs a different response.

Avoid overloading teams

Performance tracking fails when it becomes a reporting burden. Keep it light:

• One primary measure per layer for most initiatives.
• Pull delivery data from delivery tools rather than asking teams to re-enter it.
• Make the business owner responsible for adoption and outcome data, since they're closest to it.
• Track at the right frequency. Delivery weekly or by sprint; adoption monthly; outcomes at planned reviews.

Reading performance across the portfolio

Individual project tracking is useful. Portfolio-level patterns are more useful:

• Which types of investment reliably hit their outcome targets?
• Where does adoption consistently fall short?
• Is forecast accuracy improving over time?
• What share of completed investments have an outcome measured at all?

That last measure is a good health check on its own. If fewer than half of completed investments have a recorded outcome, the organization is effectively flying blind on value. See Closing the loop.

A simple performance summary

For each initiative in a portfolio review, a one-line summary across layers is often enough:

Supplier portal. Delivery: complete, 3 weeks late. Quality: 2 minor defects. Adoption: 62% of suppliers onboarded (target 80%). Outcome: onboarding time 9 → 4 days (target 3); review due in March.

That line tells leaders more than any status color, and points straight at the action needed: adoption.

How Aizu helps

Aizu keeps the layers together for each initiative. Delivery evidence and completed sprint velocity come from Jira or Azure DevOps; work items track what has been done; and objectives, key results and KPIs record targets and actual measurements over time. Portfolio views distinguish work completed from value achieved, so a finished initiative with an unmet outcome stays visible. Related: The post-implementation review.