This technically could be the last section of your plan, this is where you take a high level look at the plan and existing challenges that may hamper your ability to deliver on any said item. Depending on who and how I.T. decisions are made in your organization could literally dismantle your strategy on many levels. I wrote on this topic back June 2009, it’s called I.T. Decisions – Who Makes Them In Your Organization?
Once you’ve finished this section you can then do an Executive Summary for the purposes of presenting to your Executive Team and or Board of Directors. Here is a short hypothetical example of this section:
A one year planning and budgeting cycle creates significant difficulties for the I.T. Department to execute the early stages of this plan.
- Hardware and software have to be upgraded or replaced regularly, either to take advantage of newer technologies or reduce maintenance fees. However, sometimes an upgrade would make long term sense but cannot be done because it is too large for a one year budget. This has resulted in a series of sub-optimal short term purchasing decisions being made.
- Recent budget cuts have forced a multi-year upgrade schedule to be differed resulting in perpetually out-of-date technology.
- Many projects take longer than one year to complete and require both tools and personnel at the start-up stage, but will not see significant results until the subsequent year.
- A new service is anticipated to be required by a department in a future year but the department lacks sufficient budget or approval to such an expenditure; however, there might be sufficient lead time for IT to prepare the infrastructure; does IT ” risk it ” and build the infrastructure anyway?
That’s just snippet of what you might put in this Planning Observations section, I suggest you pull your top three together to ensure you are covering the critical issues. You’ll want your IT leaders to be in the loop especially if you are seeking additional budget and it gets rejected, they may be able to assist you with other creative ways to turn the rejection around.
This is the third part of the Analysis section in our mock I.T. Strategic Plan. This section is all about observing and assessing what you have and what assets you may have. You might call it an inventory of which gives you a high-level snapshot of your organization, assets, liabilities and so on. Again, I am not going into great detail in these posts, they are intended to be quick references to give you an idea of what might go into each area and section of your plan.
This part is called Core Competencies, here are a couple of possible entries for your consideration:
1. Good people; qualified, experienced and possibly well trained.
2. Infrastructure; This would be software and hardware that is well integrated.
3. Ability to relate or communicate the services that IT can provide
4. You may have adequate funding available to meet objectives
Again, each of these are just examples of what might be in this part of your plan. The list can be as long as you want it but most likely you will only have a few items to enter here. I.T. Plans take very different shapes depending on the organization and who is building it, it’s a perspective and point of view…or a summary of how you see the needs of the organization and how you view the use of technology.
Next I will go over S.W.O.T. (Strengths, Weaknesses, Opportunities and Threats). Another area of observation and reflection, until next time.