Home | Redefining the Iron Triangle: What Actually Makes a “Good” Project?
Ask any traditional project manager what makes a project “good”, and they will likely point you toward the classic Iron Triangle: On Time, On Budget, and In Scope.
It is a comfortable, tidy definition. It fits beautifully onto a spreadsheet, looks spectacular in a steering committee deck, and allows everyone to tick their performance KPIs and move on.
But if you step out of the boardroom and look at the actual operations of an organisation, you will quickly realise that the Iron Triangle is a vanity metric. You can deliver a flawless technical installation on the exact day promised, without overspending by a single dollar, and still have the entire initiative end in catastrophic commercial failure.
Why? Because the software is live, but the people have quietly revolted. They are still using their shadow spreadsheets, their workarounds, and their old habits.
In the modern corporate landscape, a truly “good” project cannot be measured by the moment of delivery. A good project is defined by one thing: permanent, self-sustaining behaviour change that drives business value.
Most project frameworks are obsessively front-loaded. Millions are spent on the design, the vendor selection, and the build phases. Everyone treats the “Go-Live” date as the finish line.
But from a change management perspective, Go-Live isn’t the end, it is the starting gun.
A good project is designed from the outset with the understanding that human beings do not change their habits overnight. When you drop a new system or process into an environment, you are temporarily stripping away your team’s competence. You are making experienced, proud workers feel like clumsy beginners again.
If a project doesn’t include a deliberate strategy to support people through this inevitable “valley of despair,” the workforce will naturally seek the path of least resistance and abandon the tool. A good project builds the specific human infrastructure required to compress this transition period, actively accelerating the journey from initial frustration to confident, everyday adoption.
“The commercial value of a project isn’t unlocked when the code is deployed. It is unlocked when the frontline trusts the system enough to let it take a task off their plate.”
We are no longer living in an era where technology is just a static tool sitting on an employee’s desk. The modern workplace is a complex, fluid ecosystem where human capability and intelligent automation must live side-by-side.
A good project doesn’t just throw advanced tools or AI capabilities at a team and hope for the best. It actively considers how the workflow needs to be redesigned so that humans and smart systems complement each other rather than clash.
When projects fail in this arena, it is rarely because the technology is broken. It is because the project team treated it as a simple software installation rather than a structural workforce design challenge. If a new system adds an extra “cognitive tax” to an already exhausted employee, it will fail. A good project looks at the friction on the ground and deliberately structures roles so that technology removes the administrative toil, leaving the humans free to do the high-value, collaborative work they do best.
If your primary metric for project success is a log-in rate or a mandatory training completion stat, you are measuring compliance, not adoption.
A good project focuses on delivering felt relief to the end-user. Before a single line of code is written or a new process is mapped, the project team must understand the daily pressures of the frontline.
Does this initiative actually make a store manager’s roster building faster?
Does it reduce the administrative burden on a nurse at the end of a shift?
Does it give a corporate team their Friday afternoons back?
When people experience genuine relief from a change, you don’t need to force them to use it through heavy-handed corporate mandates. They will pull the change into their daily workflow willingly.
The hard truth for executive sponsors is that you cannot squeeze commercial value out of a burnt-out or confused workforce. Technical implementation is a binary event you flip a switch. True transformation is a human journey that requires energy, operational empathy, and sustained support.
The next time you evaluate an upcoming initiative, look past the Gantt charts and the vendor promises. Ask the tougher, change-focused questions:
Have we resourced the 90 days after launch as heavily as the build?
Are we equipping our middle managers to lead through the operational friction?
Have we designed the future workflow so our people and our technology actually thrive together?
The projects that shape the future aren’t the ones that move the fastest, they are the ones that move with the best information about their people.
The Outlier Group
A specialist Change Management agency who design and deploys change campaigns that are memorable and move the needle.
Recent Posts