Earned value can reveal whether authorised work is progressing efficiently, but it cannot prove that the work remains worth doing.
A program reports a cost performance index close to plan and a schedule index that appears manageable. The dashboard is green. Yet critical integration work is slipping, defects are rising and the business case has weakened. The metrics are not necessarily wrong. Leaders are asking them to answer questions they were not designed to answer.
Earned value management is powerful when used within its boundary. It becomes dangerous when numerical control is mistaken for strategic control.
The Strategic Context
Earned value management integrates scope, schedule and cost through a common performance baseline. Planned value represents the budgeted value of work expected to be complete. Earned value represents the budgeted value of work actually completed. Actual cost records what that work cost.
These measures allow leaders to compare progress with plan and examine cost and schedule efficiency. They can also support forecasts of the likely cost at completion.
For complex projects and programs, this creates disciplined visibility that simple budget-versus-actual reporting cannot provide. Actual expenditure alone does not show how much authorised work has been accomplished. Low spending may indicate efficiency or delay. Earned value helps distinguish the two.
Its strategic value, however, depends on the integrity of the baseline and the decisions made from the evidence.
What Leaders Commonly Misread
The first error is reading earned value as business value. In EVM, “value” is the budgeted value assigned to completed work. It is not customer value, revenue, benefit or economic value.
The second is assuming that a favourable index proves project health. EVM does not automatically measure quality, safety, stakeholder acceptance or benefits. A team can earn planned value by completing defective or strategically obsolete work if completion rules allow it.
The third is treating schedule variance as a direct measure of completion date risk. Traditional schedule indicators aggregate work across the baseline. They may not distinguish between delay on the critical path and delay on work with available float.
The fourth is assuming that the method creates objectivity by itself. Percentage-complete assessments, poorly structured work packages and weak change control can make the results appear precise while remaining highly judgemental.
Reframing the Issue
EVM should be reframed as one instrument in a wider executive control system.
It answers a specific question: relative to the authorised baseline, how efficiently is the project converting time and cost into completed scope?
It does not answer:
- Does the scope still support strategy?
- Is the deliverable fit for purpose?
- Are critical dependencies protected?
- Will operations adopt the result?
- Are benefits still achievable?
- Has the external environment changed the investment case?
The executive task is to combine EVM evidence with these wider dimensions rather than demand that one metric represent the entire investment.
Baseline Integrity Determines Metric Integrity
EVM depends on an integrated baseline containing defined scope, sequenced work and time-phased budgets. If work is vague, completion cannot be measured credibly. If the schedule is unrealistic, comparison with it provides false assurance. If budgets are disconnected from work packages, earned value loses meaning.
Change control is equally important. Approved changes should modify the baseline transparently. Constant rebaselining to remove adverse variance destroys the historical signal. Refusing to update a baseline after legitimate change is also misleading.
Leaders need to know whether baseline revisions represent authorised changes in the investment or attempts to restore favourable performance.
Related article: The Work Breakdown Structure Is a Control Architecture
Progress Rules Must Reduce Subjectivity
Work should earn value through predefined, observable completion rules. Short work packages with tangible outputs generally provide stronger evidence than long activities assessed through subjective percentages.
Practical approaches may include:
- Fixed-formula methods for short tasks.
- Weighted milestones for longer, staged work.
- Completed units where outputs are repetitive.
- Objective technical measures where physical progress can be verified.
- Zero value until full completion for short, indivisible deliverables.
No method is universally superior. The choice should reflect the work and consequence. The purpose is to prevent reported progress from moving ahead of demonstrated achievement.
Quality controls must also interact with the earning rule. If a deliverable fails agreed verification, leaders should question whether its budgeted value has genuinely been earned.
Indices Need Context
The cost performance index compares earned value with actual cost. The schedule performance index compares earned value with planned value. Values below one generally indicate unfavourable efficiency against the baseline; values above one indicate favourable performance.
Interpretation requires context. A favourable cost index may result from deferred work or unavailable resources. A poor cost index may reflect an authorised acceleration intended to protect greater enterprise value. Schedule efficiency may improve while a critical dependency continues to deteriorate.
Forecasts based on past performance also assume that the future will behave sufficiently like the past. That may be reasonable for repetitive work and weak for novel integration, regulatory approval or commissioning.
Related article: The Critical Path Is a Forecast, Not a Promise
The Executive Performance Stack
EVM becomes more useful when placed within a layered performance view:
- Delivery efficiency: EVM cost and schedule measures.
- Technical performance: requirements achieved, defects, test results and process capability.
- Critical-path health: milestone confidence, float consumption and dependency risk.
- Operational readiness: people, process, data, support and transition conditions.
- Benefits outlook: expected value, timing and ownership.
- Strategic relevance: whether the investment still deserves priority.
This stack prevents a green delivery metric from masking a red strategic condition.
Decision Framework
When reviewing EVM results, leaders should ask:
| Test | Required interpretation |
|---|---|
| Baseline | Is the reference plan authorised, integrated and still credible? |
| Progress | Is earned value supported by objective completion evidence? |
| Quality | Has completed work passed relevant verification? |
| Criticality | Are variances affecting critical or non-critical work? |
| Forecast | Which assumptions make the completion forecast credible? |
| Strategic value | Does the remaining work still justify the remaining cost? |
The response to adverse performance should not be automatic. Options include correcting execution, resequencing work, changing scope, funding acceleration, revising the delivery model or stopping the investment. Each response should be judged by enterprise value, not by its ability to make an index look better.
EVM itself should also pass a proportionality test. Establishing and maintaining a credible system consumes effort. It is most valuable where work can be structured, baselines are meaningful and the consequence of weak visibility justifies the control cost.
From Strategy to Execution
Immediately, verify that reported value is tied to defined deliverables and acceptance evidence. Separate schedule-index commentary from critical-path analysis.
Over the medium term, integrate EVM with risk, quality, change and benefits reporting. Forecasts should be reconciled with identified risks and actual delivery constraints rather than generated mechanically.
Long-term capability requires calibration. Organisations should compare forecast-at-completion accuracy with actual outcomes, examine where progress rules failed and improve baseline design. Current Australian guidance includes AS 4817:2019 and AS 21512:2025; organisations applying formal EVM should verify the standards and contractual requirements relevant to their context before implementation.
Portfolio leaders should avoid imposing full EVM on every initiative. The method should be tailored to materiality, complexity, contractual environment and the organisation's ability to maintain reliable data.
Signals to Monitor
Warning signs include:
- Earned value increases while defects or rework rise.
- Long activities report steady percentages without objective outputs.
- Baselines are repeatedly changed after adverse performance appears.
- Schedule indices are discussed without critical-path evidence.
- Forecasts ignore known risks, supplier failures or approval constraints.
- Leaders equate favourable EVM indices with benefits realisation.
- The reporting system costs more effort than the decisions it improves.
Questions for the Leadership Team
- What exactly has been earned, and what evidence proves completion?
- Is the baseline credible enough to serve as a management reference?
- Which current variance threatens the critical path, quality or benefits?
- Are favourable metrics hiding deferred work or weaker acceptance standards?
- Does the remaining investment still create sufficient strategic value?
- Is the control system proportionate to the project's consequence and complexity?
Closing Perspective
Earned value management is valuable because it links completed scope to time and cost. That discipline should be protected. Its boundary should be protected as well. EVM can reveal execution efficiency and improve forecasts, but leaders must still judge quality, criticality, operational readiness and strategic relevance. Measurement supports judgement; it does not replace it.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.