IT Vision Thing
May 23, 2008
As a SMB business manager, I am sure you have had to deal somewhat with vision.
Perhaps for an elevator pitch for VC capital,
Maybe for an IPO prospectus.
Maybe even just so that your customers know what you actually do.
Do you have an IT vision as well?
This vision should be a lesson in simplicity, it should have no jargon or technobabble. But it should be a clearly articulated road map for the future.
And yes, it should be revisited regularly. Now this vision will not be as complex or tough to build as the vision required for some change initiative, but it should exist and be articulated and communicated by senior IT staff as required.
As a post I did here states, complexity causes instability, instability causes breakage, and breakage causes downtime and costs money.
Simply put, this vision will articulate what technology platforms and tools your business is going to utilize. And it should be the road map that limits this complexity.
Unfortunately, in the SMB space, we often find IT complexity that is completely beyond the bounds of reason for our organization sizes.
By complexity, I mean technology sprawl. There is absolutely no reason for the average SMB to have more different kinds of technologies, tools and architectures than a company of IBM’s size has.
That may be exaggerating – but it happens all too often.
A year or so ago, I remember speaking to an IT Manager at an SMB sized organization that had several facilities and a good customer base spread along a couple of lines of business. This business was using three different database management systems, four or five different classes of server operating systems, and several different tools that actually performed the same function for different operating units.
Consider just the direct upfront licencing costs of all of this software and hardware, Now consider the expertise and time required in the care, feeding and maintenance of all of these. And we will avoid even considering that a customer of two business units will have separate customer records from different tools each unit uses.
This organization did not have an articulated IT vision. So one business unit manager wanted a particular tool that happens to run on MS WIndows Server and MS SQL Server, while another business manager wanted a similar tool that ran on Linux and Oracle Corporations Database Software. And a third enterprise tool ran on a Novell server etc etc.
Your technology road map vision may be partially dictated by customer or supplier linkages, or you may be lucky and can define it the way you prefer from the ground up. The important thing is to define it. Regardless of which architecture and platforms you choose, emphasizing that these are the corporate standards will reduce the costs associated with end less sprawl.
Will there be deviations? possibly. But my advice to you is to demand a good business case to support it.
You can subscribe to this blog by clicking the RSS icon on the Home Page!