Newsletters:

Developing a Technology Strategy - Page 1

Sep 2, 2008
By

Mike Scheuerman






Developing a technology strategy is not about figuring out what servers or networks to put into place, but rather putting in to place a framework within which a set of business applications can be deployed.

 

There are three things that you need to know when developing a technology strategy for your company:


 

       An in-depth understanding of the business strategies the company is pursuing;

       A vision of how technology will add value to business processes; and

       Technology use principles.

 

Business Strategy

 

Understanding and being conversant with the business strategy is critical to technology strategy development. Building a technology strategy without understanding the business strategy is like building a dam in a dry gully and hoping it will rain. You might get a lake, but more likely you’ll get a muddy pond.

 

IT is a large part of the engine that implements and reports on the success (or failure) of the business strategy.

 

Business Value

 

For each business process that uses technology (which nowadays is virtually all of them), there has to be some value that IT brings to the table. Whether it’s a more efficient process or a competitive advantage, the value must be defined by the user or business unit. IT is merely the tool that is used to achieve that value.

 

Business analysts and system analysts can help the business technology user analyze the process and can suggest ways that technology can be used to improve processes. However, those analysts are not there everyday trying to get a job done. The partnership between IT and the business user is crucial to building a solution to a business problem that is both workable and maintainable.

 

Technology Use Principles

 

When you’re defining the technology strategy, establishing a set of principles to measure any technology against makes decision making a bit easier. For example, if you want to ensure data consistency, the principle is that there will be a single source of data. You might call this the “enter once, use everywhere” principle. That bumper-sticker slogan is easy to remember. That is what you want if you don’t want to continuously explain why a particular decision was made.

 

This set of principles should be short and easily understood by both technical and non-technical users. The principles should be focused on reliability, consistency, and maintainability. Given a good set of principles, the decisions that are made by project sponsors, project managers, developers, and end users will almost always align with the general technology strategy.

 

Some principles that you might want to use are listed below.

 

Reliability - Measure twice, cut once. This maxim used in the building trades applies just as well to IT projects. Always double check to make sure that what you’re building is what the user wants and needs. Good planning will drastically reduce the number of changes near the end of a project where it gets very expensive to make changes.

 

Consistency - Enter once, use everywhere. This is a bit like normalizing a database. You only put the data in one place and then reference that as the “system of record.” This principle ensures that reports and information delivered are consistent across the entire organization.

Page 1 of 2


Tags: IT management, infrastructure, IT Leadership, CIO management,
 

0 Comments (click to add your comment)
Comment and Contribute

Your comment has been submitted and is pending approval.

Author:

Comment:

 (click to add your comment)

Comment and Contribute

Your name/nickname

Your email

Comment:

(Maximum characters: 1200). You have characters left.