Strategic Technology Planning and Adoption of New Technologies in Enterprise Architecture

In economically challenging times, early adoption of emerging technologies can give companies a competitive edge, but a passive "as‑needed" approach may lead to costly, ad‑hoc decisions rather than tactics aligned with broader corporate strategy.

This strategic analysis report outlines recommended activities and best practices for strategic technology planning, applicable to enterprises with formal Advanced Technology Groups (ATG) or less‑structured planning functions.

Strategic Technology Planning Process

The typical process follows a common set of steps—Scope, Track, Rank, Evaluate, Evangelize, Transfer (STREET)—to guide technology investment decisions.

Figure 1

Scope: Identify company goals, industry direction, and business‑process bottlenecks to focus technology investments.

Track: Scan for new technology opportunities and capture results in a decision‑ready format.

Rank: Select a subset of technologies, plans, and project ideas most likely to deliver significant benefit, balancing resources between business requests and proactive strategic initiatives.

Evaluate: Investigate areas where understanding of a technology or its impact is insufficient to decide on operational adoption.

Evangelize: Influence those who can bring technology into production; marketing, education, networking, and incentives are core ATG activities, especially after the evaluation stage.

Transfer: Hand over knowledge and responsibility to the personnel who will develop and operate the technology, including both experienced staff and those needing new skills.

Adopting New Technologies in Enterprise Architecture

Enterprise Architecture (EA) teams should use a structured approach to plan the introduction of new technologies and products into the corporate IT environment. New technologies continuously reshape the EA portfolio; EA must model these impacts, capture usage changes, and help the business develop technology effectively over its lifecycle.

Enterprise Architecture Framework

1] New Model or Modification of Existing Model?

The key distinction is whether the new technology or product replaces an existing component or introduces a completely new model, which may require stricter planning and formal change approval.

2] Define a New Technical Component Standard

Many new technologies are instances of technical components defined in the ETA. EA should drive planning and modeling activities to record changes to ETA standards and guidelines reflecting new technologies or products.

After selecting component technologies, planners should evaluate and choose specific products as part of the component standard, also considering which supporting products or technologies should be removed from the "production" list.

Below is a lifecycle view of technology and product adoption:

Figure 2

3] Impact at the Technology Domain Level

Technology‑domain considerations start from component decisions and flow down to EA principles and common‑need visions, such as "use standards" and "preferred commodity solutions," guiding both top‑down and business‑driven work.

4] Impact on Technology Pattern Standards

Adopting a major new technology should be placed in the context of providing the right infrastructure or design for applications; each pattern should be reviewed and updated as needed, but not all patterns require immediate changes.

5] Impact on Technical Service Standards

New technology adoption may raise technical service considerations that need to be examined.

6] Define New Technical Strategy for Marketing and Project Definition

Organizations should define a strategy and roadmap indicating when each guidance option should be enabled in current and upcoming projects, assess required resources, conduct stakeholder analysis, and communicate updates to stakeholders.