Blog
Project Acceptance Is Not Project Success
Project acceptance is not project success. GPM’s current look back at Zwentendorf shows just how far apart these two states can lie: Austria’s nuclear power plant was technically complete, yet it never entered service after the referendum of 5 November 1978. 50.47 percent voted against commissioning it.
The lesson lies in governance, not in energy policy: a project can meet scope, schedule and technical acceptance and still miss its intended benefit. At Zwentendorf, the decisive acceptance question was settled only after most of the capital had already been committed.
Complete does not mean effective
In IT projects, the pattern is less dramatic, but it is common. A migration passes technical acceptance, yet the business works around the new process. A reporting product is live, but nobody uses it as a basis for decisions. A supplier delivers the agreed functionality, while the operating organisation has not clarified roles or data quality for running it.
Three layers therefore need to be governed separately:
- Deliverable: What has been demonstrably built, tested and accepted?
- Operational readiness: Who takes over processes, data, support and decisions from day one?
- Benefit and acceptance: Which behaviour or metric should change, and who confirms this outside the project team?
In complex software initiatives, I often see the first layer reported with precision, while the other two vanish into a closing slide. That simply shifts risk beyond go-live.
Test benefits before go-live
A 1978 referendum cannot be equated with an IT steering committee. That is precisely why the case works well as a mental model: decision-makers must not put off questions of legitimacy, use and long-term viability until the final acceptance.
In practice, every major outcome needs a benefit owner outside the project team from an early stage, measurable acceptance criteria and a timetable for non-technical decisions. In a migration reconciliation, the team should do more than compare planned against actual data. It should also document which business unit owns the data in the target process and which criteria release its use.
What project leaders should do now
Put three questions on the agenda of your next steering committee: Who will use the outcome, and from when? How will we measure the expected benefit? Which decision outside the project can still prevent impact? If the answers are only technical, acceptance has progressed further than governance. The relevant metric is not whether the project is complete, but whether its purpose actually starts in operations.