Lessons on project governance from the CBA scandal
The CBA financial scandal is a classic example of the effect of setting the wrong performance targets. If your measurement systems focus on the wrong things, you will get exactly what you asked for: the wrong things!
Project management used to be defined as balancing the ‘iron triangle’ of time, cost and output (scope), these days quality, sustainability, safety and maintainability are frequently added to the mix. In the modern lexicon, project success is defined as delivering ‘stakeholder value’, or as fulfilling ‘stakeholder expectations’. In short, project success is multi-dimensional and depending on the requirements of the project’s stakeholders, some dimensions are more important than others.
The challenge for project controls professionals and PMOs is creating performance measures that focus on things that matter; as Einstein said: “Not everything that can be counted counts and not everything that counts can be counted.” And even more importantly, just because something is easy to measure accurately does not mean it really matters.
The CBA financial planners were measured and incentivised on the amount of profit they generated for the bank: CBA paid bonuses to staff that sold high-risk products and paid more bonuses (commissions) to staff that unnecessarily churned clients through package after package. The financial planners were not incentivised to look after the best interests of the customers.
As discussed in ‘The normalisation of deviant behaviours’ the real surprise is that anyone in the CBA management can pretend to be surprised when their financial consultants did exactly what they were being paid to do. The way the CBA Board has avoided taking any disciplinary actions against the staff and managers in their wealth management division tends to support this view, and suggests the KPIs and performance were largely in line with what was intended, the maximisation of bank profits rather than the optimisation of the clients’ wealth.
Paying bonuses and commissions to encourage specific behaviours is at the high end of the behaviour modifying tool kit available to management and can be very effective for clients if used ethically, however, KPIs and performance measurements don’t need to be linked to personal payments to be effective.
KPIs frame ‘success’
Most people are innately motivated to achieve success and will adapt their behaviours to be ‘successful’ against any reasonable KPI. The challenge is setting the right KPIs to drive the desired behavioural outcomes; as discussed in ‘What you measure is what you get’. Set the wrong KPIs and even with the best of intentions you can drive undesirable outcomes.
Why does this matter to PMOs and project management in general? I would suggest the overemphasis in most PMO reporting structures on the easy-to-measure KPIs of ‘on time’ and ‘on cost’ are very likely destroying value. If the project team is aware of the fact their project will be flagged as ‘Red’ on a RAG report if they don’t finish the development of a component by the end of the week, they will be motivated to cut corners, reduce quality, skip or minimise documentation and ignore long-term desirable characteristics such as maintainability to avoid the red flag. None of the shortcuts will be enough to cause the component to be rejected but in aggregate the quality of the item is reduced and long-term value lost.
This type of value/quality degradation is particularly easy to encourage in ‘soft projects’ such as IT coding. You can write a software module that ‘just works’ or you can spend a bit more time to clean up and document the code so it is easy to understand and maintain.
Similar options to create ‘just okay’ or ‘gone-through-the-motions’ outcomes can be encouraged in training material development, organisational change and a host of other soft projects by focusing on cost and time rather than value and benefits realisation. It is easy to finish an organisational change project ‘on time’ and ‘on budget’ (all KPIs green) if you don’t worry about actually creating the desired change in the minds and behaviours of the people in the organisation; ‘they all attended the workshop, it’s not our fault they did not buy into the initiative…’. The project was a ‘success’ but the change initiative was a failure?
Measuring value, quality and benefits contribution is much harder than measuring time and cost performance. However the question for PMO and executive management to answer is: do you want your projects to meet some arbitrarily set cost and time parameters or do you want to get some real and sustainable value out of the money being spent?
There are basically two choices:
- If you are happy just to spend money and expect nothing back, measure cost. If you actually want to realise sustainable value, measure the project’s value contribution.
- If you want to put pressure on your project team to perform, set a ridiculously short time for completion. All that will happen are costs will go up and quality will go down but the team will be ‘working to maximum capacity’. If you want to optimise costs and value, do some proper planning, add in appropriate contingencies for risk and measure the quality and usefulness of the project’s deliverables.
These are simple choices that need to be framed within the context of each project—there is no right answer! There will always be a limited number of projects where speed is an imperative, but for most a combination of better strategic planning so the work is started at the right time and/or simply allowing adequate time will produce far better quality outcomes at a significantly reduced cost.
Simply having an immovable deadline is not an excuse. The London Olympics infrastructure was started early, properly resourced from the beginning, used appropriate procurement systems and finished a year ahead of the opening ceremony with no fatalities. The key KPI was no injuries, most of the other outcomes revolved around this primary objective, which required proper training, skilled workforces, careful planning, clean working spaces and carefully thought through methods of working.
Contrast this success to similar projects in New Delhi and Rio de Janeiro where strategic decisions were not made at the right times, pressures to ‘increase speed’ developed and cost, quality and safety all suffered (or in the case of Brazil, are suffering).
Getting the balance right, setting the right KPIs and requiring management to have the right systems in place to achieve the organisation’s objectives is a governance imperative. The ‘governing body’ needs to decide what matters and then task their executive to implement the appropriate systems, KPIs and other measures.