¶ … Business Strategy Aligning IT and Business Strategy

An IT strategy focused on maintaining a cutting edge technology position is not the most effective way to support any kind of overall business strategy. To refute this argument, this essay examines other IT strategies.

Many IT organizations struggle to develop an effective IT strategy. Typically, businesses exhibit confusion about what goals and components make up an IT strategy, and about the process of obtaining business input and developing a long-term strategy that serves the business' planning needs (Gartner, 2011).

According to Gartner's research, most IT organizations are unable to develop a business-strategy-driven IT strategic plan because they use a bottom-up planning process, asking business units what projects they need. Instead, a more effective approach would be integrating the IT team into the organization's upfront, top-down business planning processes (2011).

Gartner argues that IT strategy is effective when it is directly linked to how the organization makes day-to-day investment and prioritization processes. Moreover, IT strategy initiatives are effective only when business input is included. In the absence of a clearly articulated business strategy, or when the CIO does not know how to plan for and respond to multiple business requirements from multiple shared-service business customers, IT strategy is less effective (2011).

Glaser argues that developing an IT strategy using a dogmatic approach is dangerous and results in an incomplete or misaligned IT strategy. The basic purpose in developing an IT strategy is to insure that there is a well-defined relationship between IT investment decisions and the organization's overall strategies, goals, and objectives. When an organization defines the IT agenda incorrectly or partially correctly, such as happens by focusing on a cutting edge technology approach to the exclusion of all others, it runs the risk that significant resources will be misdirected. Glaser notes that "Being on time, on budget, and on specification is of diminished utility if the wrong thing is being done" (p. 1).

Numerous...

Gartlan and Shanks (2007) conducted a survey of 69 CIOs and CEOs from large and medium-sized Australian organizations. For the purposes of their research, they defined successful alignment as evidenced by both IT and business strategy demonstrating "a planned alliance, which then leads to tangible, successful, business-focused outcomes" (p. 117). Their definition clearly relies on the premise that IT delivers business value, independent of a specific technology position.
Gartlan and Shanks' research identified ten factors that promote business and IT strategy alignment. Their analysis indicated that, of the various factors which contribute to successful alignment, the most important process factors were "having a process that promotes clarity and consistency and a process that ensures IT goals are linked with business goals" (p. 131). Their conclusion is technology-neutral.

Other processes must combine to make IT strategy and business strategy alignment successful. The IT strategy process must be purposefully designed and it must also have an owner or sponsor. It must also be integrated with other processes, such as budget, portfolio rationalization, and enterprise architecture planning and systems implementation. IT strategy must also be managed using clearly defined metrics and mechanisms (Hajela, 2005).

Study after study shows that the alignment of business and IT continues to be a top priority for CIOs. Better service management has been proposed to remedy business/IT alignment issues. Successful alignment begins with effective collaboration, which in turn requires adherence to three primary principles: trust, communication, and context. According to Mangold, trust between IT and business units is based on having no hidden agendas, and having full disclosure of issues. Effective communication requires that all parties have the same understanding of the terminology used in discussions. A shared context means that while IT and the business units may not have the same understanding of the components in a project, they must have identical understanding of the components for which…