Outgrace
Outgrace The Leadership Magazine, home
O

When On Time and On Budget Stopped Being Enough

MacBale’s P8 lifecycle: execution, reporting and replanning run as a loop until the business is stable

When On Time and On Budget Stopped Being Enough

For half a century, project managers were judged by a triangle of scope, schedule and cost. The profession is now trying to measure something harder: whether the project was worth doing.

diagram after Pragintion PM (via pragintionpm.com)

The triangle

Ask a project manager how a project is judged and most will draw a triangle. One corner is scope, what the project must deliver. Another is time, the schedule. The third is cost, the budget. The model, often called the iron triangle or the triple constraint and usually credited to the British engineer Martin Barnes in 1969, holds that the three are linked. Cut the budget and either the scope shrinks or the schedule stretches. Add scope and something else gives. Quality, in the original telling, sits in the middle and suffers when the corners are forced.

The triangle survived because it is useful. It gives a sponsor and a project manager a shared vocabulary for trade-offs, and it produces numbers that are easy to report: percentage complete, budget consumed, days late. The standard references of the profession built on it. Later editions of PMI’s Guide to the Project Management Body of Knowledge added quality, risk and resources alongside the original three, a recognition that the triangle on its own left too much out.

The trouble lies in what the triangle cannot see. A new finance system can be delivered in full, on the date promised, for the money agreed, and still fail: because staff route round it with spreadsheets, because the data migrated into it was dirty, or because the business case that justified it assumed a market that no longer exists. By the triangle’s measure, that project succeeded.

The value gap

The size of that blind spot has been measured, at least for large technology projects. In 2012 McKinsey and the University of Oxford reported on more than 5,400 large IT projects and found that, on average, they ran 45 per cent over budget and 7 per cent over time, and delivered 56 per cent less value than predicted. The overrun is the familiar complaint. The larger shortfall was the one the triangle does not record.

Practitioners who spend their careers on troubled programmes tend to make the same observation from the inside. Justin J. MacBale, a Texas-based programme manager who publishes essays on project method through his consultancy, Pragintion PM, put it in a July 2025 essay on the triangle’s limits: “In reality, even when scope, time, and cost are well-controlled, initiatives can still fail.” He added a point about accountability that the textbooks tend to skip: “The truth is, PMs rarely have direct control over these core constraints.” Budgets and deadlines are usually set when a project is approved, before the person who must deliver it has been hired.

A new definition

In 2024 the Project Management Institute, the largest professional body in the field, published a study that tried to change the definition itself. Drawing on nearly 10,000 practitioners, it proposed that a successful project is one that “delivers value that is worth the effort and expense”. It also argued that success is a continuum, not a pass or fail.

Asked to rate their projects on that basis, respondents judged 48 per cent successful, 40 per cent mixed and 12 per cent failures. PMI turned the result into a Net Project Success Score, the share of successes minus the share of failures, which came out at 36. The score resembles the Net Promoter Score used to track customer loyalty, and it shares that measure’s limitation: it records perceptions, not audited outcomes. But it moves the question from “did we do what we said?” to “was it worth it?”, and that is a different question for everyone involved, from the sponsor down.

The new definition puts a burden on the project manager that the triangle never did. To say whether something was worth its cost, you have to understand what the business needed from it. PMI’s 2025 Pulse of the Profession report examined exactly that, and the result was not flattering. Of 2,841 project professionals surveyed, only 18 per cent showed high business acumen. Those who did met business objectives more often (83 per cent against 78) and had fewer outright failures (8 per cent against 11). The gaps are modest, and a survey cannot prove that acumen causes better results. But the direction is clear, and it is the one PMI is now urging its members to take.

Where value leaks

Value leaks at predictable points. One is adoption: a system that people do not use delivers nothing, whatever the go-live report says. Another is what happens after launch. Many project plans end at delivery, and the weeks in which the business learns to run the new process are treated as someone else’s problem. MacBale’s own lifecycle model adds an explicit stage for “Support & Business Stabilization” before a project is closed, and his writing on rescuing failing projects ends on the same point: “Closure isn’t a checkbox.”

Mergers are where the leak is easiest to see. After a deal closes, the buyer must combine systems, data, processes and people, often under a transition services agreement that gives it only a fixed period of access to the seller’s systems. Run late and the costs mount; run fast and the integration can meet its dates while losing the customers, staff or data that made the deal worth doing. The project plan may look healthy throughout. The value case is where the damage shows.

A third leak is organisational. Project managers are expected to deliver outcomes they do not command. In MacBale’s phrasing, from a 2026 essay on what separates professional project management from organising a family event, “a project manager has little to no authority to make decisions.” The job is to get decision-makers the right information in time and to persuade them to act. That is a political skill as much as a technical one, and it does not appear on a Gantt chart.

What the machines take

Automation sharpens all of this. In 2019 Gartner predicted that AI would eliminate around 80 per cent of the tasks of today’s project-management offices by 2030, naming data collection, tracking and reporting. A 2026 survey of 1,651 project and portfolio professionals for the software company Smartsheet found that 97 per cent were already experimenting with AI, though only 46 per cent trusted it to act without supervision.

If the triangle is the measure, that is a threat: much of what is reported against scope, schedule and cost is exactly the routine collection and reporting that software does well. If value is the measure, the picture changes. Judging whether a project is still worth its cost depends on context that is often unwritten, such as a sponsor’s shifting priorities, a vendor’s history or a department’s resistance. MacBale, who is openly sceptical of AI in project roles, framed the limit in a July 2026 essay: “If your job requires you to act on information that is never published or tracked, then AI as a tool is not only limited but can be reckless to use.”

His sharper concern is about apprenticeship. Junior project staff have traditionally learned by doing the routine work and getting it wrong. Automate that work, he argues, and the profession removes the rung on which judgement is built. “So where does someone get entry level experience or how does someone enter a professional career with little to no experience?” It is a question the forecasts tend to skip.

The harder measure

None of this makes the triangle obsolete. Budgets still run out and deadlines still bind; a project that ignores them will not survive long enough to deliver value. What has changed is that the triangle is no longer accepted as a sufficient answer. Boards that have watched large programmes finish on time and fail anyway are asking a harder question, and the profession’s standards body is now asking it too.

The harder measure is also more uncomfortable for the people being measured. It is easy to prove that a milestone was met. It is much harder to prove that the business is better off, and harder still when the answer depends on decisions the project manager did not make. That discomfort is the point. The test is moving from whether the plan was followed to whether the project was worth doing.

Sources

Justin J. MacBale: studio headshot, smiling, grey pinstripe suit, light-blue shirt, patterned tie, soft beige backgroundProfessional services: project and programme management, pos

Ten Essays and a Podcast

Justin MacBale has not written a book. What he has published instead is a year of essays on project method, and a podcast about project careers.

Justin J. MacBale: studio headshot, smiling, grey pinstripe suit, light-blue shirt, patterned tie, soft beige backgroundProfessional services: project and programme management, pos

Justin MacBale, on the Record

Ten statements from his essays and published remarks, 2025 to 2026. Compiled from published sources; this is not an interview.

MacBale (right) with host Anna Anderson on the Project Manager Connect Show, 2026Professional services: project and programme management, pos

The Project Economy, Counted

Demand for project managers is rising, the definition of a successful project is changing and AI is aimed at the routine half of the job. What the main studies say, and where they stop.

Newsletter

The Briefing

One email a week: the leaders we profiled, the ideas worth stealing, and nothing else.

Weekly, free, one click to leave. Read our privacy policy.