3 replies
by james r linn
First thing to remember is that it should be fundamentally linked to the corporate strategic plan. In the absence of a formal corporate plan, you will have to detrmine what the companies long term goals are. Your strategic plan should address how ISwill help the company acheive those goals.
The best place to start with a current "AS IS" analysis. This should take an objective look at what you do to day and analyze it with a SWOT analysis(Strengths, Weaknesses, Opportunities Threats).
Then move to external factors - industry trends etc. which may influence how you provide services.
Bring it all together with an analysis of what the corporate goals are, how you currently support those goals, how you project you could better support those goals(Gap analysis), and finally how you would move IS from where you are to where you want to be.
Ideally you should align your planning horizon to whatever horizon the company uses. If you've never done a strategic plan, keep the horizonshort, and extend it out a little more every cycle. IS often starts with a 1 year cycle(which isn't strategic) the first year, 2 years the second year, 3 years the third year. Frankly I don't see much value in looking too far beyond three years, given the rapid nature of change in technology.
Thats just a start.
Many training companies have courses - I took one at the Canadian Management Centre which is affiliated with the American Management Association.
James
by http://stobie.home.sprynet.com/work/
You should be working from a Strategic Business Plan (SBP) that describes what the enterprise wants to be doing in the future.
Information Systems is only one part of the Strategic Technology Plan (STP). Often there are trade-offs that can be made between different types of technologies to accomplish the same effect. The STP should provide a vision on how the technology will be used to bring about the enterprise vision. The STP should be flexible to adapt to new technologies but go out far enough to address the entire SBP.
In order to address migration, every STP, should acknowledge the as-is state, whether inside the document or to reference documents, and provide a migration path from the as-is to the visionary state.
The STPshould be used by all technology (IT and other) development group to guide their development and should be a living document evolving as the enterprise evolves.
The STP focuses heavily on architecture, that is how things work. There may be supporting documents describing alternatives and why particular one where chosen. The STP may include alternatives to be decided later. The STP should include or reference an enterprise model describing at least how it should work and reference a current model of as-is.
There is a lot more that can be said. This is my speciality and has to be customized for every enterprise.
by jklein
One suggestion is to take a good look at what your compeditors are offering their clients as IT services. Gage yourself against what their level of service is.
There are industry benchmark consultants who can give you an estimatation of where yourcompeditors are technologically and how you rank in the industry. This will provide you with an idea of where your company should be.
I try to keep the strategic planning document as technically brief as possible. Management only gets confused with technospeak. KISS is the way to go. I just point out the advantages and how this tech move can increase productivity, lower cost while removing risk.
This discussion is closed to new replies.
Trending IT Employment posts
Sort by Trending