Digital strategy

Connect technology choices, organisation, risk and business goals to build a realistic and durable digital strategy.

55 articles · Latest article updated

Search covers every article in this topic, including the archive and article text.

Understand the topic

A practical guide to this topic

Digital strategy connects a decision to assets, dependencies and constraints. These pieces help document context, qualify uncertainty and choose a realistic order of action.

What to examine
  • Map actors, assets and dependencies before selecting a solution.
  • Separate established facts, weak signals and unresolved questions.
  • Compare options by impact, reversibility, workload and accountability.
  • Test export, reconstruction and continuity before contractual or technical dependencies make an exit impractical.
  • Prepare scenarios, expected outcomes, evidence and exception decisions to assess a delivery through tasks actually tested.
  • Include migration, operation, quality, support and exit in an explicit comparison.
  • Separate transferred volume, energy, emissions and delivered service to avoid unverified environmental gains.
  • Document consequential choices without turning every meeting into an oversized dossier.
  • Turn a tool list into maintenance, replacement and retirement decisions.
  • Expand a new version using comparable observations and an exercised recovery path.
  • Organise closure without abandoning ongoing cases, users or retention responsibilities.
  • Separate business account, web origin and RP ID to plan a transition without silently rebinding credentials.
  • Decide whether a signed artifact still matches the approved producer, build process and release.
  • Tie each DNS name to a controlled resource and make DNS cleanup part of service retirement.
Useful questions
  • Which decision must be made now?
  • Which assumptions could change the choice?
  • What evidence will show whether the action worked?
  • What disappears without the supplier?
  • Who should accept delivery?
  • Is there a standard cost per user?
  • Does a faster site always emit less?
  • Does every ticket need an ADR?
  • Must all old software be replaced?
  • What starting percentage should be used?
  • Is closing the interface enough?
  • Can a database edit change a passkey’s RP ID?
  • Are a matching digest and valid signature enough?
  • Does a CNAME pointing to an error page prove the subdomain can be claimed?

Illustrative decision example

Situation
Fictional example: these inputs describe no customer or observed result. Two proposals answer the same request, but one includes migration while the other covers only building the site.
Check
Ask each bidder to describe migration of the same content, checks, training and operational handover. Record inclusions and assumptions.
Act
Align scope before comparing prices. Record exclusions that would change the choice without inventing a universal score.

Mastering the RFP Process: Winning Strategies for Digital Project Proposals

Project acceptance: turn needs into criteria and evidence

GOV.UK — Prepare a service assessment

Name the assumption that changes the choice

When comparing building, buying or retaining, document the decision, dependencies and decisive metric. Verify provenance before estimating gains and name evidence that could stop or revise the project.

Which missing information could reverse the recommendation?

Explore the methods

Read data · verify · decide

Compare offers across the same lifecycle

A monthly price is not a complete cost. Compare setup, operation, skills, dependencies and exit over an explicit horizon.

Common horizon
36 monthsOne exit at the end
Offer A
€11,400€120 monthly licence
Offer B
€10,680€240 monthly licence

Fictional teaching case — figures describe neither CIE nor a client.

Questions to support your decisions

Find answers and practical checks in the analyses in this category.

Explore the archive

Further analysis in this topic beyond the recent articles listed below.

Reference material

Primary guidance published by the organizations responsible for these methods and standards.