Dan Brody Chief Information and Technology Officer CITO

Wash – Rinse – Spin Repeat Project Budget Time

CIO/CTO are managing budgets, proposals, and projects case making season now. It comes around every year to go through your wash cycle. A time when business cases start to being prepared for next year’s projects, and it seems as though every year I am asked for tips on how to best “sell” a proposal "Wash - Rinse - Spin." While I understand what’s asked, it concerns me to hear it put in those terms.

A business case should clearly set out the benefits of what is proposed along with the expected costs, and some supporting elements. It should then be judged alongside other business cases on its merits, and either gets approved or not. If the business case demonstrates clear benefit, then it shouldn’t need selling; and if it doesn’t, then it shouldn’t be positioned (or sold) as if it does!

The purpose of project justification

The fundamental issue with many project justification processes is that they aren’t entirely based on what is right for the organization, but have decisions clouded by force of personality and political influences. This article is not about how to improve the process, so we’ll save that for another day. But it’s easy to understand why projects are positioned to try and appeal to those stakeholders whose views and preferences seem to carry more weight.

Let’s try to put that to one side and focus on what the project justification process should be about. The project proposal or business case needs to address just a few basic elements, most importantly the following three:

  1. What benefits will the project deliver to the organization? That might be revenue growth or cost savings, but should be expressed in financial terms wherever possible. It should also address when the benefit occurs to allow for accurate calculation of the return on investment.
  2. What costs will the project incur? The obvious cost piece is the project itself, but this should also consider ongoing support and maintenance costs. Again, an indication of when the various costs will occur should also be included.
  3. How does the project align with organizational strategy? The organization will have established some strategic priorities, and an explanation of how the proposed initiative aligns with those should provide.

It’s clear to see how these elements contribute to the project selection and approval process--the projects that align with the corporate priorities and deliver the best net return are most likely to be approved. There will be exceptions, of course--regulatory projects, maintenance initiatives, etc. But the “game changers” will be passed based on the elements above.

Project proposals will all have their supporters--the people and groups that came up with the ideas and developed the business cases. The champions of these proposals have a personal stake in the project approval -- not just ego and reputation, but also more tangible factors like department budgets, resource levels, particular position, etc. It is very tempting to overstate the benefits, understate the costs and make the project sound as though it closely aligned with the organization’s goals and objectives. Then what might be the case--to “sell” the proposal rather than just present it and allow it to live or die on its own merits.

Controlling the spin

Reduce the potential for abuse in the justification project stage, and organizations should consider some different steps. One of the simplest--but also one of the most effective--is to provide standard templates for proposals that focus on numbers and how those numbers are developed rather than allowing for a lot of free text descriptions and discussion that may not add value. Helping to make the review and comparison of proposals simpler because there is more consistency between business cases. The downside of this approach is that it makes a proposal rather “sterile” and removes the opportunity to explain what may be new and complex ideas.

The next step that organizations should consider is an independent review of numbers before submission to the decision-making process. An informal audit by the finance team of the cost and benefit claims can help to identify any errors or unrealistic assumptions and will also ensure that there is consistency in the numbers used for the different financial calculations (things like exchange rates, the cost of capital, etc.).

The final step that can is the simplest but rarely is done. That is simply to measure the actual benefits and costs against the business case. In many organizations, the business case seems to be ignored as soon as a project is approved. By holding sponsors accountable for the numbers that they claimed in their proposals, a lot of the more blatant salesmanship can be eliminated.

Proposal/Project justification is a competitive business--there will always be more proposals than there is money available for investment, and it’s easy to understand why people try to gain an advantage over competing proposals. It’s the organization’s responsibility to ensure that this “noise” is eliminated and that all proposals compete equally for the available funding.

cropped-CIO_Brody1.png@CIOBrody Consulting
Daniel Brody
Contact Me


%d bloggers like this: