Digital strategy

1 What is a digital strategy?

A strategic plan maps out where the business is going over the long term. A digital strategy applies the same discipline to technology: a considered, long-term view of how digital technology will be used to achieve competitive advantage – what to invest in, what new products, services and ways of working technology opens up, and what the organisation must do now to be ready.

Not every organisation needs an elaborate or expensive digital strategy; for some, digitisation genuinely offers modest benefits. But every organisation must at least think it through deliberately – the disruption cases in Chapter 1 are a catalogue of businesses that did not. In sectors being reshaped by the technologies of Chapter 16, the digital strategy is not a separate technical annex: it largely is the business strategy.

YouTube videoPlay video

2 The governance of digital transformation

Digital transformation means redesigning the business and operating model around digital technology and data – becoming, to some degree, the digital enterprise described in Chapter 16. The syllabus asks a pointed question: who is responsible for leading this process, and what is their role?

The answer is the board and senior executive leadership – not the IT department. Digital transformation qualifies for board attention on every test that matters:

• it is potentially existential – disruption threatens the whole business model, not one function

• it involves major, long-horizon capital commitments and hard trade-offs against other investments

• it cuts across every function – marketing, operations, finance, HR – so only the top of the organisation can drive it

• it carries enterprise-level risks: cyber attack, data misuse, regulatory breach, project failure.

2.1 The role of the board

• Set the digital ambition – decide how central technology is to the organisation's future (the strategic grid below helps), and make that ambition part of the corporate strategy and purpose, not an annex to it.

• Govern the investment portfolio – approve the business cases, stage the funding, and stop projects that no longer earn their place. Digital investments compete for capital like any others, but their benefits are harder to quantify, which demands more board judgement, not less scrutiny.

• Oversee digital risk – including cyber – cyber security is a board responsibility, not a technical detail: the board should know what the critical information assets are, how they are protected, and how the organisation would detect, withstand and recover from an attack. It also oversees data privacy and the ethical use of data and AI (Chapters 16 and 18). The detailed management of cyber risk is examined in the Risk Management paper.

• Monitor progress – track the transformation with meaningful measures (see data and metrics below), not just project milestones.

• Own the people consequences – ensure the organisation has, or is building, the digital skills and culture the strategy assumes (see the final section of this chapter).

2.2 Executive leadership roles

Below the board, organisations assign digital leadership in different ways: the chief information officer (CIO) traditionally runs technology services; a chief technology officer (CTO) may lead the technology underpinning products; many organisations appoint a chief digital officer (CDO) specifically to drive transformation across functions, and/or a chief data officer to govern data as an asset. Titles matter less than the design principles:

• someone at executive level must own the transformation, with authority across functions and a seat in strategy formation

• the CEO must visibly sponsor it – transformations delegated downwards, or treated as an IT project, are the ones that fail

• accountability for benefits sits with the business leaders who claimed them, not with the technologists who built the systems.

3 The economics of digitisation

3.1 How strategically important is IT to this organisation?

