Benefits
What can I say that hasn’t already been said by Neil Harrison in his excellent LinkedIn post a few weeks ago? I love his analogy of a bike (the output), the outcome and the benefits https://www.dhirubhai.net/feed/update/urn:li:activity:6699214120450854912/
It’s obvious that we should identify benefits up front when considering project ideas. The benefits (no pun intended) are twofold.
1) We want to make sure that we get what we paid for. That the assumptions in the business case stack up and our investment was a success.
2) It’s very important from a lessons learnt perspective. What IF, over time, our projects continuously fail to realise the benefits that they promised? What should we do? The project ideas would likely need more analysis and clear metrics BEFORE starting. This way, we can stop a project early if it’s failing to meet expectations and to stop throwing good money after bad. We can also invest in the types of projects that will deliver benefits.
For those that are interested in P3M3 (maturity assessments) this should be significant. By reusing the project outputs for the new project inputs means that we can achieve 5 out of 5 in maturity.
That’s the last of the topics on my list... for now
Human-led AI Change Management | Advising Leaders on AI Adoption | Helping You Discover Your ‘Why’ for AI, Ensuring Measurable Results with Positive People | Founder, The Adaptologists
4 å¹´That's very kind of you Stuart, and thank you for sharing the link to my post. I'll be sure to check out articles 1-12!