4. Strategic Analysis, Foresight, and Technology Intelligence

Introduction and Context

Strategic planning in information technology begins with a disciplined understanding of the environment in which an organization operates. Technology decisions are shaped not only by internal capabilities, but also by regulation, market structures, social expectations, cybersecurity threats, economic conditions, supplier power, research developments, and the changing behaviour of users. An organization that plans without examining these forces risks investing in obsolete capabilities, underestimating dependencies, or responding too slowly to disruption.

Strategic analysis provides the evidence base for governance and decision-making. It helps leaders interpret the present, while foresight extends attention toward plausible futures. Technology intelligence adds a more systematic investigation of technological developments, their maturity, applications, sources of uncertainty, and potential consequences. Together, these practices enable an organization to distinguish signal from noise, identify strategic risks and opportunities, assess its ability to respond, and create coherent technology roadmaps.

The purpose is not to predict the future with certainty. Prediction is often impossible in complex sociotechnical systems. The purpose is to improve preparedness, challenge assumptions, expose dependencies, and create options. For doctoral-level practice, strategic analysis should therefore be understood as both an analytical activity and a form of organizational learning.

Learning Objectives

By the end of this chapter, the reader should be able to:

1. Explain the relationship between environmental scanning, foresight, technology intelligence, and IT governance.

2. Apply PESTLE, SWOT, capability assessment, horizon scanning, scenario planning, and roadmapping appropriately.

3. Evaluate technological opportunities in relation to organizational capabilities, risks, dependencies, and strategic objectives.

4. Distinguish evidence-based intelligence from speculation, hype, and untested assumptions.

5. Design an integrated analysis process that supports investment, risk management, architecture, and governance decisions.

6. Critically assess ethical, regulatory, security, and methodological limitations in strategic technology analysis.

Strategic Analysis as an Evidence-Based Governance Practice

Strategic analysis converts dispersed information into a structured interpretation of the organization’s strategic position. It normally examines three interconnected questions. First, what is changing externally? Second, what can the organization do internally? Third, what choices follow from the relationship between external conditions and internal capability?

This distinction is important because environmental change does not automatically create either opportunity or threat. A new artificial intelligence capability may create an opportunity for an organization with relevant data, skills, governance, and infrastructure. The same development may constitute a risk for an organization that lacks explainability controls, secure data, or qualified personnel. Strategic significance is therefore relational: it depends on the interaction between an external development and an organization’s ability to respond.

A useful analytical cycle consists of the following activities:

• define the strategic question and decision horizon;
• scan and collect relevant internal and external evidence;
• classify and interpret changes;
• assess capabilities, dependencies, and exposure;
• generate strategic options;
• test options through scenarios and assumptions;
• prioritize initiatives and establish indicators; and
• monitor, learn, and revise the analysis.

The cycle should not be treated as a linear one-time exercise. Environmental information changes, assumptions become invalid, and implementation reveals new evidence. Effective governance therefore establishes review points and assigns responsibility for monitoring significant developments.

The External Environment: PESTLE and Environmental Scanning

PESTLE analysis examines political, economic, social, technological, legal, and environmental influences. Its value lies less in producing a long list of factors than in revealing relationships and implications.

Political factors may include national digital strategies, public-sector procurement rules, geopolitical tensions, sanctions, or government priorities concerning critical infrastructure. Economic factors include interest rates, technology costs, labour-market conditions, funding constraints, and the financial consequences of vendor concentration. Social factors include trust in digital services, workforce expectations, demographic change, digital inclusion, and changing attitudes toward surveillance or automated decisions. Technological factors include platform evolution, standards, interoperability, computational capacity, and emerging architectures. Legal factors include privacy, intellectual property, sector regulation, data residency, accessibility, and liability. Environmental factors include energy consumption, electronic waste, carbon reporting, and climate-related disruption to facilities or supply chains.

PESTLE becomes strategically useful when each factor is examined through four questions:

1. What is changing?

2. What is the likely time horizon and degree of uncertainty?

3. Which organizational objectives or capabilities could be affected?

4. What action, monitoring, or contingency is justified?

Environmental scanning is the broader process through which such information is gathered and interpreted. Sources may include regulatory publications, standards bodies, academic research, supplier disclosures, patents, security advisories, customer research, incident reports, professional communities, and internal operational data. Source diversity is important because commercial forecasts may emphasize adoption, vendors may understate limitations, and academic work may be technically promising but operationally immature.

