Foundations of Digital Transformation and Technology Strategy

Introduction

Digital transformation is often described as the use of digital technologies to improve an organisation. This description is directionally correct but incomplete. Digital transformation is not simply the installation of software, migration to the cloud, or replacement of paper with electronic records. It is a sustained organisational change in which digital technologies alter how value is created, delivered, captured, governed, and experienced.

For managers, the subject matters because technology has moved from the operational periphery to the centre of competition. Data, software, platforms, connectivity, automation, artificial intelligence, and digital ecosystems now influence customer relationships, operating models, supply chains, employee work, risk exposure, and business economics. A firm may possess advanced technology and still fail to transform if its processes, incentives, leadership, and business model remain unchanged.

This chapter establishes the conceptual foundation for studying digital transformation and technology strategy. It distinguishes digitization, digitalization, and digital transformation; explains technological disruption and convergence; introduces digital maturity; and traces the evolution of information technology from a support function to a strategic capability. It also develops practical frameworks for managerial diagnosis and decision-making.

Learning Objectives

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

1. Distinguish digitization, digitalization, and digital transformation.
2. Explain the meaning and scope of technology strategy.
3. Analyse technological disruption, convergence, and platform effects.
4. Assess digital maturity across multiple organisational dimensions.
5. Explain the evolution of IT from infrastructure support to strategic capability.
6. Connect technology choices with business models, operating models, and competitive advantage.
7. Evaluate managerial, ethical, governance, and implementation implications of digital transformation.

1. The Digital Context of Management

The digital economy is characterised by the increasing use of programmable, connected, data-intensive technologies. A digital product can often be reproduced at very low marginal cost; a digital service can be updated continuously; and a connected platform can coordinate many participants without owning all of the underlying assets.

Several forces explain the strategic importance of digital transformation:

• Computing abundance: Processing and storage have become widely available through cloud infrastructure and specialised hardware.
• Connectivity: Mobile networks, broadband, application programming interfaces (APIs), and the Internet of Things connect people, assets, organisations, and markets.
• Datafication: Activities are represented as data that can be stored, analysed, combined, and used for decisions or automation.
• Software intensity: Software increasingly determines the functionality of physical products and services.
• Automation and artificial intelligence: Rules-based automation and learning systems can augment or replace parts of human work.
• Platform coordination: Digital platforms facilitate interactions among customers, suppliers, developers, workers, advertisers, or other participants.
• Rapid experimentation: Digital products can be tested, measured, and revised more rapidly than many physical products.

These forces do not produce identical outcomes in every industry. Regulation, safety requirements, asset intensity, customer trust, labour arrangements, and legacy systems constrain the speed and form of transformation. A bank, hospital, manufacturer, university, and logistics firm may all become more digital, but their transformation pathways will differ.

2. Three Foundational Concepts

2.1 Digitization

Digitization is the conversion of information from an analogue or physical form into a digital representation. Scanning a paper invoice into a PDF, converting a film photograph into a digital image, or encoding a temperature reading in binary form are examples.

Digitization changes the format of information but does not necessarily change the underlying process. A scanned form may still be manually reviewed, physically routed, and stored in departmental folders. Digitization is therefore usually the first layer of change.

2.2 Digitalization

Digitalization is the use of digital technologies to improve, integrate, or automate an existing process. For example, an organisation may replace paper purchase orders with an electronic workflow that checks approvals, updates inventory, and sends status notifications.

Digitalization changes how work is performed. It may reduce cost, cycle time, error, or inconvenience, but the basic purpose and structure of the process may remain recognisable. Digitalization commonly involves process redesign, system integration, data standards, and performance measurement.

2.3 Digital Transformation

Digital transformation is a broad and ongoing organisational change in which digital technologies, data, and digitally enabled capabilities reshape value creation, operating models, organisational arrangements, and stakeholder relationships.

Transformation is therefore more extensive than technology implementation. It may involve:

