I have discussed at length the identification and quantification of benefits, which includes a description of the benefit and an action plan to actually derive the benefit. The role of the IT department in this stage of the process is manifest. If the IT department wishes to add value, then they must also become involved in carrying out the action plan, managing progress towards objectives and doing their portion required in each action. They must also track progress towards achieving the benefits and report on that progress. They must also report on the benefits stream . Again I have a picture in my mind of a literal stream of benefits contrasted against a stream of costs (Figure 7.12).

Figure 7.12: Literal benefits stream

Is this too simple a view of the world? Perhaps na ve?

Interestingly, this simple view of costs versus benefits has been used in numerous presentations to business and IT people alike, because there are a few issues that need resolution when talking to IT:

• There is a big difference between promised benefits and actual benefits

• A benefits release programme is needed to convert promised benefits into actual benefits

• How do you know the actual benefits exist if you don t measure inputs to t he benefits stream?

• What are we doing to minimize the cost sinks?

• Is the net flow of benefits greater than the net flow of costs?

• Is the benefits stream getting wider as time goes...