Scanning should distinguish weak signals from established trends. A weak signal is an early indication of a possible change whose significance is not yet clear. A trend is a direction of change supported by repeated observations. A driver is a force likely to shape future conditions, while an uncertainty is a factor whose direction or impact remains difficult to determine.

Internal Position: Capability Assessment and SWOT

External analysis must be combined with an assessment of internal capability. Capability is more than possession of technology. It includes people, processes, data, architecture, leadership, funding, governance, supplier relationships, and the ability to learn and change.

A capability assessment can examine maturity across dimensions such as:

• strategic alignment and portfolio management;
• architecture and integration;
• cybersecurity and resilience;
• data quality, stewardship, and governance;
• product and service delivery;
• talent and organizational learning;
• financial and vendor management; and
• compliance, risk, and assurance.

Maturity models can support comparison, but their categories should not be accepted uncritically. A high score does not guarantee strategic effectiveness if the capability is misaligned with organizational priorities. Conversely, a modestly mature capability may be sufficient for a low-risk context. Assessment should therefore combine qualitative evidence, performance indicators, interviews, audits, service data, and user experience.

SWOT analysis organizes findings into strengths, weaknesses, opportunities, and threats. Strengths and weaknesses are primarily internal; opportunities and threats are primarily external. The framework is simple, but its usefulness depends on disciplined interpretation. A statement such as “strong data capability” is too vague. A better formulation identifies the capability, evidence, and strategic relevance—for example, “shared customer-data standards reduce integration effort across priority services.”

SWOT should lead to strategic choices rather than remain a descriptive inventory. Strength–opportunity strategies use internal advantages to capture opportunities. Weakness–opportunity strategies address capability gaps that prevent exploitation. Strength–threat strategies use existing resilience to reduce exposure. Weakness–threat strategies may require avoidance, partnering, staged investment, or risk acceptance.

From Analysis to Foresight

Foresight is the systematic exploration of possible, plausible, and preferable futures. It differs from forecasting, which often projects expected outcomes from historical patterns. Foresight accepts uncertainty and asks how different combinations of drivers could produce different conditions.

Several distinctions are useful:

• A probable future is one considered most likely under current assumptions.
• A plausible future could occur given known relationships and uncertainties.
• A possible future is not ruled out, even if it appears unlikely.
• A preferable future expresses a normative choice about what the organization wishes to create.

Foresight does not remove uncertainty; it makes assumptions visible. It is particularly valuable where historical data are limited, change is nonlinear, or decisions have long-lived consequences.

Scenario Planning

Scenario planning develops coherent accounts of alternative futures rather than a single forecast. A common process begins by identifying the focal issue, decision horizon, major drivers, and critical uncertainties. Drivers are then assessed by potential impact and uncertainty. The most consequential uncertainties can be used to construct scenario axes, provided the resulting scenarios are internally consistent and meaningfully different.

Good scenarios are not optimistic, pessimistic, and moderate versions of the same future. They represent distinct conditions that challenge current strategy. Each scenario should describe relevant external conditions, stakeholder behaviour, technology consequences, organizational implications, early indicators, and possible strategic responses.

Scenario planning can be used to test questions such as: Would the target architecture remain viable if a major supplier withdrew? How would service delivery change if regulation restricted the use of personal data? What capabilities would be required if demand doubled within three years? The value lies in identifying robust actions—useful across several futures—as well as contingent actions that should be activated when indicators cross defined thresholds.

Horizon Scanning

Horizon scanning searches systematically for emerging developments that may affect strategy. It extends beyond immediate operational risks and examines developments at the margins of current attention. A scanning system may classify issues by time horizon, impact, confidence, maturity, and relevance.

A practical horizon-scanning register records the development, evidence sources, affected domains, possible benefits, risks, assumptions, responsible owner, and next review date. Developments should not be ranked solely by novelty. A mature technology with high organizational relevance may deserve more attention than a dramatic but speculative invention.

Horizon scanning is vulnerable to availability bias, hype cycles, confirmation bias, and overreliance on visible sources. Structured challenge sessions, diverse expertise, source triangulation, and explicit confidence ratings improve quality.

Technology Intelligence and the Assessment of Emerging Technologies

Technology intelligence is the purposeful collection, analysis, and communication of information about technologies, competitors, research, standards, markets, intellectual property, suppliers, and applications for strategic decision-making. It differs from simple technology monitoring because it interprets significance in relation to organizational choices.

