The Iron Triangle Isn't Enough – Atkinson's Research
Time, cost and quality. The three corners of the iron triangle are often the first thing a project manager learns — and the most common way to judge whether a project succeeded. But as far back as 1999, researcher Roy Atkinson pointed out a built-in problem: two of the corners are guesses made at the stage of the project when we know the least.
Atkinson's article has become one of the most discussed in project management research. It's not about throwing the triangle away, but about no longer treating it as the only measure of success — something that affects how you should report, prioritize and talk to your sponsor.
What does the research say?
The article was published in the International Journal of Project Management. Atkinson's reasoning is simple but sharp: the schedule and budget are set early in the project, when uncertainty is at its highest. In practice they are educated guesses — 'two best guesses', as he calls them. Quality, the third corner, is even harder to pin down: different people perceive it differently, and that perception also changes over time.
If we only measure success against these three metrics, we risk drawing the wrong conclusions in both directions. A project that stays on time and on budget can deliver something nobody uses. A project that blows its schedule can still create great value for the organization. Judging the project solely by the guesses then means measuring the wrong things.
Atkinson therefore proposes assessing success more broadly: beyond the iron triangle, also the quality of what is actually delivered, the benefits to your own organization, and the benefits to a wider circle of stakeholders — everyone affected by the outcome. The triangle is still needed to steer the work, but it is a tool for tracking progress, not the whole truth about whether the project was worth doing. According to Atkinson, measuring the wrong things is just as serious as measuring the right things wrongly — both lead to bad decisions.
What does this mean for you as a project manager?
Report deviations honestly. Since the schedule and budget are based on early estimates, deviations are to be expected — they are information, not shame. Your job is to show the consequences across the whole triangle and give decision-makers options, not to downplay problems until they can no longer be hidden.
Weigh changes against both the triangle and the benefits. When someone wants to add scope: don't just ask what it costs in time and money, but also what it adds in real value. Sometimes the answer is that the change is worth its price — but that should be a conscious choice, not something that sneaks in.
Agree on success criteria early. Talk to your sponsor right at the start about what success means beyond the triangle: what benefits should emerge, for whom, and when can they be measured? That way you avoid arguing over the definition once the project is over.
How to practice this
Reasoning about the iron triangle is rarely hard on paper. The hard part is the conversation: telling a sponsor that the schedule won't hold, or standing firm against pressure to promise something you don't believe in. In Project-simulator you practice exactly those conversations against AI counterparts in a safe environment, and get evidence-based feedback that points to your own wording. You can try it free for a week.
In Project-simulator you practice these conversations against an AI counterpart and get feedback grounded in research like this.
Try free for 7 days