‘A’ versus ‘B’
by jed simms on August 25, 2009
Why you need to be a member of the ‘B’ team!
You can
- ‘A’ deliver the project
- ‘B’ deliver the business outcomes, benefits and value.
Delivery of ‘A’ does not automatically result in the delivery of ‘B’.
‘B’ is not a subset or subsequent step to ‘A’ but the reason for ‘A’.
‘B’ therefore needs to drive ‘A’ to ensure the business outcomes are realizable.
This is rarely the case.
‘A’ is usually defined, managed and delivered (with varying degrees of success).
‘B’ is usually defined in the business case and then hoped for as a consequence of delivering ‘A’.
‘B’ is seen as a means of justifying ‘A’, not as the focus of ‘A’.
‘B’ is harder to achieve than ‘A’.
Yet ‘B’ is where the value is and is the true measure of project success.
Organizations good at delivering ‘A’ are often not good at delivering ‘B’.
Most don’t even try.
Most organizations still focus on ensuring ‘A’ is delivered and hope for ‘B’.
Most still don’t see the difference.
But the basics do not change.
‘B’ is why we do projects (‘A’).
Achievement of ‘B’ is the measure of success.
Achievement of ‘B’ delivers the business value.
‘B’ needs to be the starting and end point, driving ‘A’.
It is time to redirect our focus onto ‘B’ and make everyone part of the ‘B’ team.
It is time for a new Project Delivery Science™.
What do you think? Please post your comments.
Leave your comment