Not all businesses can make the same use of technology or need the same proportion of expenditure on it. A useful first assessment (McFarlan's strategic grid) asks two questions: how dependent is the organisation on IT today, and how important will IT developments be to its strategy in future?

3.2 Information intensity

A second pointer is the information intensity of the business – how much information there is in the product itself, and in the process that produces and delivers it. A bag of cement contains little information and its production is routine: digitisation's scope is inherently limited. A broadcaster or newspaper exists to move information: digitisation transforms it. And information intensity can hide in the process rather than the product: there is little information in a shirt, but a fashion retailer producing fifteen thousand designs a year runs on information – computerised design, manufacturing, logistics and demand data.

3.3 Costs and benefits

The economic justification of digitisation is a balance of costs and benefits, and the balance is awkwardly lopsided. Costs are mostly tangible, up-front and estimable (if development is controlled): hardware, software development, cloud and hosting services, specialists' salaries, training. There are some intangible costs too – such as the reputational damage if systems were hacked and sensitive data disclosed.

Benefits are much harder. Some are tangible – labour savings from an automated warehouse – but many of the most important are not:

• better inventory control means fewer stock-outs, better service, a stronger reputation and eventually higher sales – but by how much?

• a more engaging website and sharper social media build recognition and loyalty – how is that quantified?

• integrating ordering, payment and despatch saves measurable handling cost but also wins customers through sheer convenience – how big is that effect?

Ways organisations try to pin the benefits down: observing competitors' operations and results; market evidence that share is being lost to more tech-savvy rivals ('invest or die'); customer surveys (do they find our systems poor? what would they value?); running a pilot in one region and measuring the effect; recruiting people who have seen the effect of digitisation elsewhere; and consulting IT specialists – remembering that consultants are unlikely to advise that more IT is pointless.

3.4 The business case, feasibility and the project plan

Before major digital expenditure is committed, a business case should be made and tested by a feasibility study covering:

• Economic feasibility – do expected benefits justify the costs (with honesty about how soft the benefit estimates are)?

• Technical feasibility – will it work, particularly if the project is experimental or groundbreaking?

• Operational feasibility – will it let staff, customers and suppliers do what they need to do, acceptably fast and simply?

• Social feasibility – will people accept and use it? (Banks that replaced call centres with menus and voice recognition discovered the hard way that customers found it unacceptable – some reversed course.)

An approved project then needs a project plan controlling four things:

• Scope – precisely what the system will do and precisely what the deliverables are ('reduce stock-outs to x%; guarantee delivery within eight hours'), not vague ambitions ('improve inventory management'). Poor scope definition is the reef on which most IT projects founder: undefined projects grow, mutate and become ruinously expensive to change mid-build.

• Cost – the budget; requests for more resources should re-open the cost-benefit case, not be nodded through.

• Time – delivery dates, which often tie into other business changes.

• Quality – the performance standards to be achieved: speed, reliability, usability.

4 Digital business models

Digitisation does not just make existing processes cheaper – it re-routes the flow of business. Classic patterns to recognise:

• Disintermediation – cutting out the middleman: travellers booking directly with airlines and hotels, leaving traditional travel agents stranded.

• Re-intermediation – a new, digital middleman inserting itself: aggregator and booking platforms that stand between customer and supplier precisely because they make comparison and booking easier.

• Countermediation – suppliers creating their own intermediary: for example, a booking site jointly owned by several airlines, steering customers to the owners' flights.

• E-procurement and reverse auctions – purchasing runs through electronic marketplaces; in a reverse auction, would-be suppliers bid the price down, and the lowest compliant bidder wins the contract.

• Platform models – the most consequential pattern: creating value by matching two or more groups rather than by selling down a pipeline (Chapter 16). Platforms are the engine of the digital ecosystems examined next.

5 Digital ecosystems

Chapters 4 and 7 analysed ecosystems, networks and platforms as part of the organisational ecosystem – participants and roles, value creation versus capture, network effects and how platforms are built. This chapter looks at the same phenomenon through the digital-strategy lens: digital ecosystems – communities of organisations and individuals creating value together around a shared digital platform – and what they mean for the organisation forming its digital strategy: its participants, interactions, dynamics, and the partnerships needed for strategic success.

5.1 Participants

• The orchestrator (or keystone) – the organisation that owns the platform, sets its rules and shapes the ecosystem: the app-store owner, the marketplace operator, the operating-system vendor.

• Producers and complementors – the independent businesses and individuals who supply the products, content, apps and services traded on the platform. They are not employees or ordinary suppliers: they invest their own resources and take their own risks, complementing the platform.

• Customers and consumers – who come for choice, convenience and trust.

• Partners and enablers – payment providers, logistics firms, data and cloud providers – and, watching all of it, regulators.

5.2 Interactions

Participants interact through the platform's technology: interfaces (APIs) through which complementors plug their products and services in, shared data that lets participants find and trust each other (search, ratings, reviews), and integrated payment and delivery. The orchestrator writes the rules of the game: who may join, what quality standards apply, what fees are charged, who sees what data. Setting those rules is a strategic act – too extractive and complementors leave; too lax and quality and trust collapse.

5.3 Dynamics

Ecosystem competition behaves differently from pipeline competition. Chapter 7 introduced these dynamics; in digital ecosystems they run at full strength:

• Network effects – each additional customer makes the platform more valuable to producers, and vice versa; growth feeds on itself.

• Winner-takes-most – network effects plus low marginal costs tip markets towards one or two dominant platforms.

• The chicken-and-egg problem – a new platform needs producers to attract customers and customers to attract producers; orchestrators solve it by seeding one side (subsidies, free tools, supplying content themselves) until the flywheel turns.

• Co-evolution – participants adapt to each other continuously; the ecosystem's health (not just the orchestrator's profit) determines its survival, so orchestrators must leave enough value on the table for complementors to thrive.

5.4 Impact on strategy

For the organisation forming strategy, digital ecosystems change the questions. Competition is increasingly ecosystem against ecosystem rather than firm against firm. An organisation must choose its role: orchestrate a platform of its own (rarely feasible – it demands scale, technology and a credible proposition for both sides), or participate skilfully in others' ecosystems – which brings reach and shared capabilities, but also dependence on rules, fees and algorithms the orchestrator can change unilaterally. Partnerships across the ecosystem – with complementors, technology providers and even competitors – become a normal instrument of strategy rather than an exception, and stakeholder analysis must extend to ecosystem partners the organisation does not control.

6 Digital consumption

The syllabus highlights the key trends in how customers consume the organisation's products and services:

