Technology strategy

Last updated

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. [1] 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. The strategy includes the formal vision that guides the acquisition, allocation, and management of IT resources so it can help fulfill the organizational objectives. [2]

Contents

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. [3] Often the Information Technology Strategy is led by an organization's Chief Technology Officer (CTO) or equivalent. [4] 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 three and five 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. [5]

Effective strategy

A successful technology strategy involves the documentation of planning assumptions and the development of success metrics. [6] These establish a mission-driven strategy, which ensures that initiatives are aligned with the organization's goals and objectives. [6] This aspect underscores that the primary objective of designing technology strategy is to make sure that the business strategy can be realized through technology and that technology investments are aligned with business. Some experts underscore the successful technology strategy is one that is integrated within the organization's overall business strategy not just to contribute to the mission and vision of the company but also get support from it. [7]

There are frameworks (e.g., ASSIMPLER [8] ) available that provide insights into the current and future business strategy, assess business-IT alignment on various parameters, identify gaps, and define technology roadmaps and budgets. These highlight key information, which include the following:

For a strategy to be effective, it should also 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. Capturing value requires knowledge how to gain 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 define 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 value.

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. [9]

Framework of (IT) technology strategy

Process of IT Strategy is simplified with framework constituted of IT Service Management (ITSM [10] ), 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. [9]

Typical structure of a (IT) technology strategy

The following are typically sections of a technology strategy:

Includes a SWOT Analysis SWOT analysis

Audience

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.

Implementation

The implementation of technology strategy will likely follow the conventional procedure taken when implementing a business strategy or an organization's planned changes within the so-called change management framework. Fundamentally, it is directed by a manager who oversees the process, which could include gaining targeted org. [11] For instance, in the area of systematic exploration of emerging technologies, this approach help determine the relevance and opportunities offered by new technologies to business through its well-defined assessment mechanisms that can effectively justify adoption. [7]

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:

See also

Notes

  1. ↑ Mistrik, Ivan; Tang, Antony; Bahsoon, Rami; Stafford, Judith (2012). Aligning Enterprise, System, and Software Architectures. Hershey, PA: IGI Global. p. 17. ISBN   9781466621992.
  2. ↑ Senft, Sandra; Gallegos, Frederick (2010). Information Technology Control and Audit, Third Edition. Boca Raton, FL: CRC Press. p. 204. ISBN   9781420065503.
  3. ↑ Information Technology Strategy Projects Archived 2010-07-31 at archive.today
  4. ↑ Donaldson, Scott; Siegel, Stanley; Donaldson, Gary (2012). CTOs at Work. New York: Apress. p. 9. ISBN   9781430235934.
  5. ↑ Bernd, Bernd. Strategy Execution.
  6. 1 2 Hoque, Faisal; Walsh, Lawrence; Mirakaj, Diana; Bruckner, Jeffrey (2011). The Power of Convergence: Linking Business Strategies and Technology Decisions to Create Sustainable Success. New York: American Management association. p. 98. ISBN   9780814416952.
  7. 1 2 Lowe, Paul (1995). Management of Technology: Perception and opportunities. London: Chapman & Hall. p. 70. ISBN   0412643707.
  8. ↑ "ASSIMPLER EA Framework - Making Life Simpler for an Enterprise".
  9. 1 2 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.
  10. ↑ "Definition: ITSM (IT Service Management) • Join Us! »". servicemanagers.org. Archived from the original on 2017-12-21.
  11. ↑ Baker, David (2004). The Strategic Management of Technology: A Guide for Library and Information Services. Oxford: Chandos Publishing. p. 214. ISBN   1843340429.

Related Research Articles

Information technology (IT)governance is a subset discipline of corporate governance, focused on information technology (IT) and its performance and risk management. The interest in IT governance is due to the ongoing need within organizations to focus value creation efforts on an organization's strategic objectives and to better manage the performance of those responsible for creating this value in the best interest of all stakeholders. It has evolved from The Principles of Scientific Management, Total Quality Management and ISO 9001 Quality Management System.

Information technology service management (ITSM) are the activities performed by an organization to design, build, deliver, operate and control IT services offered to customers.

Enterprise architecture (EA) is a business function concerned with the structures and behaviours of a business, especially business roles and processes that create and use business data. The international definition according to the Federation of Enterprise Architecture Professional Organizations is "a well-defined practice for conducting enterprise analysis, design, planning, and implementation, using a comprehensive approach at all times, for the successful development and execution of strategy. Enterprise architecture applies architecture principles and practices to guide organizations through the business, information, process, and technology changes necessary to execute their strategies. These practices utilize the various aspects of an enterprise to identify, motivate, and achieve these changes."

A business case captures the reasoning for initiating a project or task. Many projects, but not all, are initiated by using a business case. It is often presented in a well-structured written document, but may also come in the form of a short verbal agreement or presentation. The logic of the business case is that, whenever resources such as money or effort are consumed, they should be in support of a specific business need. An example could be that a software upgrade might improve system performance, but the "business case" is that better performance would improve customer satisfaction, require less task processing time, or reduce system maintenance costs. A compelling business case adequately captures both the quantifiable and non-quantifiable characteristics of a proposed project. According to the Project Management Institute, a business case is a "value proposition for a proposed project that may include financial and nonfinancial benefit."