A technology-intelligence assessment should consider at least six dimensions:

1. Technical maturity: reliability, scalability, interoperability, performance, and operational requirements.

2. Adoption maturity: evidence of use in comparable contexts and availability of skills and support.

3. Strategic fit: contribution to organizational objectives and architecture principles.

4. Economic value: total cost, opportunity cost, benefits, and cost of delay.

5. Risk and assurance: security, privacy, safety, explainability, resilience, and regulatory exposure.

6. Dependency profile: data, infrastructure, standards, suppliers, skills, and exit options.

Technology maturity is often represented through readiness levels, but a technically mature component may still be organizationally immature. For example, a solution may perform well in laboratory conditions while lacking appropriate controls, integration patterns, procurement routes, or accountable ownership. Assessment should therefore distinguish technical feasibility from strategic viability.

Technology intelligence also examines the ecosystem. A technology does not exist in isolation: it may depend on cloud services, specialist chips, data formats, open-source communities, certification schemes, or a small number of vendors. Concentration risk, licensing changes, geopolitical constraints, and skills scarcity can materially alter the business case.

Roadmapping: Connecting Futures to Action

A technology roadmap links strategic objectives with capabilities, initiatives, technologies, dependencies, and time. It prevents the common error of treating technology acquisition as strategy. A roadmap should show why a capability is needed, what must precede it, what outcomes are expected, and how progress will be assessed.

Roadmaps may be organized in layers. A strategic layer describes goals and outcomes; a capability layer specifies required organizational abilities; an initiative layer identifies programmes and projects; an architecture layer describes platforms, data, integration, and security; and a delivery layer identifies milestones, owners, resources, and measures. The layers should be connected but not confused. A product launch, for example, is not itself a strategic outcome.

Dependencies deserve explicit representation. A data-analytics initiative may depend on data classification, identity management, consent processes, integration interfaces, staff capability, and procurement decisions. Failure to show these dependencies creates unrealistic schedules and fragmented investment.

Roadmaps should contain decision gates rather than imply irreversible commitment. Discovery, proof of concept, controlled pilot, scale-up, and retirement are different decisions. Each gate should specify evidence requirements, risk tolerances, funding conditions, and criteria for stopping. This approach supports real-options thinking: small early investments can preserve the ability to expand, redirect, or abandon an initiative as information improves.

Integrating the Methods into a Strategic Workflow

The tools discussed in this chapter are complementary. PESTLE structures external analysis; capability assessment examines internal readiness; SWOT connects the two; horizon scanning identifies emerging signals; scenario planning tests strategy under uncertainty; technology intelligence evaluates specific developments; and roadmapping converts choices into coordinated action.

An integrated workflow might begin with a strategic question such as whether to modernize a core service platform. Environmental scanning identifies regulatory, market, and technology drivers. Capability assessment reveals architectural debt, skills gaps, and governance constraints. SWOT summarizes the strategic position. Scenarios test platform choices under different supplier, demand, and regulatory conditions. Technology intelligence assesses candidate architectures and suppliers. The roadmap sequences foundational work, pilots, investment gates, and contingency options.

The workflow should produce decision-relevant outputs, including:

• a statement of strategic assumptions;
• a register of risks, opportunities, and dependencies;
• capability gaps and target capabilities;
• scenario implications and early-warning indicators;
• evaluated technology options;
• a staged roadmap with owners and decision gates; and
• measures for benefits, risk, resilience, and learning.

Applied Case: Northbridge Health Network

Background

Northbridge Health Network is an illustrative regional provider coordinating hospitals, clinics, laboratories, and community services. Its information environment consists of aging clinical applications, multiple identity stores, inconsistent data standards, and several outsourced platforms. The board is considering a programme involving cloud migration, predictive analytics, and a unified patient-information service.

Situation and Problem

The proposed programme promises better coordination and reduced duplication, but it also introduces privacy, cybersecurity, service-continuity, supplier, and algorithmic risks. Previous technology projects had exceeded schedules because dependencies on data quality, clinical workflow redesign, and staff capability were underestimated.

Analysis

PESTLE analysis identified stricter expectations for health-data protection, workforce shortages, growing demand for remote services, rising cyber threats, and pressure to demonstrate environmental responsibility. Capability assessment found strong clinical expertise but weak enterprise architecture, fragmented data stewardship, limited model-risk expertise, and high dependence on two suppliers.