• a new customer proposition;
• a shift from selling products to providing outcomes or subscriptions;
• redesign of decision rights and organisational structures;
• new partnerships or ecosystem relationships;
• continuous software-based service improvement;
• redesigned employee roles and skills;
• new risk, privacy, and governance mechanisms.

The three concepts can be summarised as follows:

The distinctions are analytical rather than absolute. A transformation programme may contain thousands of digitization and digitalization initiatives. However, an organisation can digitize extensively without transforming its strategy or business model.

3. Technology Strategy: Meaning and Scope

Technology strategy is the deliberate set of choices through which an organisation uses, develops, acquires, governs, and renews technology to support its objectives and competitive position.

A technology strategy should not be confused with a list of technical projects. It addresses the relationship between technology and enterprise purpose. Important questions include:

1. Which capabilities are strategically important?
2. Which technologies should be built internally, purchased, partnered for, or retired?
3. How should the organisation balance innovation, resilience, cost, security, and speed?
4. What architecture and data foundations are required?
5. Which technology decisions should be centralised and which should be delegated?
6. How will value, risk, adoption, and outcomes be measured?

A useful technology strategy has at least six components:

Strategic intent

Technology investments should be linked to explicit business outcomes, such as growth, customer retention, operational resilience, regulatory compliance, or improved service quality.

Technology portfolio

The organisation must manage a portfolio of systems, platforms, data assets, infrastructure, experiments, and technical debt. Portfolio thinking prevents every initiative from being evaluated as an isolated project.

Architecture and integration

Architecture defines how applications, data, infrastructure, security controls, and interfaces fit together. Poor integration creates duplicated data, inconsistent processes, and dependence on manual workarounds.

Sourcing and ecosystem choices

The firm must determine what to build, buy, lease, share, or obtain through a partnership. Cloud services, open-source software, managed services, and platform ecosystems expand the range of options but introduce dependency and governance risks.

Capability and operating model

Technology strategy requires people with product management, architecture, cybersecurity, data, design, engineering, change-management, and domain expertise. It also requires decision processes that allow rapid learning without weakening accountability.

Governance and risk

Technology must be governed through standards, investment controls, privacy safeguards, cyber-risk management, ethical review, continuity planning, and compliance mechanisms.

Technology strategy is consequently both a competitive and a risk-management discipline. A technically elegant system that does not serve users or business priorities is strategically weak; a commercially attractive system that creates unacceptable privacy or resilience risks is also weak.

4. Technological Disruption

4.1 Meaning of disruption

In general usage, technological disruption refers to technology-enabled change that significantly alters established products, processes, markets, or industry structures. In a more specific sense associated with the theory of disruptive innovation, disruption occurs when a simpler, more accessible, or lower-cost offering initially serves overlooked or less demanding customers and later improves to challenge established firms.

The narrower theory should not be used as a synonym for every major technological change. A breakthrough product serving demanding mainstream customers may be highly innovative without fitting the strict pattern of disruptive innovation.

4.2 Mechanisms of disruption

Technology can disrupt through several mechanisms:

• Cost restructuring: automation or digital delivery lowers unit cost.
• Access expansion: mobile or online distribution reaches customers previously excluded by geography or price.
• Experience improvement: personalisation, convenience, speed, or transparency changes customer expectations.
• Intermediation change: platforms connect participants directly or reorganise the role of intermediaries.
• Business-model innovation: firms shift from ownership to access, transactions to subscriptions, or products to outcomes.
• Information advantage: data and analytics improve matching, forecasting, pricing, or service.
• Complementor mobilisation: an ecosystem of developers, sellers, or partners increases the value of a core platform.

4.3 Incumbent responses

Incumbents often struggle because existing revenue models, performance measures, capabilities, and incentives favour the current system. Common responses include:

1. defending the existing model;
2. improving the existing model incrementally;
3. creating a separate digital venture;
4. acquiring a digital firm;
5. transforming the core business;
6. participating in an ecosystem rather than attempting to control it.