<span class="mw-page-title-main">Business process re-engineering</span> Business management strategy

Business process re-engineering (BPR) is a business management strategy originally pioneered in the early 1990s, focusing on the analysis and design of workflows and business processes within an organization. BPR aims to help organizations fundamentally rethink how they do their work in order to improve customer service, cut operational costs, and become world-class competitors.

Enterprise risk management (ERM) in business includes the methods and processes used by organizations to manage risks and seize opportunities related to the achievement of their objectives. ERM provides a framework for risk management, which typically involves identifying particular events or circumstances relevant to the organization's objectives, assessing them in terms of likelihood and magnitude of impact, determining a response strategy, and monitoring process. By identifying and proactively addressing risks and opportunities, business enterprises protect and create value for their stakeholders, including owners, employees, customers, regulators, and society overall.

Business analysis is a professional discipline focused on identifying business needs and determining solutions to business problems. Solutions may include a software-systems development component, process improvements, or organizational changes, and may involve extensive analysis, strategic planning and policy development. A person dedicated to carrying out these tasks within an organization is called a business analyst or BA.

A federal enterprise architecture framework (FEAF) is the U.S. reference enterprise architecture of a federal government. It provides a common approach for the integration of strategic, business and technology management as part of organization design and performance improvement.

<span class="mw-page-title-main">Enterprise architecture framework</span> Frame in which the architecture of a company is defined

An enterprise architecture framework defines how to create and use an enterprise architecture. An architecture framework provides principles and practices for creating and using the architecture description of a system. It structures architects' thinking by dividing the architecture description into domains, layers, or views, and offers models – typically matrices and diagrams – for documenting each view. This allows for making systemic design decisions on all the components of the system and making long-term decisions around new design requirements, sustainability, and support.

IT portfolio management is the application of systematic management to the investments, projects and activities of enterprise Information Technology (IT) departments. Examples of IT portfolios would be planned initiatives, projects, and ongoing IT services. The promise of IT portfolio management is the quantification of previously informal IT efforts, enabling measurement and objective evaluation of investment scenarios.

<span class="mw-page-title-main">Business architecture</span> Business discipline

In the business sector, business architecture is a discipline that "represents holistic, multidimensional business views of: capabilities, end-to-end value delivery, information, and organizational structure; and the relationships among these business views and strategies, products, policies, initiatives, and stakeholders."

An operating model is both an abstract and visual representation (model) of how an organization delivers value to its customers or beneficiaries as well as how an organization actually runs itself.

Business–IT alignment is a process in which an organization integrates and utilizes information technology (IT) to achieve business objectives. It is the ability of IT to produce business value which means the process of establishing an environment where both IT and business professionals are capable of working together in order to achieve common goals in any specific area of work.

<span class="mw-page-title-main">Dennis E. Wisnosky</span>

Dennis E. Wisnosky is an American consultant, writer and former chief architect and chief technical officer of the US DoD Business Mission Area (BMA) within the Office of Business Transformation. He is known as one of the creators and initiators of the Integrated Definition (IDEFs) language, a standard for modeling and analysis in management and business improvement efforts.

<span class="mw-page-title-main">Solution architecture</span> Term used in information technology

Solution architecture is a term used in information technology with various definitions, such as "a description of a discrete and focused business operation or activity and how IS/IT supports that operation".

Business systems planning (BSP) is a method of analyzing, defining and designing the information architecture of organizations. It was introduced by IBM for internal use only in 1981, although initial work on BSP began during the early 1970s. BSP was later sold to organizations. It is a complex method dealing with interconnected data, processes, strategies, aims and organizational departments.

<span class="mw-page-title-main">FDIC Enterprise Architecture Framework</span>

FDIC Enterprise Architecture Framework was the enterprise architecture framework of the United States Federal Deposit Insurance Corporation (FDIC). A lot of the current article is about the enterprise architecture framework developed around 2005, and currently anno 2011 out-of-date.

Business process management (BPM) is the discipline in which people use various methods to discover, model, analyze, measure, improve, optimize, and automate business processes. Any combination of methods used to manage a company's business processes is BPM. Processes can be structured and repeatable or unstructured and variable. Though not required, enabling technologies are often used with BPM.

Capability management is the approach to the management of an organization, typically a business organization or firm, based on the "theory of the firm" as a collection of capabilities that may be exercised to earn revenues in the marketplace and compete with other firms in the industry. Capability management seeks to manage the stock of capabilities within the firm to ensure its position in the industry and its ongoing profitability and survival.

The history of business architecture has its origins in the 1980s. In the next decades business architecture has developed into a discipline of "cross-organizational design of the business as a whole" closely related to enterprise architecture. The concept of business architecture has been proposed as a blueprint of the enterprise, as a business strategy, and also as the representation of a business design.

References

This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.