Technology strategy

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

Technology strategy (information technology strategy or IT strategy) is the overall plan which consists of objectives, principles and tactics relating to use of technologies within a particular organization. Such strategies primarily focus on the technologies themselves and in some cases the people who directly manage those technologies. The strategy can be implied from the organization's behaviors towards technology decisions, and may be written down in a document.

Other generations of technology-related strategies primarily focus on: the efficiency of the company's spending on technology; how people, for example the organization's customers and employees, exploit technologies in ways that create value for the organization; on the full integration of technology-related decisions with the company's strategies and operating plans, such that no separate technology strategy exists other than the de facto strategic principle that the organization does not need or have a discrete 'technology strategy'.

A technology strategy has traditionally been expressed in a document that explains how technology should be utilized as part of an organization's overall corporate strategy and each business strategy. In the case of IT, the strategy is usually formulated by a group of representatives from both the business and from IT.[1] Often the Information Technology Strategy is led by an organization's Chief Technology Officer (CTO) or equivalent. Accountability varies for an organization's strategies for other classes of technology. Although many companies write an overall business plan each year, a technology strategy may cover developments somewhere between 3 and 5 years into the future.

The United States identified the need to implement a technology strategy in order to restore the country's competitive edge. In 1983 Project Socrates, a US Defense Intelligence Agency program, was established to develop a national technology strategy policy.


Effective strategy[edit]

For a strategy to be effective, it should answer questions of how to create value, deliver value, and capture value:

  • In order to create value one needs to trace back the technology and forecast on how the technology evolves, how the market penetration changes, and how to organize effectively.
  • To capture value one should know how to compete to gain a competitive advantage and sustain it, and how to compete in case that standards of technology is important.
  • The final step is delivering the value, where firms defines how to execute the strategy, make strategic decisions and take decisive actions. The Strategic Alignment Process is a step by step process that helps managers stay focused on specific task in order to execute the task and deliver

Business–technology alignment[edit]

Primary objective of designing technology strategy is to make sure that the business strategy can be realized through technology and technology investments are aligned to business. There are frameworks (e.g. ASSIMPLER[3]) to study current and future business strategy, assess business-IT alignment on various parameters, identify gaps, and define technology roadmaps and budgets. Technology strategy facilitates the attainment of a company's vision through alignment of its information technology strategy with its business strategy.

The important components of information tech-strategy is information technology and strategic planning working together.

The IT strategy alignment is the capability of IT functionality to both shape, and support business strategy (Henderson and Venkatraman, 1993).

The degree to which the IT mission, objectives, and plans support and are supported by the business mission, objective, and plans (Reich and Benbasat, 2000)

Meta-model of (IT) technology strategy[edit]

Aligned with Statement Of Applicability (SOA) approach, IT strategy is composed of IT Capability Model (ITCM) and IT Operating Model (IT-OM) as proposed by Haloedscape IT Strategy Model.[4]

Framework of (IT) technology strategy[edit]

Process of IT Strategy is simplified with framework constituted of IT Service Management (ITSM[5]), Enterprise Architecture Development (TOGAF) and Governance (COBIT). IT Strategy is modeled as vertical IT service applied to and supported by each horizontal layers of SOA architecture. For details, refer Haloedscape IT Strategy Framework.

Typical structure of a (IT) technology strategy[edit]

The following are typically sections of a technology strategy:

  • Executive Summary – This is a summary of the IT strategy
    • High level organizational benefits
    • Project objective and scope
    • Approach and methodology of the engagement
    • Relationship to overall business strategy
    • Resource summary
      • Staffing
      • Budgets
      • Summary of key projects
  • Internal capabilities
    • IT project portfolio management – An inventory of current projects being managed by the information technology department and their status. Note: It is not common to report current project status inside a future-looking strategy document. Show Return on Investment (ROI) and timeline for implementing each application.
    • An catalog of existing applications supported and the level of resources required to support them
    • Architectural directions and methods for implementation of IT solutions
    • Current IT departmental

Includes a SWOT Analysis SWOT_analysis

  • Strengths
    • Current IT departments strengths
  • Weaknesses
    • Current IT department weaknesses
  • External Forces
    • Summary of changes driven from outside the organization
    • Rising expectations of users
    • List of new IT projects requested by the organization
  • Opportunities
    • Description of new cost reduction or efficiency increase opportunities
      • Example: List of available Professional Service contractors for short term projects
    • Description of how Moore's law (faster processors, networks or storage at lower costs) will impact the organization's ROI for technology p
  • Threats
    • Description of disruptive forces that could cause the organization to become less profitable or competitive
    • Analysis IT usage by competition
  • IT Organization structure and Governance
    • IT organization roles and responsibilities
    • IT role description
    • IT governance
  • Milestones
    • List of monthly, quarterly or mid-year milestones and review dates to indicate if the strategy is on track
    • List milestone name, deliverables and metrics


A technology strategy document is usually designed to be read by non-technical stakeholders involved in business planning within an organization. It should be free of technical jargon and information technology acronyms.

The IT strategy should also be presented or read by internal IT staff members. Many organizations will circulate prior year versions to internal IT department for feedback. The feedback is used to create new annual IT strategy plans.

One critical integration point is the interface with an organization's marketing plan. The marketing plan frequently requires the support of a web site to create an appropriate on-line presence. Large organizations frequently have complex web site requirements such as web content management.

Relationship between strategy and enterprise technology architecture[edit]

A technology strategy document typically refers to but does not duplicate an overall enterprise architecture. The technology strategy may refer to:

  • High-level view of logical architecture of information technology systems
  • High-level view of physical architecture of information technology systems
  • Technology rationalization plan

See also[edit]


  1. ^ Information Technology Strategy Projects Archived 2010-07-31 at
  2. ^ Bernd, Bernd. Strategy Execution. 
  3. ^
  4. ^ Singh, Neeraj (2015). Essential strategy and enterprise architecture : strategy and enterprise architecture for business-aligned, SOA-based IT solution developed through different phases of preliminaries & foundation, business architecture, information system architecture, application & data architecture, platform & technology architecture. Middletown, DE: Haloedscape Haves. ISBN 978-1-5078-4014-6. 
  5. ^