No response is universally correct. The choice depends on strategic fit, speed, capability gaps, cannibalisation risk, regulation, and the organisation’s ability to operate both existing and emerging businesses.

5. Technology Convergence and Ecosystems

Technology convergence occurs when previously distinct technologies, industries, or capabilities combine to create new products, services, or markets. Telecommunications, computing, media, payments, and location services, for example, can converge in a smartphone-based service.

Convergence has at least three forms:

• Technological convergence: integration of hardware, software, networks, sensors, and analytics.
• Industry convergence: boundaries between industries become less distinct.
• Capability convergence: organisations combine previously separate capabilities such as design, data science, operations, and marketing.

Convergence increases opportunity but also complexity. A firm entering a neighbouring domain may face unfamiliar regulation, competitors, customer expectations, and operating risks.

Digital ecosystems are networks of interdependent organisations that jointly create value. A platform may provide technical and governance infrastructure, while complementors provide applications, content, services, or distribution. Ecosystem strategy requires attention to participation rules, interoperability, value distribution, data rights, trust, and power asymmetry.

Network effects are central to many ecosystems. A direct network effect occurs when a service becomes more valuable as more users of the same type join. A cross-side network effect occurs when growth on one side of a platform increases value for another side, such as buyers and sellers. Network effects can accelerate growth, but they do not guarantee success. Poor quality, weak trust, exclusionary conduct, congestion, or regulatory intervention can reduce value.

6. Digital Maturity

Digital maturity is the extent to which an organisation has developed the leadership, capabilities, technology, processes, culture, and governance needed to achieve its digital objectives. It is not simply the number of technologies deployed.

A useful maturity assessment examines multiple dimensions:

Maturity is multidimensional and non-linear. An organisation may have advanced cloud infrastructure but weak data governance, or excellent digital customer experience but fragile operational systems. It is therefore misleading to assign a single maturity score without explaining the dimensions and evidence behind it.

A practical assessment process includes:

1. Define the strategic outcomes to be enabled.
2. Select dimensions relevant to the industry and business model.
3. Establish observable indicators for each dimension.
4. Gather evidence through interviews, system data, process observation, and customer research.
5. Identify capability gaps and dependencies.
6. Prioritise actions according to value, urgency, feasibility, and risk.
7. Reassess periodically because maturity is a moving target.

A maturity model should support decisions, not become an end in itself. High maturity is not always necessary in every capability. A small firm may rationally outsource infrastructure while developing distinctive customer analytics internally.

7. From IT Support to Strategic Capability

The role of IT has evolved through several overlapping stages.

Stage 1: Automation of clerical work

Early business computing focused on payroll, accounting, inventory, and transaction processing. The principal objectives were efficiency, accuracy, and scale.

Stage 2: Information provision

Management information systems supplied reports and dashboards to support planning and control. The challenge shifted from processing transactions to producing timely and relevant information.

Stage 3: Enterprise integration

Enterprise resource planning, customer relationship management, supply-chain systems, and data warehouses connected functions and standardised processes. Integration improved visibility but also created dependence on common architectures and vendors.

Stage 4: Business alignment

IT leaders increasingly participated in strategic planning. Technology investments were evaluated in relation to competitive positioning, operating models, customer experience, and organisational change.

Stage 5: Digital product and platform capability

Software became part of the product and customer proposition. Technology teams adopted product management, agile delivery, DevOps, application programming interfaces, cloud services, and continuous improvement.

Stage 6: Strategic and societal capability

Technology now shapes resilience, public trust, labour, sustainability, privacy, cybersecurity, and market power. The chief information officer, chief technology officer, chief digital officer, data leaders, risk leaders, and business executives must work as a connected leadership system.

The central change is from a project mindset to a capability mindset. A project delivers a defined output within a temporary period. A capability is the repeatable ability to achieve an outcome. Digital transformation requires capabilities such as secure experimentation, real-time decision-making, product discovery, data stewardship, and rapid service improvement.

