The main aim of preparing that first IT budget is presenting an IT strategy proposal with a determined value.
The board can agree or disagree on the value you placed on the proposal, so it’s your job is to prepare the IT budget that the board will agree with. If you’ve never done this before, here are a few pointers on preparing your first IT budget.
Your first IT budget should give you a chance to demonstrate how you can improve things for the company.
Take a look at how IT has been running until now, and then answer the following:
To get the board on your side, you will have to align your plans with theirs.
Data is your most valuable asset. If you’re new to this position, acquire data from previous years and see what your predecessor has been spending on the most.
You might see how you would make things different immediately.
If there are no previous budgets to look at and you’re in charge of making the first IT budget ever, then industry research on technology spending and budget allocation will provide a good measure of how you should set things up.
You might be in charge of making your first IT budget, but you are not the only one in the IT department.
Collaborate with other IT professionals and have quick meetings where you can gather their input on the most pressing matters.
Invite them to articulate their needs and why they think their issue should be addressed first. You might find that you need more staff, replace end-of-cycle gear, or improve your cybersecurity with a cyber risk employee training.
A budget that just demands is a budget set to fail. The strongest argument is one that’s backed up by actual numbers.
When preparing your first IT budget, don’t just list how much money you need for each of your operational, ongoing, and capital costs.
Think in terms of return on investment (ROI). When the board sees growth in revenue, or savings, or more efficient operations, you will find a common ground much faster.
Don’t forget to quantify the IT and cyber risks and solutions to the decision-makers that the company could be facing. Doing this in financial impact is a language they will understand best (that’s where you should use Boardish!)
The number one reason why IT budgets are not approved is because the board doesn’t understand the inherent risk the company might be in. Not just cybersecurity risk, but business risks including a lack of mobility, unscalability etc.
You can solve this by presenting several possible scenarios right then and there. The board members can see for themselves how much more it costs to keep outdated technology, bad security practices, or allow BYOD without any real policies for example. And this makes for faster, and more reactive decision making.
Making the first IT budget requires some good research and analytical skills – get the needed data and analyse it. You don’t have to do everything alone. There’s plenty of tools that will assist you and help you get approval.