• Hyperpersonalisation – offerings, prices, content and communications tailored to each individual in real time, powered by the customer's own data trail (introduced with customer analysis in Chapter 9, and supercharged by the generative AI of Chapter 16).

• From products and services to experience – customers increasingly buy access, outcomes and experiences rather than owning things: streaming instead of discs, ride-hailing instead of car ownership, subscription instead of purchase. What is evaluated is the whole experience – discovery, purchase, use, support – not the artefact alone.

• Continuous relationships – consumption becomes an ongoing, data-generating relationship rather than a series of anonymous transactions. Every interaction feeds the analytics that improve the next interaction – a feedback loop that rewards incumbents with data and makes customer retention, engagement and lifetime value the measures that matter (see the metrics below).

7 Data and metrics: measuring digital success

If digital investment is justified by forecast benefits, its success must be measured – if only to correct the forecasting next time. How easy that is depends on the kind of system:

• Transaction processing systems – changes are relatively easy to measure retrospectively: inventory levels, collection periods, staffing costs in the accounts department, before-and-after customer satisfaction with delivery times.

• MIS and decision support systems – harder, because objective measures of 'better decisions' barely exist. Usable proxies: speed of answering queries, time to produce reports, speed of decision-making, staff ratings of the system. You can rarely know what outcomes the old system would have produced.

7.1 Digital traction

For digital businesses themselves – websites, apps, platforms – financial metrics alone arrive too late. The industry measures traction: grip. Does a visit lead to a transaction, a registration, a return visit, a contribution – or nothing? The World Economic Forum groups traction metrics under three headings:

Scale – how big is the audience?

• unique visitors and total visits; registered users

• month-on-month growth in registrations

• organic user acquisition – growth not reliant on paid advertising.

Active usage – how many of them actually use it?

• daily and monthly active users

• conversion rate – the proportion moving from one stage to the next (visit → registration → purchase)

• abandon rate – e.g. baskets abandoned, unsubscribes.

Engagement – how deeply are they involved?

• time on site or in app; average page views per visit; downloads; posts, uploads, likes and shares

• bounce rate – the percentage of visitors who navigate away after viewing just one page

• screen flow – analysis of common user pathways, particularly screens that immediately precede a large number of exits: perhaps that screen is confusing, unwelcoming or off-putting

• stickiness – is the site habit-forming? A common measure is average daily active users ÷ monthly active users. If 9,000 unique users visit in a month and about 9,000 visit every day, everyone is visiting daily (stickiness = 1). If only 300 of the month's 9,000 visit on an average day (stickiness = 1/30), the average user comes about once a month.

• cohort retention – tracking each month's new visitors as a group to see how many return:

Interpret cohort tables carefully: the falling percentages do not necessarily mean the site is becoming less engaging – the four-months-ago cohort has had four months in which to revisit, the newest cohort only one. Compare each cohort's behaviour at the same age before drawing conclusions.

• Net promoter score (NPS) – customers are asked how likely they are to recommend the site or service, on a scale of 0–10: 9–10 are promoters, 7–8 passives, 0–6 detractors. NPS = % promoters − % detractors.

• Churn rate – the annual percentage of customers who stop using or subscribing. For subscription and experience businesses, churn and customer lifetime value are the numbers investors read first.

8 Leadership and culture in digital transformation

The syllabus closes the digital strand by asking how leaders and their organisations should think, act and react differently because of digital transformation. Technology is the easy half; most failed transformations fail on leadership and culture.

• Digital mindset at the top – leaders need enough technological fluency to interrogate what they are shown, and the humility to keep learning as the technology moves. A board that cannot discuss data, platforms or AI delegates its strategy to whoever can.

• Experimentation over perfect planning – digital opportunity is explored by test-and-learn: small, fast, measured experiments (pilots, prototypes, minimum viable products), scaling what works and killing what does not. That requires leaders to fund uncertainty and treat well-run failed experiments as information, not blame.

• Data-driven decision culture – decisions argued from evidence and experiments rather than seniority ('the highest paid person's opinion'). Leaders model this by asking for the data and changing their minds when it disagrees with them.

• Breaking silos – digital value chains run across functions, so transformation organises around customer journeys and products with small cross-functional ('agile') teams, rather than sequential functional hand-offs.

• Talent and reskilling – the plan must say where digital skills will come from (hiring, partnering, and above all reskilling existing staff) and be honest about the roles automation will change – handled well, this is the difference between a workforce that drives the change and one that resists it.

• Leading the change itself – digital transformation is a major organisational change: expect the resistance, use the change-management frameworks, styles and levers of Chapter 14, and remember the cultural web – artefacts like agile ceremonies change faster than the underlying assumptions that actually govern behaviour.

9 Test your knowledge

Two short exercises close the chapter in the online notes: ten flashcards on the terms and frameworks above, and ten practice questions with worked feedback on every option. Work through the cards first, then the questions.