8. A Framework for Analysing Digital Transformation

Managers can analyse a transformation through five linked questions:

8.1 Why must the organisation change?

This concerns external pressures, customer expectations, competitive threats, regulatory change, cost structures, and strategic opportunities. A technology trend by itself is not a sufficient business case.

8.2 What value proposition is changing?

The organisation should identify the customer problem, the proposed experience, the source of differentiation, and the way value will be captured. Digital transformation often fails when technology is selected before the value proposition is clear.

8.3 How will the operating model change?

Operating-model analysis covers processes, roles, decision rights, partners, locations, technology, and performance measures. A new front-end application cannot deliver a seamless experience if fulfilment, service, and data remain fragmented.

8.4 Which capabilities are required?

Capabilities may include data engineering, cybersecurity, design, automation, change leadership, ecosystem management, and responsible AI. The organisation should distinguish essential differentiating capabilities from commodity services.

8.5 How will change be governed and learned?

Transformation requires sequencing, funding, architecture standards, risk controls, benefit tracking, user adoption, and feedback loops. Leaders should define what can be experimented with locally and what requires enterprise-wide control.

A simple value-realisation logic can be expressed as:

Here, benefits may include additional revenue, avoided cost, improved quality, resilience, or customer value. Investment cost includes implementation and transition expenditure; operating cost includes ongoing technology and support costs; and risk-adjusted cost represents expected losses or the cost of mitigating material risks. This expression is a managerial decision aid, not a complete valuation model. Benefits should be defined with a baseline, time horizon, ownership, and measurement method.

9. Applied Case: Northstar Mutual Insurance

The following is an illustrative case, constructed for educational purposes.

Background

Northstar Mutual is a regional insurance company with a strong agent network and a profitable portfolio of motor and home insurance. Customers increasingly expect online quotations, rapid claims decisions, digital documents, and proactive risk advice. Northstar’s core policy-administration system is twenty-five years old. It is reliable but difficult to integrate with modern applications.

Problem

Northstar launched several disconnected initiatives: a mobile application, a chatbot, a data lake, and a robotic process automation programme. Each initiative delivered some local benefit, but customers still had to repeat information across channels. Claims staff manually reconciled data, and executives could not agree on whether digital investment was reducing cost or increasing retention. Cybersecurity and privacy concerns also increased as more customer data moved across systems.

Analysis

The initiatives represented digitalization, but not yet transformation. The company had digitized documents and automated selected tasks, but its value proposition and operating model remained largely unchanged. A maturity assessment identified weaknesses in cross-channel customer design, data ownership, integration architecture, product governance, and benefits measurement.

Approach

The executive team adopted four principles:

1. Design the claims journey around customer outcomes rather than departmental systems.
2. Create a governed customer and policy data model with clear ownership.
3. Treat claims technology as a digital product, with a multidisciplinary product team.
4. Use an incremental architecture: APIs and event-based integration around the reliable core, rather than immediate replacement of the entire system.

The company introduced digital first notification of loss, automated document classification, rules-based triage, and human review for complex or disputed cases. It also established controls for access, auditability, model monitoring, explainability, and appeals. The use of artificial intelligence was limited to tasks for which data quality and risk controls were adequate.

Outcome

After twelve months, routine claims were processed more quickly, duplicate data entry declined, and customers could track claim status through multiple channels. However, the programme did not eliminate the legacy system. Instead, Northstar developed a clearer investment roadmap, retired redundant applications, and linked technology metrics to business outcomes such as cycle time, customer satisfaction, leakage, and operational resilience.

Learning points

• Digital transformation begins with a business and customer problem, not a fashionable technology.
• Legacy systems can sometimes be integrated and progressively modernised rather than immediately replaced.
• Data governance is an operational requirement, not merely a compliance activity.
• Automation should include human oversight where decisions affect rights, safety, or financial outcomes.
• A product operating model supports continuous improvement more effectively than isolated project delivery.

