A project can meet its schedule, budget and quality targets and still fail the organisation that funded it.
Time, cost and quality are powerful management disciplines. They make commitments visible, reveal variance and force trade-offs. Without them, project delivery can become unaccountable.
The mistake begins when these controls are treated as a complete definition of success.
The supplied MPM416 material explicitly challenges the assumption that the traditional “iron triangle” is enough to explain project success or failure. It argues that operational techniques such as PERT and CPM remain useful while also noting that they do not, by themselves, represent the uncertainty of complex project environments or the link to stakeholder value.
That distinction matters because executives do not invest in projects to create compliant schedules. They invest to change capability, performance or strategic position.
The Strategic Context
Project controls answer an important question: Are we delivering the agreed scope within acceptable constraints?
Enterprise governance must answer several additional questions:
- Did the output solve the problem that justified the investment?
- Did the organisation realise the intended benefit?
- Did the initiative improve strategic position or operating capability?
- Were the consequences acceptable to material stakeholders?
- Did the change create value that can be sustained?
These questions operate at different timescales. Delivery performance may be visible during the project. Benefits can emerge months or years later. Strategic value may depend on how the environment changes after implementation.
This temporal difference explains why project success is so easily misclassified. The easiest measures are often available first.
What Leaders Commonly Misread
The first misread is believing that a green dashboard means a good investment. It may mean only that the project is performing against its approved baseline.
The second is treating a missed baseline as proof of strategic failure. Some projects should change when evidence changes. A deliberate scope adjustment that protects value may be better than preserving an obsolete commitment.
The third is measuring benefits only after completion. If benefit logic is weak, leaders need to discover that before all capital has been committed.
The fourth is allowing the same success criteria to serve every governance level. Project teams need delivery measures. Program leaders need outcome and dependency measures. Portfolio leaders need investment, strategic contribution, capacity and aggregate risk measures.
The fifth is assuming stakeholder satisfaction should replace hard controls. It should not. Stakeholder value is broader than popularity, and project performance still requires disciplined delivery.
The answer is a layered model of success, not the rejection of traditional measures.
Reframing the Issue
Instead of asking whether a project is “successful”, leaders should ask:
Successful at what level, for whom, and over what period?
This produces a more useful hierarchy.
Delivery success
Did the team produce the agreed output with acceptable control of time, cost, quality, scope, safety and risk?
Transition success
Could the permanent organisation adopt and operate the output?
Benefit success
Did the new capability create the intended measurable outcome?
Strategic success
Did the outcome strengthen the organisation's priorities, resilience, position or long-term value?
Societal and stakeholder acceptability
Were the broader social, environmental and stakeholder consequences consistent with the organisation's obligations and values?
Not every project requires equal emphasis on every layer. But senior governance should know which layer it is actually measuring.
Strategic Analysis: Why the Triangle Persists
The iron triangle persists because it is useful. Time, cost and quality are comparatively concrete, can be measured frequently and sit close to the project manager's sphere of influence.
Strategic success is harder. It depends on external conditions, operational adoption, leadership behaviour and business-case assumptions. Accountability is more dispersed.
This can tempt organisations to manage what is easiest to count rather than what matters most.
A hypothetical customer-service transformation illustrates the problem. The project may deliver the system on time, within budget and to specification. Yet if staff adoption is weak, customer resolution time does not improve and operating costs rise because old and new systems run in parallel, delivery success has not translated into enterprise success.
The opposite case is also possible. A project may exceed the original schedule because a regulatory requirement changes, yet the revised solution may protect the organisation from much greater future exposure. A narrow scorecard could call the project late while strategic governance considers the adaptation rational.
Success therefore requires context.
Related article: A Project Can Finish and the Change Can Still Fail
Decision Framework
A five-layer success architecture can be used at approval and review.
| Layer | Core question | Typical evidence |
|---|---|---|
| Delivery integrity | Did we execute responsibly? | Schedule, cost, quality, safety, scope, risk |
| Operational adoption | Can the organisation use it? | Readiness, usage, process adherence, support load |
| Benefit realisation | Is performance improving? | Benefit indicators, productivity, service, revenue or risk outcomes |
| Strategic contribution | Does it advance the strategy? | Strategic objectives, capability position, resilience, option value |
| Stakeholder and sustainability impact | Are broader consequences acceptable? | Stakeholder outcomes, social and environmental effects, compliance, legitimacy |
The key is not to create a larger dashboard. It is to connect each layer causally.
For example:
Output delivered → capability available → behaviour changes → operational result improves → strategic objective advances.
If leaders cannot explain this chain, the business case may be describing aspiration rather than a credible mechanism of value creation.
A second principle is to assign ownership by layer. The project manager may own delivery integrity. An operational executive may own adoption and benefits. A sponsor or portfolio body may own strategic contribution. Shared accountability should not mean ambiguous accountability.
From Strategy to Execution
Immediately, review the success criteria of major projects and identify whether they stop at delivery. Add at least one outcome measure that tests whether the output is changing the target environment.
Over the medium term, connect project reviews to benefit and operating data. This avoids the common separation in which delivery teams report project health while business units report performance through unrelated systems.
Over the long term, use post-investment evidence to improve selection. If completed initiatives regularly meet delivery targets but fail to produce benefits, the organisation may not have a delivery problem at all. It may have a strategy, business-case or portfolio-selection problem.
Related article: Business Cases Are Investment Hypotheses, Not Permission Slips
Executives should also distinguish benefit erosion from delivery failure. An initiative may have been well executed, yet the market may have moved. That information should improve future investment logic rather than being hidden to preserve a simplistic success narrative.
The same logic applies to learning. A project that disproves a major assumption early can create value by preventing a larger commitment, even if the original objective is not achieved. Conversely, a project that reaches completion while suppressing adverse evidence may destroy value despite an apparently orderly close. Mature governance therefore rewards truthful learning as well as delivery performance, provided that learning is converted into timely decisions rather than used to excuse weak execution.
Signals to Monitor
Success measurement is too narrow when:
- board reporting focuses almost entirely on red-amber-green schedule and budget status;
- benefit owners become visible only near project closure;
- business cases contain benefits that are not operationally measurable;
- completed projects are labelled successful before adoption data exists;
- changes that protect strategic value are discouraged because they damage baseline metrics;
- project teams optimise local targets at the expense of downstream operations;
- stakeholder impacts are treated as communications issues rather than design constraints;
- post-investment reviews are rare or disconnected from future project selection.
A revealing signal is when leaders can state the variance to budget precisely but cannot explain whether the organisation is better off because the initiative exists.
Questions for the Leadership Team
- What does success mean beyond finishing the project?
- Which benefit measures will tell us whether the operating system actually improved?
- Who owns each layer of success after handover?
- Could the project meet all baseline targets and still be a poor investment?
- Could a justified change make delivery metrics worse while protecting strategic value?
- What stakeholder or sustainability consequence would make the outcome unacceptable even if the business case is achieved?
- How will lessons from realised benefits change future portfolio decisions?
References
Silvius, G 2017, ‘Sustainability as a new school of thought in project management’, Journal of Cleaner Production, vol. 166, pp. 1479–1493.
KPMG Australia & Australian Institute of Project Management 2020, project delivery performance survey as cited in the supplied course material. [FACT CHECK REQUIRED]
Closing Perspective
The iron triangle remains valuable because projects still need disciplined control. It becomes dangerous only when the organisation mistakes a delivery instrument for a complete theory of value.
Senior leaders need a wider view: delivery integrity, adoption, benefits, strategic contribution and acceptable stakeholder consequences. That wider view does not weaken accountability. It directs accountability toward the reason the project was funded in the first place.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.