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) 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
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.
Framework of (IT) technology strategy
Process of IT Strategy is simplified with framework constituted of IT Service Management (ITIL), 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
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
- 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
- Current IT departments strengths
- 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
- 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
- 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
- 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
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
- Floyd, S.W. & Wolf, C. (2010) 'Technology Strategy' In: Narayanan, V.K. & O'Connor, G.C. (eds.) Encyclopedia of technology and innovation management. West Sussex: Wiley pp. 125–128. ISBN 1-4051-6049-7
- Lawson, J (2006) "Delivering on Strategy: Those That Can...Do!! Those Who Simply Talk... Make Another Fine Mess", "Spectra – Journal of the MCA, June 2006" See Article Here.
- Strassmann, Paul A. (1990), The Business Value of Computers: An Executive's Guide, The Information Economic Press ISBN 0-9620413-2-7.
- The Human Capital Impact on e-Business: The Case of Encyclopædia Britannica. This case study is widely quoted example how technology has large impacts an overall organization's overall business strategy.
- J. C., Henderson; , N. Venkatraman. "Strategic alignment: Leveraging information technology for transforming organizations". IBM research. Retrieved 7 November 2013