---
title: Evaluate the benefits
acode: G01
principles:
  - 3
  - 5
---

The sponsor (or someone on their behalf) should spend a few hours in every post-project cycle, measuring the benefits realized from the project.

Besides the **expected benefits**, the sponsor should be actively looking for **unexpected benefits**, **potential benefits**, and **dis-benefits** as well. 


## Purpose 

We should evaluate the benefits of the project for the following reasons:

* It's a reminder for the sponsors and other stakeholders that projects are done to generate benefits.
* It helps us understand our environment and become more realistic in future projects. 
* It helps us find ways to increase benefits ([G02](../../g/02/)).


## Common pitfalls 

You can avoid some of the commonest issues by considering the following:

* The sponsor may have someone else evaluate the benefits, but the sponsor should have complete supervision over them and regard this activity as an important management activity that belongs to the higher management levels. 
* A vague, wordy description of the benefits doesn't serve any purpose. The result may be high‑level and probabilistic, but it has to stay meaningful and capable of being used in [G02](../../g/02/).
* Remember that benefits are not limited to monetary ones, and other benefits such as reputation, market share, opportunities, and gained knowledge should also be considered.


