Digital Strategy, Innovation and Transformation

Introduction and Context

Digital technologies have moved from being operational support tools to becoming central mechanisms for creating value, managing risk and competing in markets. Cloud computing, data platforms, artificial intelligence (AI), mobile applications, automation, digital ecosystems and connected devices affect how organisations design products, serve customers, organise work and make decisions. Consequently, information technology (IT) can no longer be managed only as a technical service. It must be governed as a strategic capability.

Digital strategy concerns the choices through which an organisation uses digital capabilities to achieve its mission and improve its position. Digital transformation is the coordinated organisational change required to realise those choices. Innovation is the process through which new or significantly improved products, services, processes, business models or organisational practices are developed and adopted.

Transformation is therefore not equivalent to purchasing new software. It involves a relationship among strategy, people, processes, information, technology, governance and culture. An organisation may install advanced technology and still fail to transform if its processes remain inefficient, employees are not prepared, data are unreliable or leaders cannot demonstrate business value.

This chapter develops a practical and analytical approach to aligning IT with organisational strategy, assessing digital maturity, redesigning processes and business models, constructing technology roadmaps, evaluating investments and leading data-driven transformation.

Learning Objectives

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

1. Explain the relationship between business strategy, IT strategy, digital strategy and digital transformation.
2. Analyse an organisation’s digital maturity using structured dimensions and evidence.
3. Identify opportunities for process innovation and business-model redesign.
4. Construct a technology roadmap linked to strategic outcomes and dependencies.
5. Evaluate digital investments using financial and non-financial criteria.
6. Design governance, data and change-management arrangements for transformation.
7. Critically assess the ethical, regulatory, operational and security risks of digital initiatives.
8. Lead a data-driven transformation programme using measurable benefits and feedback.

1. Strategic Alignment of IT and the Organisation

1.1 From IT alignment to digital strategy

Traditional IT alignment asks whether technology supports an existing business strategy. Digital strategy asks a broader question: how can digital capabilities change the organisation’s products, processes, relationships and competitive position? The distinction is important. An organisation may align IT with current processes while missing opportunities to redesign those processes entirely.

A useful hierarchy is:

• Organisational strategy: the mission, objectives, competitive position and allocation of resources.
• Business or functional strategy: how a business unit creates value in a market or operational domain.
• IT strategy: the portfolio of information systems, infrastructure, architecture, skills and services required to support organisational objectives.
• Digital strategy: the integrated use of data and digital capabilities to create, capture and deliver value.
• Transformation portfolio: the prioritised set of initiatives through which strategy is implemented.

Alignment is not a one-time document. It is a continuing process of translating strategic intent into capabilities, investments, operating changes and measurable outcomes. A strategy-to-execution chain can be expressed as:

Strategic objective → required capability → digital initiative → measurable benefit → governance and learning.

For example, if a retailer’s objective is to improve customer retention, the required capabilities may include a unified customer view, personalised engagement and reliable fulfilment. Possible initiatives include a customer-data platform, recommendation services and inventory integration. Benefits may be measured through retention, customer lifetime value, fulfilment accuracy and service cost.

1.2 The role of the chief information and digital functions

The chief information officer (CIO) traditionally manages enterprise IT, architecture, cybersecurity, service delivery and technology investment. The chief digital officer (CDO), where the role exists, may focus on digital products, customer experience, data monetisation and transformation. In practice, responsibilities vary and may overlap. The essential principle is not the job title but clear accountability.

Senior technology leaders should participate in strategic decision-making, not merely receive requirements from business departments. They must understand customers, regulation, operations, finance and risk. Conversely, business leaders must accept responsibility for process redesign, data quality, adoption and benefit realisation. Digital transformation fails when it is treated as an IT project owned exclusively by the technology department.

1.3 A capability-based view

A capability is an organisation’s capacity to perform an activity reliably and create an intended outcome. Capabilities combine people, processes, information, technology, governance and relationships. Examples include digital identity management, predictive maintenance, online fulfilment and regulatory reporting.