A SWOT analysis showed that Northbridge had trusted clinical relationships and valuable longitudinal data, but lacked common data definitions and sufficient integration skills. Opportunities included improved care coordination and earlier identification of high-risk cases. Threats included ransomware, inappropriate disclosure, supplier lock-in, and loss of professional trust if automated recommendations were opaque.

Scenario planning developed four plausible contexts based on regulatory strictness and supplier-market concentration. In the most challenging scenario, strict regulation coincided with the failure of a major supplier. This exposed the need for portability, tested exit procedures, local operational resilience, and stronger data governance.

Technology intelligence compared three architecture options: a fully centralized platform, a federated data model, and a staged hybrid approach. The centralized option offered analytical simplicity but created concentration and migration risk. The federated option preserved local autonomy but required mature standards and governance. The hybrid option allowed gradual consolidation while retaining selected local systems.

Approach and Strategy

Northbridge selected a staged hybrid roadmap. The first phase established common data definitions, identity governance, security controls, and an architecture review board. The second phase created a controlled analytical environment using de-identified data and tested model performance across demographic groups. The third phase introduced limited clinical decision support with human review, clear escalation procedures, and audit logs. Expansion depended on evidence of clinical value, fairness, security, usability, and operational resilience.

The roadmap included supplier exit exercises, independent assurance, staff training, patient communication, and quarterly horizon scans. A technology-intelligence owner was appointed to monitor standards, regulatory guidance, vendor changes, and relevant research.

Outcome

The staged approach delayed some visible features but reduced the risk of large-scale failure. It revealed that data standardization and identity management were prerequisites for analytics. It also allowed clinicians to challenge inappropriate use cases before deployment. The principal outcome was not merely a new platform; it was improved strategic control over data, suppliers, architecture, and future investment.

Learning Points

The case illustrates five principles. First, opportunity assessment must include capability readiness. Second, dependencies should be made visible before commitments are made. Third, scenario planning can expose risks that a business case overlooks. Fourth, emerging technology requires staged experimentation and assurance. Finally, governance is most effective when it creates informed options rather than simply approving or rejecting projects.

Risks, Limitations, and Common Errors

Strategic analysis can create false confidence. Frameworks simplify reality and may encourage analysts to place complex developments into convenient categories. SWOT can become subjective; PESTLE can produce unprioritized lists; scenarios can become narratives without decisions; and roadmaps can disguise unsupported assumptions as dates.

Common errors include confusing activity with outcome, treating vendor claims as evidence, ignoring second-order effects, assuming that technical feasibility guarantees adoption, and failing to revisit analysis after major events. Another error is separating strategy from implementation: a roadmap that ignores procurement, skills, security, architecture, and change management is not strategically credible.

Bias requires active management. Senior leaders may suppress inconvenient evidence, experts may overvalue their own domain, and teams may interpret uncertainty as a reason to delay all action. Useful safeguards include independent challenge, transparent assumptions, multiple evidence sources, confidence ratings, pre-mortems, red-team analysis, and explicit stop criteria.

Quantitative models can support prioritization, but numerical precision should not be mistaken for knowledge. Scores for impact, probability, or maturity are often judgment-based. Their value comes from making reasoning visible and comparable, not from eliminating uncertainty.

Governance, Ethics, and Responsible Use of Intelligence

Strategic analysis involves choices about whose interests count and which risks are acceptable. Governance should specify accountability for intelligence collection, interpretation, decisions, and review. Sensitive information must be handled lawfully and securely, especially when scanning involves personal data, confidential supplier information, or security vulnerabilities.

Technology assessments involving artificial intelligence require attention to privacy, bias, explainability, human oversight, contestability, and accountability. Ethical analysis should examine affected stakeholders, not only the sponsoring organization. A technically efficient system may still be unacceptable if it excludes vulnerable groups or transfers risks to people with limited ability to challenge decisions.

Regulatory compliance is a minimum condition, not a complete ethical standard. Organizations should also consider professional duties, public trust, accessibility, environmental impact, and intergenerational consequences. Governance bodies should demand evidence proportionate to potential harm and should preserve the ability to suspend or withdraw systems that produce unacceptable outcomes.

Digital Tools, Analytics, and Automation

