Digitisation, digitalisation and digital transformation describe related kinds of change. They are not used identically by every author or organisation, so a project should define what the terms mean in its own scope.
A useful working distinction is between converting information, changing a workflow and changing the way an organisation creates value.
Digitisation: changing the form of information
Digitisation converts analogue information into a digital representation. Examples include scanning a contract, transcribing a paper price list into a spreadsheet or recording a training session.
The immediate result is digital information. Whether it becomes easier to find, use or retain depends on the quality, structure, permissions and tools around it. Scanning a document does not automatically make its contents searchable or reliable.
A digitisation project can be valuable on its own. It may support access or preservation without requiring a broader transformation programme.
Digitalisation: changing how work is done
Digitalisation uses digital capabilities to change a process. An electronic contract workflow, for example, can connect preparation, review, signature, status and retention. The change concerns how people and systems work together, not only the file format.
Other illustrative examples include a shared customer record, an order status portal or a reporting workflow that draws from approved sources. Benefits need to be measured; a new tool can also create extra work if it does not fit the process.
Automation is one possible part of digitalisation. Some steps may still need human judgement or review.
Digital transformation: broader organisational change
Digital transformation concerns a wider change in how an organisation operates or creates value through digital capabilities. It can involve business models, customer relationships, responsibilities, skills and decision-making as well as technology.
A hypothetical equipment supplier might explore a service model based on monitored machine usage. That would require changes to contracts, maintenance, billing and customer support, not only a sensor or dashboard.
A broad change is not automatically better than a small one. The appropriate scope follows the business need and the organisation’s capacity to make and sustain it.
Comparing the concepts
| Concept | Main question | Example | Evidence to assess |
|---|---|---|---|
| Digitisation | How should information be represented digitally? | Converting approved paper records into searchable files | Completeness, accuracy and access |
| Digitalisation | How should the workflow change? | Connecting document review and approval | Completion time, errors and user experience |
| Transformation | How should the organisation operate or create value? | Developing a service model around a product | Adoption, economics and customer outcomes |
These categories overlap. A programme may include all three, and different departments may start from different positions. There is no mandatory maturity ladder that every company must follow in the same order.
Define the actual scope
Before approving an initiative, record:
- the problem or opportunity being addressed;
- the people, processes and information involved;
- what will change and what depends on that change;
- the outcome to measure and the current baseline;
- ownership of the new process and its ongoing operation.
Calling a project “transformation” does not establish its value. Similarly, a focused digitisation task should not be dismissed merely because it is narrow.
Avoid common misunderstandings
Buying an ERP does not by itself show that a business model has changed. Introducing AI does not remove the need for suitable data, permissions and evaluation. A dashboard does not make decisions evidence-based unless people understand and use its measures.
A smaller improvement may be the right choice. In other cases, a new service or business model may require coordinated changes across several areas. Compare alternatives using the intended outcome rather than the label.
Budget and measurement
Cost and schedule depend on data preparation, integrations, process changes, training and operation. The category name does not imply a standard price or duration.
Use measures relevant to the change, such as the accuracy of digitised records, time to complete a workflow or adoption of a new service. Distinguish released capacity from reduced costs, and test assumptions about revenue or margin.
FAQ
Must digitisation happen before digitalisation?
Some workflows need information to be converted first, while others already use digital data or start as new digital processes. Assess the actual dependencies rather than assume a universal sequence.
Does every SME need a full digital transformation?
No universal answer applies. A company may need a focused improvement, a broader change or maintenance of an existing process. Specific legal duties also need to be assessed separately from strategic choices.
How should a company choose its next step?
Define the problem, inspect the current process and compare feasible options. Choose a scope that can be supported, measured and maintained by the organisation.
How much does digitalisation cost?
There is no standard amount attached to the term. Estimate the particular data, software, integration, training and operating work, and state assumptions and exclusions clearly.
How can management assess the proposal?
Use a business case with a baseline, expected changes, costs, risks and a plan to measure results. The evidence should support the chosen scope rather than rely on general industry percentages.
A path with QA10
Q-Journey connects business process review with subsequent software development. AiP Express and Platinum are parts of that path, with Lean and Muda consulting included in Platinum. Scope, deliverables, price and timing are agreed individually.