A capability-based approach is superior to a technology-first approach because technologies change rapidly while strategic capabilities provide continuity. The question is not “Where can we deploy AI?” but “Which business capability could be improved by prediction, classification, generation or automation, and under what controls?”

2. Innovation and Digital Value Creation

2.1 Types of innovation

Innovation may be classified by what changes:

Incremental innovation improves existing performance, while radical or disruptive innovation may create a new market or make established capabilities less valuable. Both are important. Incremental work often produces dependable benefits; exploratory work protects long-term competitiveness.

2.2 Innovation as a managed learning process

Innovation is uncertain. The objective of early experimentation is not to prove that an idea is correct but to reduce critical uncertainty at reasonable cost. A disciplined innovation cycle is:

1. Identify a customer, operational or societal problem.
2. Form explicit assumptions about users, value, feasibility and risk.
3. Develop the smallest credible experiment or prototype.
4. Collect evidence using agreed measures.
5. Decide whether to persevere, modify, scale or stop.

Design thinking contributes user research, problem definition, ideation, prototyping and testing. Lean experimentation contributes rapid learning and the minimum viable product. These approaches are useful but should not be applied mechanically. A prototype that is acceptable for learning may be inappropriate for production because it lacks security, resilience, accessibility or auditability.

2.3 Business-model transformation

A business model explains how an organisation creates, delivers and captures value. The Business Model Canvas is a practical analytical device containing customer segments, value propositions, channels, customer relationships, revenue streams, key resources, key activities, key partners and cost structure.

Digital technologies can alter each component. Platforms may connect previously separate groups; data may support personalisation; cloud services may convert capital expenditure into usage-based operating expenditure; APIs may enable partners to extend a service. However, digital business models can create dependency on platforms, privacy concerns, concentration of market power and new cybersecurity exposure.

A business-model proposal should therefore answer four questions:

• What customer or stakeholder problem is being solved?
• Why is the proposed digital value proposition better than alternatives?
• How will value and revenue be captured while costs remain sustainable?
• What capabilities, controls and ecosystem relationships are required?

3. Assessing Digital Maturity

Digital maturity is the extent to which an organisation possesses and consistently applies the capabilities needed to achieve its digital objectives. It is not a simple measure of how modern its software appears. A mature organisation may deliberately retain older systems where they are reliable, while a less mature organisation may possess advanced tools without effective governance.

3.1 Maturity dimensions

A practical assessment should examine at least the following dimensions:

A five-level scale can support discussion:

1. Ad hoc: fragmented activity, dependence on individuals and limited measurement.
2. Emerging: isolated digital projects and growing awareness of common needs.
3. Defined: documented standards, strategic priorities and repeatable practices.
4. Managed: integrated capabilities, performance measures and active portfolio governance.
5. Optimising: continuous learning, adaptive investment and evidence-based improvement.

The scale is not a universal scientific law. It is a management instrument. Assessors should define evidence for each level and avoid treating maturity scores as precise measurements.

3.2 Conducting a maturity assessment

A robust assessment combines interviews, workshops, document analysis, process observation, architecture review, employee surveys and performance data. Perceptions alone are insufficient, and technical audits alone overlook culture and adoption.

The assessment process is:

1. Define the scope, strategic questions and organisational units.
2. Select dimensions and observable indicators.
3. Gather evidence from multiple sources.
4. Score current capability and record confidence in each score.
5. Identify capability gaps and their strategic consequences.
6. Define a target state with a realistic time horizon.
7. Prioritise interventions according to value, urgency, feasibility and risk.

A score should always be accompanied by evidence. For example, “data maturity = 2” is weak; “customer identifiers differ across three systems, ownership is unclear and 18% of sampled records lack a valid consent status” is actionable. Quantitative indicators must also be interpreted carefully: a high number of dashboards does not demonstrate data maturity if decisions are not improved.

4. Process Redesign and Operating-Model Change

4.1 Why digitising a poor process fails

Organisations commonly automate existing procedures without challenging their assumptions. This can produce “digital bureaucracy”: faster movement through an unnecessarily complex process. Effective transformation begins with the desired outcome and the user journey, not with a software feature list.