10. Artificial Intelligence and Emerging Technologies

Artificial intelligence is relevant to digital transformation because it can support prediction, classification, recommendation, generation, optimisation, and autonomous action. Its strategic value depends on data quality, workflow integration, human adoption, governance, and the economics of deployment.

Generative AI can assist with knowledge retrieval, drafting, coding, service interaction, and content production. It also introduces risks including inaccurate outputs, confidential-data leakage, intellectual-property disputes, bias, excessive automation, and unclear accountability. Organisations should therefore assess the task, data, model, user, and consequence before deployment.

Other important developments include edge computing, industrial Internet of Things, digital twins, robotics, advanced analytics, quantum research, and low-code development. The strategic question is not whether an organisation has experimented with each technology. It is whether the technology strengthens a priority capability and can be deployed safely at an acceptable total cost.

11. Ethical, Governance, and Regulatory Considerations

Digital transformation redistributes information and decision power. Governance must therefore address more than project approval.

Privacy and data rights

Organisations should collect only necessary data, define legitimate purposes, control access, protect information, and provide appropriate transparency. Privacy should be designed into processes and systems rather than added after implementation.

Cybersecurity and resilience

Connectivity expands the attack surface. Security requires identity management, secure architecture, vulnerability management, monitoring, incident response, backup, recovery, supplier oversight, and organisational awareness. Resilience also requires plans for cloud outages, data corruption, system failure, and geopolitical disruption.

Fairness and explainability

Automated decisions can reproduce historical bias or create new forms of exclusion. High-impact systems should be tested for disparate effects, monitored over time, and subject to meaningful human review. Explainability requirements should be proportionate to the consequences of the decision.

Accountability

Responsibility cannot be transferred to a vendor or algorithm. The organisation using a system remains responsible for its decisions, controls, and stakeholder impacts. Clear ownership, audit trails, escalation mechanisms, and documented assumptions are essential.

Workforce and inclusion

Automation can augment work, eliminate tasks, create new roles, and intensify performance monitoring. Responsible transformation includes consultation, reskilling, job redesign, accessibility, and attention to unequal effects across workers and communities.

Sustainability

Digital systems consume energy and materials, even when delivered through efficient cloud services. Strategy should consider equipment life cycles, energy sources, data retention, model-computation requirements, and electronic waste.

12. Challenges and Limitations

Digital transformation programmes commonly encounter the following difficulties:

• Unclear objectives: technology activity is mistaken for strategic progress.
• Legacy complexity: old systems contain undocumented rules and critical dependencies.
• Fragmented ownership: no leader owns the end-to-end customer or operational outcome.
• Weak data foundations: inconsistent definitions undermine analytics and automation.
• Change resistance: incentives and routines reinforce existing behaviour.
• Talent constraints: organisations lack product, architecture, data, security, or change expertise.
• Vendor dependence: outsourced capability may create switching costs and concentration risk.
• Innovation theatre: pilots are celebrated without a credible path to scale.
• Measurement failure: outputs such as releases or users are measured instead of outcomes.
• Control imbalance: excessive bureaucracy slows useful experimentation, while weak controls create avoidable harm.

These challenges imply that transformation is a socio-technical process. Technical design and organisational design must be addressed together.

13. Best Practices for Managers

1. Start with strategic outcomes and stakeholder problems.
2. Establish a shared transformation thesis explaining why change is necessary.
3. Assess current maturity using evidence rather than perception.
4. Build a target operating model before selecting a large technology portfolio.
5. Fund products and capabilities, not only temporary projects.
6. Modernise architecture incrementally where replacement risk is high.
7. Treat data as an enterprise asset with accountable stewardship.
8. Embed privacy, cybersecurity, accessibility, resilience, and ethics by design.
9. Combine executive sponsorship with empowered multidisciplinary teams.
10. Use small experiments, but define scaling criteria in advance.
11. Measure adoption, outcomes, total cost, and risk—not merely delivery activity.
12. Develop internal learning and reskilling alongside technology investment.

