And I thought you'd never ask. People haven’t really come up with a standard for benefits management, so it is easy to get caught up filling in endless forms and documents.  But as I said in the last post, you can make PRINCE2 very simple so that it works for you, and you can do the same with Benefits Management.

Benefits management is a very simple, common sense, thing to do.  We do it all the time, subconsciously, usually very well, and sometimes badly.

So how can you do it well?

John Thorp's book "the information paradox" is probably the foundation on which future benefits realisation has been based. Although it is based around IT projects (notoriously, with a 70% "failure" rate), there is much that can be applied to all environments.

John thesis on key concepts: fundamental definitions such as

If the Benefits Management Strategy is the high-level and relatively unchanging document, then with the Benefits Approach and Benefits Tracking process we get down to the nitty gritty of doing the doing.
Identifying Benefits
Profiling
Creating a High-Level plan and getting signup
Quantifying, and getting signup
Summarising and Detailing
Planning the realisation
the Benefits Realisation Plan
The Benefits Approach is about a whole lot more detail on how you will tackle this