Process redesign should distinguish:

• Value-adding activities: directly create an outcome valued by the customer or stakeholder.
• Necessary control activities: do not directly create value but manage legal, financial, safety or operational risk.
• Non-value-adding activities: delay, duplication, rework or unnecessary handoffs.

Process mapping may use a service blueprint, value-stream map or Business Process Model and Notation (BPMN). Important information includes triggers, actors, decisions, data objects, systems, controls, exceptions and performance measures.

4.2 A redesign method

A disciplined redesign method is as follows:

1. Select a process using evidence of customer harm, cost, delay, risk or strategic importance.
2. Define the outcome and the customer or stakeholder who receives it.
3. Map the current state, including exceptions and informal workarounds.
4. Measure cycle time, waiting time, failure demand, rework, cost and quality.
5. Identify root causes rather than merely visible symptoms.
6. Design a future state using simplification, standardisation, self-service, integration and appropriate automation.
7. Test the design with users and control owners.
8. Implement incrementally and monitor benefits.

Automation is most appropriate when rules are stable, inputs are sufficiently reliable, exceptions are manageable and the consequences of error are controlled. Human judgement should remain involved where decisions are ambiguous, high-impact or difficult to explain.

4.3 Operating-model implications

Digital transformation often requires a shift from functional silos to cross-functional product or service teams. A product team may include a product manager, domain specialist, designer, engineer, data professional, security representative and operations specialist. The team owns an outcome over time rather than delivering a project and immediately disbanding.

This model improves accountability but creates challenges in funding, role definition, architecture governance and coordination. It should be supported by common platforms, clear decision rights and enterprise-level standards.

5. Technology Architecture and Roadmapping

5.1 Architectural principles

A digital architecture should support strategic capabilities while controlling complexity. Common principles include:

• business and technology decisions are traceable to outcomes;
• data are governed as an organisational asset;
• interfaces are documented and reusable;
• security and privacy are designed in from the beginning;
• services are resilient and observable;
• architecture avoids unnecessary dependence on a single supplier;
• standards are used where they improve interoperability;
• technology choices consider total lifecycle cost, not only purchase price.

Cloud computing, application programming interfaces (APIs), event-driven integration, containerisation and data platforms can improve agility. They do not automatically produce it. Poorly governed cloud adoption can increase cost, duplicate data and expand the attack surface.

5.2 Building a technology roadmap

A roadmap is a time-phased representation of capabilities, initiatives, dependencies, resources, risks and expected outcomes. It is not merely a list of software acquisitions.

A practical roadmap contains:

• current-state architecture and major constraints;
• target capabilities and architectural principles;
• initiatives grouped into themes or value streams;
• dependencies and sequencing logic;
• milestones and decision gates;
• resource and skills requirements;
• benefits, risks and measures;
• decommissioning and transition activities.

Sequencing should respect dependencies. For example, reliable analytics may depend on identity resolution, data ownership, integration and quality controls. A roadmap should also preserve optionality: uncertain initiatives can begin as experiments, while foundational work can be funded as enabling infrastructure.

A useful prioritisation model considers value, strategic alignment, feasibility, urgency, risk reduction and learning value. Numerical scores can structure debate, but they should not conceal political assumptions or false precision.

6. Evaluating Digital Investments

Digital investment decisions should combine financial analysis with strategic, operational, ethical and risk criteria. Financial models are decision aids, not predictions of certainty.

6.1 Return on investment

A simple return on investment (ROI) is:

Benefits and costs must be defined over the same period and expressed in the same monetary units. Benefits may include additional revenue, cost avoidance, productivity gains or reduced losses. Analysts should state whether benefits are gross or net, and whether costs include implementation, training, migration, support, cybersecurity and decommissioning.

For example, if a transformation produces monetary benefits of $900,000 and total costs of $600,000 over its evaluation period:

This calculation does not account for the timing of cash flows or risk. It should not be compared directly with an investment whose benefits occur much earlier or later without further analysis.

6.2 Net present value

Net present value (NPV) recognises that money received at different times does not have equal economic value. A general form is:

Here, C₀ is the initial cash outflow at time zero, CF_t is the net cash flow in period t, r is the discount rate per period, and n is the number of periods. The formula assumes cash flows can be estimated, the discount rate is appropriate to the risk and periods are consistently defined. A positive NPV indicates value above the chosen discount benchmark, subject to the quality of assumptions.

Suppose an initiative costs $100,000 initially and generates $60,000 at the end of each of two years. At a discount rate of 10% per year:

The positive result is modest. Sensitivity analysis should test adoption, delivery delay, benefit realisation, cost overruns and the discount rate. In digital projects, real options may also matter: a small investment in a pilot can create the option to scale after evidence is obtained.

6.3 Balanced investment evaluation

A portfolio review should consider:

• strategic contribution;
• customer and employee outcomes;
• financial value and affordability;
• regulatory and ethical acceptability;
• cybersecurity and resilience;
• delivery complexity and organisational readiness;
• architecture and data dependencies;
• reversibility and learning potential.

Benefits should have owners, baselines, target values, measurement methods and review dates. A project is not successful merely because it delivers on time; it must produce the intended change in behaviour or performance.

7. Data-Driven Transformation and AI

7.1 Data as a strategic asset

Data becomes valuable when it is relevant, accessible to authorised users, sufficiently accurate, timely, understandable and connected to decisions. Data governance establishes ownership, definitions, quality rules, access controls, retention requirements, lineage and accountability.

Important roles include the data owner, who is accountable for a domain; the data steward, who manages definitions and quality practices; the custodian, who manages technical storage and protection; and the data user, who applies data responsibly.

A data-driven operating cycle is:

Data capture → quality and integration → analysis or model → decision or action → outcome measurement → learning and improvement.

The cycle is incomplete if dashboards are produced without decisions, or if decisions are made without measuring outcomes.

7.2 AI-enabled transformation

AI can support classification, forecasting, anomaly detection, optimisation, recommendation, language interaction and content generation. Selection should be based on a clearly defined problem, measurable benefit and acceptable risk. AI is not appropriate when the problem is poorly specified, data are inadequate, a simple rule is more reliable or the consequences of error cannot be governed.

A responsible AI lifecycle includes:

1. Problem definition and impact assessment.
2. Data provenance, consent, quality and representativeness review.
3. Model selection and baseline comparison.
4. Validation using relevant performance and fairness measures.
5. Human oversight and an escalation process.
6. Secure deployment, monitoring and change control.
7. Incident response, documentation and retirement when necessary.

Model performance should be evaluated in context. Accuracy alone may be unsuitable for imbalanced classification. For a binary classifier, precision is the proportion of predicted positives that are correct, while recall is the proportion of actual positives that are identified:

The appropriate balance depends on the consequences of false positives and false negatives. These measures are meaningful only when the classes, decision threshold and evaluation data are clearly defined.

8. Governance, Ethics, Security and Change

8.1 Governance and regulation

Transformation must comply with applicable privacy, cybersecurity, accessibility, consumer protection, records-management, intellectual-property, employment and sector-specific regulations. Requirements vary by jurisdiction, so organisations must obtain current legal and professional advice rather than rely on generic checklists.

Privacy principles commonly require lawful and transparent processing, purpose limitation, data minimisation, accuracy, retention control, security and accountability. Governance should also address cross-border transfers, third-party processing, breach response and rights of affected individuals.

8.2 Ethical issues

Ethical analysis asks not only whether an initiative is legal, but whether it is fair, explainable, proportionate and socially responsible. Risks include discriminatory outcomes, surveillance, exclusion of people with disabilities or limited connectivity, manipulation, opaque automated decisions and unequal distribution of benefits.

An ethical review should identify affected groups, potential harms, power asymmetries, alternatives and mitigation measures. Impact assessments should be repeated when the system, data or context changes.

8.3 Cybersecurity and resilience

Transformation increases interconnection and often expands dependence on cloud providers, APIs, identity systems and external partners. Security should follow a risk-based approach involving asset identification, threat modelling, least privilege, strong authentication, encryption, secure development, vulnerability management, monitoring, backup, recovery testing and incident response.