Chapter Summary

Digitization converts analogue information into digital form; digitalization improves existing processes through digital technology; and digital transformation reshapes organisational value creation, operating models, capabilities, and stakeholder relationships. Technology strategy aligns choices about technology, architecture, sourcing, people, investment, and governance with enterprise objectives.

Technological disruption can alter cost structures, customer access, industry boundaries, business models, and competitive positions. Convergence brings technologies and industries together, while ecosystems coordinate interdependent participants through platforms and governance rules. Digital maturity is multidimensional and should be assessed through strategy, leadership, customer experience, data, architecture, operations, culture, innovation, and governance.

IT has evolved from transaction processing and technical support toward enterprise integration, digital product development, platform capability, and strategic and societal responsibility. Successful transformation depends on capabilities, not isolated projects. It also requires responsible governance of privacy, cybersecurity, fairness, accountability, workforce impacts, and sustainability. The central managerial task is to connect technology choices with measurable outcomes while maintaining the trust and resilience on which digital value depends.

Key Terms

Digitization: Conversion of analogue or physical information into digital form.

Digitalization: Use of digital technologies to improve, integrate, or automate an existing process.

Digital transformation: Organisational change that reshapes value creation, operating models, and stakeholder relationships through digital capabilities.

Technology strategy: Deliberate choices about using, developing, acquiring, governing, and renewing technology.

Technological disruption: Technology-enabled change that significantly alters markets, products, processes, or industry structures.

Disruptive innovation: A specific pattern in which a simpler or more accessible offering moves from overlooked customers toward established markets.

Technology convergence: Combination of previously distinct technologies, industries, or capabilities.

Digital ecosystem: Network of interdependent organisations jointly creating value.

Platform: Digital infrastructure and governance arrangement that enables interactions among participant groups.

Network effect: Change in the value of a service resulting from changes in participation by users or complementors.

Digital maturity: Development of organisational capabilities required to achieve digital objectives.

Operating model: Configuration of processes, roles, decision rights, partners, and technology used to deliver strategy.

Legacy system: Existing technology that remains important but may constrain integration, flexibility, or modernisation.

Technical debt: Future cost or constraint created by expedient technology decisions or deferred maintenance.

Data governance: Policies, roles, standards, and controls for managing data quality, access, use, and accountability.

Product operating model: Continuous, cross-functional approach to developing and improving a digital product or service.

Technology capability: Repeatable organisational ability to achieve an outcome using people, processes, knowledge, and technology.

Responsible AI: Design and use of artificial intelligence consistent with requirements for fairness, transparency, privacy, security, and accountability.

Review Questions

Short Answer Questions

1. What is the difference between digitization and digitalization?
2. Why is digital transformation broader than technology implementation?
3. Define technology strategy and identify two of its components.
4. What is digital maturity, and why should it be assessed across multiple dimensions?
5. How has the role of IT changed from a support function to a strategic capability?

Long Answer Questions

1. Explain the relationship among digitization, digitalization, and digital transformation using an organisational example.
2. Discuss the mechanisms through which digital technologies can disrupt established industries.
3. Critically evaluate the role of platforms, network effects, and ecosystems in technology strategy.
4. Develop a multidimensional framework for assessing the digital maturity of a large organisation.
5. Explain why governance, ethics, cybersecurity, and resilience must be integrated into digital transformation strategy.

Analytical / Application Questions

1. A traditional university has digitized admissions forms but still requires students to submit the same information to several departments. Diagnose the organisation’s level of change and recommend three transformation priorities.
2. A manufacturing firm is considering an AI-based predictive-maintenance system. Analyse the strategic, data, workforce, cybersecurity, and governance questions that should be answered before implementation.
3. A retailer has launched an online store, mobile application, loyalty programme, and warehouse automation project, but customer satisfaction and profitability have not improved. Use the concepts in this chapter to identify likely causes and propose a revised transformation approach.

Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes digitization from digitalization?