Digital platforms can support environmental scanning through feeds, alerts, text analysis, knowledge graphs, patent analysis, and trend visualization. Machine-learning tools can cluster documents, detect changes in language, and identify relationships across technologies or suppliers. Dashboards can connect external signals with internal risk registers, architecture repositories, and portfolio data.

Automation should support—not replace—expert judgment. Automated systems may amplify source bias, miss contextual meaning, or elevate highly visible topics over strategically important but less public developments. Human reviewers should validate classifications, examine source quality, and challenge algorithmic rankings. Information governance should establish retention, access, provenance, and audit requirements for intelligence repositories.

Current Developments and Emerging Directions

Several developments are reshaping strategic technology analysis. Generative AI is increasing the speed of document review and scenario generation, but it also creates risks involving fabricated evidence, intellectual property, confidentiality, and overconfident interpretation. Digital twins and simulation environments may improve scenario testing where reliable operational data are available. Continuous architecture observability is linking strategic roadmaps with real-time technical conditions. Regulatory technology is helping organizations monitor obligations across jurisdictions. Sustainability intelligence is expanding analysis beyond financial cost to energy use, emissions, water consumption, and hardware life cycles.

These developments reinforce a central principle: analytical capability must evolve alongside technology. Organizations need not only better tools, but also stronger epistemic discipline—the ability to distinguish what is known, inferred, contested, and unknown.

Best-Practice Principles

Effective strategic analysis and technology intelligence generally follow these principles:

1. Begin with a decision, not with a framework.

2. Define time horizons, assumptions, and evidence standards.

3. Combine external scanning with honest capability assessment.

4. Distinguish signals, trends, drivers, uncertainties, and forecasts.

5. Evaluate technologies in their organizational and ecosystem context.

6. Make dependencies, reversibility, and exit options explicit.

7. Use scenarios to test choices rather than to predict one future.

8. Build roadmaps around outcomes, capabilities, decision gates, and owners.

9. Use diverse sources and independent challenge to reduce bias.

10. Monitor indicators continuously and revise strategy when evidence changes.

Chapter Summary

Strategic analysis enables IT governance to connect environmental change with organizational capability and strategic choice. PESTLE and environmental scanning structure examination of external forces; capability assessment and SWOT clarify internal readiness and strategic position. Foresight methods—including horizon scanning and scenario planning—help organizations explore uncertainty without pretending to predict the future. Technology intelligence evaluates emerging technologies through maturity, fit, value, risk, assurance, and dependency. Roadmapping then translates analysis into sequenced initiatives, decision gates, measures, and contingencies.

The most effective approach is integrated and iterative. It treats strategic analysis as organizational learning, uses evidence without disguising uncertainty, and combines technical evaluation with ethical, regulatory, security, environmental, and stakeholder considerations. Its ultimate purpose is to improve the quality and reversibility of strategic decisions.

Key Terms

Environmental scanning: Systematic collection and interpretation of information about external conditions affecting an organization.

Strategic analysis: Examination of internal and external factors to support significant organizational choices.

PESTLE: A framework for analysing political, economic, social, technological, legal, and environmental influences.

Capability assessment: Evaluation of the resources, skills, processes, governance, and technologies enabling performance.

SWOT: A framework organizing internal strengths and weaknesses with external opportunities and threats.

Foresight: Systematic exploration of possible, plausible, probable, and preferable futures.

Horizon scanning: Search for emerging developments, weak signals, and discontinuities that may affect strategy.

Weak signal: An early, ambiguous indication of a potentially significant future change.

Scenario planning: Construction and analysis of coherent alternative future contexts.

Technology intelligence: Interpretation of information about technologies, markets, research, standards, and ecosystems for strategic decisions.

Technology maturity: The degree to which a technology is technically reliable, deployable, and supported.

Strategic fit: The alignment between a technology or capability and organizational objectives.

Dependency: A condition, resource, supplier, capability, or decision required for an initiative to succeed.

Technology roadmap: A time-oriented representation linking objectives, capabilities, initiatives, technologies, and dependencies.

Decision gate: A formal point at which evidence is reviewed before continuing, changing, or stopping an initiative.

Real-options thinking: Treating staged investments as ways to preserve future choices under uncertainty.

Early-warning indicator: An observable signal suggesting that a scenario, risk, or opportunity is becoming more likely.

Technology hype: Excessive or insufficiently evidenced confidence in the significance or maturity of a technology.