Resilience means more than preventing incidents. It includes the ability to withstand disruption, continue critical services, recover within acceptable time and learn from failure. Business continuity objectives should be agreed with service owners rather than determined solely by technical teams.

8.4 Leading organisational change

Employees may resist transformation because of workload, uncertainty, loss of status, inadequate skills or distrust of leadership. Resistance can contain useful information about design flaws and unintended consequences. Effective change leadership provides a compelling purpose, visible sponsorship, participation in design, realistic training, local champions, psychological safety and feedback channels.

Change should be measured through adoption, proficiency, process performance, user experience and unintended effects. Communication is necessary but not sufficient; systems, incentives, roles and performance measures must reinforce the desired behaviour.

9. Illustrative Case: Northstar Municipal Services

Background

Northstar Municipal Services is a fictional local-government agency responsible for permits, inspections and public enquiries. Residents can submit forms online, but staff re-enter data into several systems. Average permit completion takes 24 days, applicants frequently telephone for updates and managers cannot reliably report backlog levels.

Problem and analysis

An initial assessment found emerging strategy maturity, low process integration, inconsistent customer identifiers, unclear data ownership and strong staff knowledge but limited analytical capability. The agency proposed purchasing an AI chatbot. Workshops showed that the principal problems were not lack of conversational technology but duplicate data entry, unclear status definitions, inconsistent forms and manual routing.

The transformation team mapped the end-to-end permit journey and measured waiting time, rework, incomplete submissions and inspection scheduling delays. It established a baseline: 31% of applications required at least one clarification, and 22% were manually re-entered into a second system.

Approach and solution

The agency adopted a capability-based roadmap:

Phase 1: Stabilise. Establish data ownership, standardise permit definitions, simplify forms, introduce a common reference number and create a service-performance baseline.

Phase 2: Integrate. Connect the application, payment, inspection and notification systems through documented APIs. Introduce a staff dashboard showing application status and ageing.

Phase 3: Improve. Add automated completeness checks and rules-based routing. Provide applicants with status notifications and accessible self-service information.

Phase 4: Experiment. Pilot an AI assistant for frequently asked questions using approved content, with clear escalation to staff. The assistant was not permitted to make legal eligibility decisions.

The programme used a product team containing service staff, process analysts, developers, data stewards, accessibility specialists and security personnel. A steering group reviewed benefits, risk and user feedback at each phase.

Outcome

After implementation, the agency reported fewer incomplete submissions, reduced re-entry and improved visibility of work in progress. Staff time was redirected from status enquiries to complex cases. The AI pilot was retained only for low-risk information requests because testing showed that ambiguous regulatory questions required human interpretation.

The result illustrates an important principle: the greatest value came from process simplification, data governance and integration; AI was a limited supporting capability rather than the transformation itself.

Learning points

1. Begin with the service outcome and evidence, not a fashionable technology.
2. Treat data definitions and ownership as transformation infrastructure.
3. Sequence foundational work before advanced analytics.
4. Keep humans accountable for high-impact or ambiguous decisions.
5. Measure benefits after adoption, not only technical delivery.

10. Contemporary Developments and Best Practice

Current digital strategy is shaped by generative AI, composable architectures, sovereign and multi-cloud concerns, platform ecosystems, cyber resilience, sustainability and digital regulation. Generative AI creates opportunities in knowledge work, software development and customer interaction, but introduces risks involving inaccurate outputs, confidential-data leakage, intellectual property and unclear accountability. Organisations need approved use cases, secure environments, human review and records of significant decisions.

Sustainability should be included in architecture and investment decisions. Relevant considerations include energy use, hardware lifecycle, data retention, efficient model selection, supplier practices and the environmental cost of redundant systems. Digital transformation can reduce travel or material use, but digital infrastructure also has environmental impacts.

Best practice is characterised by:

• explicit strategic outcomes and accountable sponsors;
• a small number of coherent transformation themes;
• evidence-based maturity assessment;
• user-centred process redesign;
• product or service ownership beyond project delivery;
• secure, privacy-preserving and interoperable architecture;
• benefits baselines and post-implementation review;
• incremental delivery with architectural discipline;
• transparent risk, ethics and regulatory governance;
• continuous learning and willingness to stop unsuccessful initiatives.

Challenges and Limitations

Digital transformation is constrained by legacy technology, scarce skills, competing priorities, procurement rules, vendor dependency, data-quality problems and change fatigue. Maturity models may oversimplify complex organisations and encourage score improvement rather than capability improvement. Financial models are sensitive to uncertain adoption and benefit assumptions. Agile methods can improve learning but may create coordination or compliance problems if governance is weak. Data and AI can support better decisions but can also reproduce historical bias or create unjustified confidence.

No framework eliminates judgement. Strategic leaders must combine analysis with stakeholder participation, professional ethics and awareness of institutional context. Transformation is a continuing organisational capability, not a programme with a permanently final state.

Chapter Summary

Digital strategy integrates organisational objectives with the use of data and digital capabilities to create, deliver and capture value. It extends beyond conventional IT alignment by asking how technology can reshape products, processes, operating models and business models.

Digital transformation requires coordinated change across strategy, capabilities, people, processes, data, architecture, governance and culture. Innovation should be managed as a learning process in which assumptions are tested through experiments and evidence. Digital maturity can be assessed across leadership, customer experience, processes, data, technology, skills, culture and governance, using evidence rather than unsupported scores.

Effective process redesign begins with outcomes and user journeys. Technology roadmaps should show capabilities, dependencies, sequencing, risks, resources and benefits. Investment decisions can use ROI and NPV, but financial measures must be supplemented with strategic, ethical, security, resilience and adoption criteria. Data governance is foundational to analytics and AI, while responsible AI requires attention to provenance, fairness, human oversight, monitoring and accountability.

Successful transformation is led as an organisational change effort. It requires executive sponsorship, cross-functional ownership, measurable benefits, secure architecture, user participation and continuous learning. The central professional responsibility is to use technology to improve legitimate outcomes while protecting people, organisations and society from avoidable harm.

Key Terms

Digital strategy: An integrated plan for using digital capabilities to achieve organisational objectives and create value.

Digital transformation: Coordinated organisational change enabled by digital technologies, data and redesigned ways of working.

Innovation: The implementation and adoption of a new or significantly improved product, service, process, business model or organisational practice.

Digital maturity: The extent to which an organisation consistently possesses and applies capabilities required for digital objectives.

Capability: The organisational capacity to perform an activity and achieve an intended outcome.

Operating model: The arrangement of processes, people, technology, governance and partners through which work is performed.

Business model: The logic by which an organisation creates, delivers and captures value.

Business Model Canvas: A framework describing nine components of a business model, including customers, value propositions, channels and resources.

Process redesign: The deliberate restructuring of activities, decisions, roles and systems to improve outcomes.

Technology roadmap: A time-phased plan linking capabilities, initiatives, dependencies, resources, risks and benefits.

Enterprise architecture: The structured description of organisational capabilities, processes, information, applications and technology.

Data governance: Policies, roles, standards and controls for managing data responsibly and effectively.

Data steward: A person responsible for maintaining data definitions, quality practices and appropriate use within a domain.

Artificial intelligence: Computational methods that perform tasks associated with human cognitive capabilities, such as prediction, classification or generation.

Precision: The proportion of positive model predictions that are correct.

Recall: The proportion of actual positive cases that a model identifies.

Return on investment: Net monetary benefit divided by total monetary cost over a defined evaluation period.

Net present value: The present value of future net cash flows minus the initial investment.

Benefit realisation: The process of measuring and achieving intended outcomes from an investment.

Cyber resilience: The ability to withstand, recover from and learn after digital disruption.

Review Questions

Short Answer Questions

1. Distinguish between IT strategy and digital strategy.
2. What is meant by digital maturity, and why should it be assessed using evidence?
3. Identify three dimensions that should be included in a digital maturity assessment.
4. State two conditions under which automation may be inappropriate.
5. Why is data governance important for AI-enabled transformation?