A. Digitization changes business models, whereas digitalization changes only culture.

B. Digitization converts information into digital form, whereas digitalization improves processes using digital technology.

C. Digitization requires artificial intelligence, whereas digitalization requires cloud computing.

D. Digitization is strategic, whereas digitalization is always operational.

Correct Answer: B. Digitization converts information into digital form, whereas digitalization improves processes using digital technology.

Question 2

Which situation is most clearly an example of digital transformation?

A. Scanning paper invoices into PDF files

B. Replacing a fax machine with email

C. Automating approval notifications in an existing purchasing process

D. Moving from selling physical products to a data-enabled subscription service with redesigned operations

Correct Answer: D. Moving from selling physical products to a data-enabled subscription service with redesigned operations

Question 3

What is the primary purpose of technology strategy?

A. To maintain an inventory of hardware assets only

B. To align technology choices and capabilities with organisational objectives

C. To eliminate the need for business leadership

D. To ensure that every emerging technology is adopted quickly

Correct Answer: B. To align technology choices and capabilities with organisational objectives

Question 4

Which is an example of a cross-side network effect?

A. A word processor becomes faster when one person uses it repeatedly

B. A private database becomes more secure as its owner adds records

C. More sellers attract more buyers to an online marketplace, increasing its value to sellers

D. A computer consumes less energy after a software update

Correct Answer: C. More sellers attract more buyers to an online marketplace, increasing its value to sellers

Question 5

Which statement about digital maturity is most accurate?

A. It can be measured adequately by counting software applications.

B. It is a single fixed score that applies equally to every organisation.

C. It includes dimensions such as strategy, data, architecture, people, operations, and governance.

D. It is achieved whenever an organisation moves its systems to the cloud.

Correct Answer: C. It includes dimensions such as strategy, data, architecture, people, operations, and governance.

Question 6

A firm has reliable legacy systems but poor integration between customer channels. Which response is most consistent with the chapter?

A. Immediately replace every legacy system regardless of risk.

B. Ignore integration because legacy systems are reliable.

C. Use incremental integration and redesign the customer journey around outcomes.

D. Purchase an unrelated application for each department.

Correct Answer: C. Use incremental integration and redesign the customer journey around outcomes.

Question 7

Which activity best reflects a capability mindset rather than a project mindset?

A. Delivering a fixed application once and disbanding the team

B. Building a repeatable ability to improve a digital service continuously

C. Approving technology expenditure without identifying an outcome

D. Measuring success only by whether the original schedule was met

Correct Answer: B. Building a repeatable ability to improve a digital service continuously

Question 8

Which governance principle is most appropriate for a high-impact automated decision system?

A. Transfer all accountability to the software vendor

B. Use the system without monitoring once it passes an initial test

C. Provide appropriate oversight, auditability, monitoring, and avenues for review or appeal

D. Remove human involvement in every decision to maximise efficiency

Correct Answer: C. Provide appropriate oversight, auditability, monitoring, and avenues for review or appeal

Question 9

In the illustrative Northstar Mutual case, why was immediate replacement of the core system not selected?

A. The company had no need for integration.

B. The existing system was reliable, so incremental integration reduced transition risk.

C. Legacy systems cannot be connected through APIs.

D. The company decided that digital transformation was unnecessary.

Correct Answer: B. The existing system was reliable, so incremental integration reduced transition risk.

Question 10

Which measure is most directly an outcome measure for a digital claims-transformation programme?

A. Number of workshops held

B. Number of software modules purchased

C. Number of project status meetings

D. Reduction in claims cycle time while maintaining quality and control

Correct Answer: D. Reduction in claims cycle time while maintaining quality and control