Epistemic discipline: Careful distinction between evidence, inference, assumption, uncertainty, and ignorance.

Review Questions

Short Answer Questions

1. Why is strategic significance described as relational?

2. What distinguishes a weak signal from a trend?

3. Identify the six dimensions of technology-intelligence assessment.

4. How does a technology roadmap represent dependencies?

5. Why should scenario planning not be treated as forecasting?

Long Answer Questions

1. Explain how PESTLE, capability assessment, and SWOT can be integrated into an IT governance process.

2. Discuss the role of scenario planning in decisions involving high uncertainty and long-lived technology investments.

3. Critically evaluate the usefulness and limitations of technology maturity assessments.

4. Explain how roadmaps can support staged investment and organizational learning.

5. Discuss the ethical and governance responsibilities associated with automated technology intelligence.

Analytical / Application Questions

1. An organization is considering adopting an AI platform supplied by one dominant vendor. Design an analysis using environmental scanning, capability assessment, scenarios, and technology intelligence.

2. A university has fragmented data, limited cybersecurity skills, and growing regulatory obligations. Construct a SWOT analysis and propose three roadmap decision gates.

3. Select an emerging technology and develop two plausible scenarios showing how different regulatory and supplier conditions could affect its strategic value.

22. Multiple Choice Questions with Answers

Question 1

What is the principal purpose of integrating environmental scanning with capability assessment?

A. To guarantee accurate prediction of future events

B. To relate external developments to the organization’s ability to respond

C. To replace governance with automated ranking

D. To ensure that every emerging technology is adopted

Correct Answer: B. To relate external developments to the organization’s ability to respond

Question 2

Which statement best describes a weak signal?

A. A confirmed regulatory requirement

B. A long-established market trend

C. An early and ambiguous indication of possible change

D. A completed technology implementation

Correct Answer: C. An early and ambiguous indication of possible change

Question 3

In PESTLE analysis, data-residency obligations are primarily classified as which factor?

A. Legal

B. Social

C. Environmental

D. Economic

Correct Answer: A. Legal

Question 4

Which practice most improves the quality of scenario planning?

A. Creating only optimistic and pessimistic versions of one forecast

B. Using critical uncertainties to construct internally coherent alternatives

C. Selecting the scenario preferred by senior management

D. Excluding developments that lack precise probability estimates

Correct Answer: B. Using critical uncertainties to construct internally coherent alternatives

Question 5

Why can a technically mature technology still be strategically immature?

A. Technical maturity always prevents interoperability

B. Organizational skills, governance, integration, or assurance may be inadequate

C. Mature technologies cannot be used by suppliers

D. Strategic maturity is determined only by research publication counts

Correct Answer: B. Organizational skills, governance, integration, or assurance may be inadequate

Question 6

Which roadmap feature most directly reduces the risk of irreversible technology commitments?

A. Fixed delivery dates without review

B. Decision gates with evidence and stop criteria

C. Removing dependencies from the plan

D. Prioritizing visible features over foundational capabilities

Correct Answer: B. Decision gates with evidence and stop criteria

Question 7

In the Northbridge case, why was a staged hybrid architecture selected?

A. It eliminated the need for data governance

B. It combined gradual consolidation with reduced concentration and migration risk

C. It guaranteed that all local systems would be retired immediately

D. It avoided the need for clinical involvement

Correct Answer: B. It combined gradual consolidation with reduced concentration and migration risk

Question 8

Which is an example of real-options thinking?

A. Funding a limited pilot that preserves the option to scale or stop

B. Approving full deployment before evidence is collected

C. Treating the initial business case as permanently valid

D. Avoiding all investment until uncertainty disappears

Correct Answer: A. Funding a limited pilot that preserves the option to scale or stop

Question 9

What is a major risk of using automated tools for horizon scanning?

A. They make source provenance unnecessary

B. They can amplify source bias and overlook contextual significance

C. They prevent organizations from storing intelligence

D. They always produce fewer signals than human analysts

Correct Answer: B. They can amplify source bias and overlook contextual significance

Question 10

Which output is most appropriate for an integrated strategic-analysis process?

A. A list of technologies ranked only by novelty

B. A roadmap linked to assumptions, dependencies, owners, indicators, and decision gates

C. A forecast containing one certain future

D. A SWOT table without strategic choices

Correct Answer: B. A roadmap linked to assumptions, dependencies, owners, indicators, and decision gates