Long Answer Questions

1. Explain how an organisation can align a digital transformation portfolio with its strategic objectives.
2. Describe a systematic method for redesigning a poorly performing business process.
3. Discuss the contents and purposes of a technology roadmap.
4. Compare ROI and NPV as methods for evaluating digital investments, including their limitations.
5. Explain how governance, ethics, cybersecurity and change management contribute to transformation success.

Analytical / Application Questions

1. A university has separate systems for admissions, enrolment and student support. Students repeatedly provide the same information, and managers cannot identify students at risk of withdrawal. Propose a capability-based transformation roadmap, including data governance and measures of success.
2. An organisation proposes an AI system to automatically reject insurance claims. Analyse the strategic, process, data, ethical, regulatory and operational issues that should be resolved before deployment.
3. A digital project requires an initial investment of $250,000 and is expected to generate $150,000 at the end of each of two years. Using a discount rate of 8% per year, calculate its NPV and explain at least three non-financial factors that should influence the decision.

Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes digital strategy from traditional IT alignment?

A. Digital strategy focuses only on replacing legacy hardware.

B. Digital strategy examines how digital capabilities can reshape value creation and business models.

C. Digital strategy excludes organisational and cultural issues.

D. Digital strategy is limited to cybersecurity compliance.

Correct Answer: B. Digital strategy examines how digital capabilities can reshape value creation and business models.

Question 2

Which evidence would most strongly support a claim that an organisation has mature data governance?

A. It owns a large number of dashboards.

B. It has purchased a cloud data platform.

C. Data ownership, definitions, quality rules, access controls and lineage are established.

D. Employees can download all data without restriction.

Correct Answer: C. Data ownership, definitions, quality rules, access controls and lineage are established.

Question 3

What should normally be done before automating a complex business process?

A. Purchase the most advanced automation tool available.

B. Map and analyse the current process, including waste, controls and exceptions.

C. Remove all human involvement immediately.

D. Measure only the software licence cost.

Correct Answer: B. Map and analyse the current process, including waste, controls and exceptions.

Question 4

An investment has total benefits of $900,000 and total costs of $600,000. What is its simple ROI?

A. 33.3%

B. 40%

C. 50%

D. 66.7%

Correct Answer: C. 50%

Question 5

In the NPV formula, what does the discount rate represent?

A. The number of project users.

B. The rate used to convert future cash flows into present value.

C. The total implementation cost.

D. The percentage of automated tasks.

Correct Answer: B. The rate used to convert future cash flows into present value.

Question 6

Which item is most appropriate for a technology roadmap?

A. Only a list of vendor advertisements.

B. Capabilities, initiatives, dependencies, sequencing, risks and expected benefits.

C. A list of employee preferences without strategic links.

D. Only the organisation’s current hardware inventory.

Correct Answer: B. Capabilities, initiatives, dependencies, sequencing, risks and expected benefits.

Question 7

Recall is calculated as:

A. True positives ÷ (true positives + false positives)

B. True positives ÷ (true positives + false negatives)

C. False positives ÷ total predictions

D. True negatives ÷ total cases

Correct Answer: B. True positives ÷ (true positives + false negatives)

Question 8

Why should an AI assistant in a regulated service escalate ambiguous questions to staff?

A. AI systems cannot process any language.

B. Ambiguous or high-impact decisions may require accountable human judgement and explanation.

C. Escalation always reduces operating costs.

D. Regulations prohibit all digital customer services.

Correct Answer: B. Ambiguous or high-impact decisions may require accountable human judgement and explanation.

Question 9

Which is an example of a necessary control activity in process redesign?

A. Repeatedly entering the same data into different systems.

B. Waiting for an unnecessary approval with no risk basis.

C. Verifying compliance with a legal requirement.

D. Duplicating a customer notification.

Correct Answer: C. Verifying compliance with a legal requirement.

Question 10

A project costs $250,000 initially and returns $150,000 at the end of each of two years. At 8% annually, its NPV is closest to:

A. −$25,000

B. −$2,743

C. $27,743

D. $50,000

Correct Answer: C. $27,743