- People treat benefits as a box to tick on the business case, deflating or inflating them to facilitate project approval.
- Even if benefits are properly defined, they are usually forgotten once the project is underway.
- Subsequent changes to project scope may impact the viability of the project’s business benefits, resulting in solutions that do not deliver expected value.
Our Advice
Critical Insight
- It is rare for project teams or sponsors to be held accountable for managing and/or measuring benefits. The assumption is often that no one will ask if benefits have been realized after the project is closed.
- The focus is largely on the project’s schedule, budget, and scope, with little attention paid to the value that the project is meant to deliver to the organization.
- Without an objective stakeholder to hold people accountable for defining benefits and demonstrating their delivery, benefits will continue to be treated as red tape.
- Sponsors will not take the time to define benefits properly, if at all. The project team will not take the time to ensure they are still achievable as the project progresses. When the project is complete, no one will investigate actual project success.
Impact and Result
- The project sponsor and business unit leaders must own project benefits; IT is only accountable for delivering the solution.
- IT can play a key role in this process by establishing and supporting a benefits realization process. They can help business unit leaders and sponsors define benefits properly, identify meaningful metrics, and report on benefits realization effectively.
- The project management office is ideally suited to facilitate this process by providing tools and templates, and a consistent and comparable view across projects.
- Project managers are accountable for delivering the project, not for delivering the benefits of the project itself. However, they must ensure that changes to project scope are assessed for impact on benefits viability.