Beyond Buying Technology

Three different things

• Digitisation — converting analogue information into digital form. Scanning paper records.
• Digitalisation — using digital technology to improve an existing process. An online form replacing a paper one.
• Digital transformation — changing how the organisation operates and delivers value, which usually means changing the process itself, the roles around it, and sometimes the business model.

Most programmes described as transformation are digitalisation, and that is frequently the correct and sufficient thing to do. The confusion causes harm when a modest process improvement is sold with transformational expectations and then judged against them.

Why programmes disappoint

• Automating a broken process. Digitising a bad process produces a faster bad process with a larger licence cost. Fix the process first; the automation is then usually simpler and cheaper.
• Technology-led, not problem-led. Selecting a platform before defining the problem guarantees that the problem is redefined to fit the platform.
• Underestimating adoption. The technical build is the smaller half. People continuing to use the spreadsheet is the normal outcome of a system delivered without adoption work.
• Ignoring the data foundation. Analytics and automation both depend on data that is accurate, accessible and consistently defined, and most organisations discover this only after committing.
• Big-bang delivery. Two years of building before anything reaches a user means two years of unvalidated assumptions.
• No owner after go-live. A system without a continuing owner degrades quickly.

What good looks like

• A clearly stated business problem with a measurable outcome.
• Process understood and simplified before it is automated.
• Delivery in increments that reach real users early.
• Business ownership, with IT as a partner rather than the owner.
• Adoption planned and resourced from the start.
• Benefits defined, baselined and measured afterwards.

Assessing where you are

Before planning, assess honestly across several dimensions: process maturity and documentation; data quality and accessibility; the technology estate and its integration; skills and digital confidence in the workforce; governance and decision-making speed; and culture — particularly whether experimentation and failure are survivable. Use a simple maturity scale, gather evidence rather than opinion, and involve people doing the work. The assessment’s value is in the conversation and in identifying the binding constraint, which is usually not the technology.