How do you know whether an IT investment is value for money?
When an organisation decides to invest in a new website, software system or IT supplier, the conversation often starts with cost.
- How much will it cost to implement?
- What are the ongoing fees?
- Can we afford it?
All sensible questions. But there's another question that's just as important:
What will we get in return for the money we're spending?
Not every IT investment is optional. Sometimes an organisation has little choice but to make a change.
- A change in legislation might mean an existing system is no longer suitable.
- A supplier might withdraw support for software that the organisation relies on.
- A security problem might make continuing with the existing arrangements unacceptable.
In these circumstances, the business case is largely established. The organisation needs to act.
The question then becomes how to meet the requirement at a reasonable cost, rather than whether the investment is worthwhile in the first place.
But many IT decisions aren't quite so straightforward
Maybe your website looks great but it isn't delivering the goods.
Or you've noticed that your staff are struggling with a software system.
Or perhaps you're unhappy with your IT supplier but can't quite put your finger on why.
All of these are perfectly valid reasons to consider replacing your system or supplier, but do you really know that that's the right solution to the right problem?
Always start with:
What problem are you trying to solve?
Imagine an organisation considering replacing a software system.
Staff complain that it's difficult to use, managers are frustrated by the reports it produces, and someone has suggested that a newer system would make everyone more efficient.
Those might be good reasons for making a change. But before spending several thousand pounds, it's worth asking what the organisation actually needs the system to achieve.
Is it supposed to reduce administration? Improve customer service? Provide better management information? Make it easier for staff to collaborate?
And, crucially, is the existing system failing to achieve those objectives?
If it's doing its job reasonably well, perhaps the answer isn't a replacement. Maybe staff need some additional training, or perhaps a change to the way the system is configured would solve the problem.
If it is failing, or rather if you think it's failing, the first thing you need to do is check the facts.
- How much time are staff actually spending on tasks that the system is supposed to simplify? Perhaps you've assumed that a particular process takes hours every week, but nobody has measured it.
- How often does the system fail or produce incorrect information? Are these recurring problems or occasional frustrations?
- Are customers or service users being affected? Have you received complaints, lost business or missed opportunities that can be traced back to the system?
- And are the problems really caused by the technology, or could they be related to the way it's being used?
You've checked reality, and now...
You've established that something needs to change
Once you can demonstrate that your existing arrangements aren't meeting your needs, the cost of doing nothing may be substantial.
But you still need to justify why a potential spend of many thousands of pounds is worth the investment.
This is where a cost-benefit analysis comes in.
Suppose a replacement system costs £5,000 to implement, with another £2,000 a year in licence and support fees.
If the existing system is causing staff to waste ten hours a week on unnecessary administration, you can estimate what that time is costing the organisation. At an employment cost of £20 an hour, that's approximately £10,000 a year.
If the replacement system could eliminate most of that wasted effort, the investment starts to look much more attractive.
Of course, the calculation isn't quite that simple. You'll need to consider additional costs such as:
- Data migration and integration with existing systems.
- Staff training and the time needed to adapt to new ways of working.
- Disruption during implementation.
- Ongoing maintenance, upgrades and additional charges.
And then consider other benefits that might be harder to express in financial terms:
- More accurate information and fewer errors.
- Faster responses to customers or service users.
- Less frustration for staff.
- Better information to support management decisions.
- Improved reliability and fewer interruptions to work.
You also need to be realistic about the expected savings. Saving ten hours of staff time doesn't necessarily mean saving ten hours of salary costs. But it might mean those employees can spend more time on work that directly benefits the organisation.
Now you're starting to get a much clearer idea of whether the project is justifiable, and an evidence-based plan to take to the people who will approve the expenditure.
Whether that's a board of trustees, a management team or the owner of a small business, it's much easier to make a sound decision when you have evidence rather than assumptions.
The question isn't simply whether you can afford to make a change. It's whether the benefits justify the cost, and what might happen if you do nothing.
If you'd like help building your cost-benefit analysis, give me a call and we can work through it together.