Skip to main content

Core path

Your path through this level

Progress saves in this browser and syncs after you sign in

Completed
0 of 6
You will be able to
  • Understand what digitalisation means and how it differs from digitisation and automation.
  • Explain how data, processes, and people fit together in a digital operating model.
  • Apply basic journey and outcome thinking to a simple service.
Optional
Full module map
Use this if you want the shape of the level before you start
Show
Digitisation converts. Digitalisation changes the operating loop so outcomes improve.
Open
Prerequisites
  • No previous technical background required
  • Read the section explanation before using tools
Outcomes
  1. Explain digitisation vs digitalisation in your own words and apply it to a realistic scenario.
  2. Digitisation converts. Digitalisation changes the operating loop so outcomes improve.
  3. Check the assumption "Outcome is defined" and explain what changes if it is false.
  4. Check the assumption "Work changes, not only tools" and explain what changes if it is false.
Practice
  • Complete one guided exercise and explain your decision in plain language
  • Use the recap only after reading the main section
Artefact and failure modes
  • A short module note with one key definition and one practical example
  • Tool adoption without change. Teams buy platforms and keep the same broken process. The pain moves, not the outcome.
  • Busy dashboards. Dashboards can look impressive and still be disconnected from decisions.
Module 1.2Why it matters
Digitalisation matters when it changes outcomes, not only when it changes tooling.
Open
Prerequisites
  • No previous technical background required
  • Read the section explanation before using tools
Outcomes
  1. Explain why it matters in your own words and apply it to a realistic scenario.
  2. Digitalisation matters when it changes outcomes, not only when it changes tooling.
  3. Check the assumption "Drivers are stated" and explain what changes if it is false.
  4. Check the assumption "Outcomes are measurable" and explain what changes if it is false.
Practice
  • Complete one guided exercise and explain your decision in plain language
  • Use the recap only after reading the main section
Artefact and failure modes
  • A short module note with one key definition and one practical example
  • Activity without outcomes. Lots of delivery can still produce no improvement. Measure what matters.
  • Overpromising. If benefits are promised without evidence, trust collapses when reality arrives.
Digitalised systems need components that support flow, measurement, and change.
Open
Prerequisites
  • No previous technical background required
  • Read the section explanation before using tools
Outcomes
  1. Explain components of a digitalised system in your own words and apply it to a realistic scenario.
  2. Digitalised systems need components that support flow, measurement, and change.
  3. Check the assumption "Feedback loops exist" and explain what changes if it is false.
  4. Check the assumption "Ownership exists" and explain what changes if it is false.
Practice
  • Complete one guided exercise and explain your decision in plain language
  • Use the recap only after reading the main section
Artefact and failure modes
  • A short module note with one key definition and one practical example
  • Fragmented systems. Fragmentation creates handoffs and delays. It also hides accountability.
  • No operational plan. If operations is ignored, delivery creates future incidents.
Digital systems improve when processes create reliable data and data changes decisions.
Open
Prerequisites
  • No previous technical background required
  • Read the section explanation before using tools
Outcomes
  1. Explain process to data to decision in your own words and apply it to a realistic scenario.
  2. Digital systems improve when processes create reliable data and data changes decisions.
  3. Check the assumption "Processes are observable" and explain what changes if it is false.
  4. Check the assumption "Definitions are shared" and explain what changes if it is false.
Practice
  • Complete one guided exercise and explain your decision in plain language
  • Use the recap only after reading the main section
Artefact and failure modes
  • A short module note with one key definition and one practical example
  • Spreadsheet islands. Local tracking breaks global visibility. The system becomes a collection of private truths.
  • Data without action. If data never changes decisions, it becomes noise.
Journeys are the user view. Platforms are the reuse view. Both must align.
Open
Prerequisites
  • No previous technical background required
  • Read the section explanation before using tools
Outcomes
  1. Explain platforms and journeys in your own words and apply it to a realistic scenario.
  2. Journeys are the user view. Platforms are the reuse view. Both must align.
  3. Check the assumption "Journeys are mapped" and explain what changes if it is false.
  4. Check the assumption "Platforms are operable" and explain what changes if it is false.
Practice
  • Complete one guided exercise and explain your decision in plain language
  • Use the recap only after reading the main section
Artefact and failure modes
  • A short module note with one key definition and one practical example
  • Platform drift. Platforms drift away from user needs unless they are product-managed.
  • Dashboard theatre. Dashboards that do not drive decisions create noise, not control.
Governance works when decisions, enforcement, and evidence are connected.
Open
Prerequisites
  • No previous technical background required
  • Read the section explanation before using tools
Outcomes
  1. Explain risks and governance in your own words and apply it to a realistic scenario.
  2. Governance works when decisions, enforcement, and evidence are connected.
  3. Check the assumption "Decision rights exist" and explain what changes if it is false.
  4. Check the assumption "Governance is usable" and explain what changes if it is false.
Practice
  • Complete one guided exercise and explain your decision in plain language
  • Use the recap only after reading the main section
Artefact and failure modes
  • A short module note with one key definition and one practical example
  • Committees without enforcement. Meetings do not enforce controls. Systems and processes do.
  • Hidden exceptions. Exceptions become the real system. Track and review them.
Optional
Planning and evidence
Objectives, timing, and CPD tracking
Show

If you want to start learning now, leave this closed. Come back when you want to plan your practice or keep evidence for CPD. This is guidance and it is not endorsed by awarding bodies. Standards mapping lives on the course overview page.

Learning objectives

What you will be able to do

  1. 1. Understand what digitalisation means and how it differs from digitisation and automation.
    Clean definitions stop teams arguing about words and start them aligning on outcomes.
  2. 2. Explain how data, processes, and people fit together in a digital operating model.
    Digital work only succeeds when data, process, and people line up.
  3. 3. Apply basic journey and outcome thinking to a simple service.
    Journey and outcome thinking stops you optimising the wrong thing.
  4. 4. Evaluate common digital trade offs between speed, risk, and reliability.
    Trade offs show up early, so I want you to name them rather than hide them.
What comes next
Next we focus on platforms and integration because this is where most transformation effort actually lands.

What changes at this level

Level expectations

Each level is independent but clearly deeper than the last. This panel makes the jump explicit.

Assessment intent
Foundations

Clear definitions and correct mapping to outcomes.

Style
mixed
20 questions
Pass standard
Coming next
Not externally certified
Evidence you can save (CPD friendly)
  • A definitions page: digitisation vs digitalisation vs transformation, plus one example from a service you know.
  • A simple customer journey map with one friction point and the outcome you would measure after fixing it.
  • A before and after operating note: what changed in process, data, and accountability, not only tooling.

CPD timing

Foundations time breakdown

Defensible timing based on page content: reading, labs, checkpoints, and reflection.

Reading
42m
6,219 words × 1.3
Practice
90m
6 × 15m
Checkpoints
30m
6 × 5m
Reflection
48m
6 × 8m
Estimated total
4h 30m
Based on page content
Claimed hours
3h
Includes reattempts + capstone

CPD tracking

Fixed hours for this level are 3. Timed assessment time is included once on pass.

View in My CPD
Progress minutes
0.0 hours

Learning objectives

What you will be able to do

  1. 1. Understand what digitalisation means and how it differs from digitisation and automation.
    Clean definitions stop teams arguing about words and start them aligning on outcomes.
  2. 2. Explain how data, processes, and people fit together in a digital operating model.
    Digital work only succeeds when data, process, and people line up.
  3. 3. Apply basic journey and outcome thinking to a simple service.
    Journey and outcome thinking stops you optimising the wrong thing.
  4. 4. Evaluate common digital trade offs between speed, risk, and reliability.
    Trade offs show up early, so I want you to name them rather than hide them.
What comes next
Next we focus on platforms and integration because this is where most transformation effort actually lands.

What changes at this level

Level expectations

Each level is independent but clearly deeper than the last. This panel makes the jump explicit.

Assessment intent
Foundations

Clear definitions and correct mapping to outcomes.

Style
mixed
20 questions
Pass standard
Coming next
Not externally certified
Evidence you can save (CPD friendly)
  • A definitions page: digitisation vs digitalisation vs transformation, plus one example from a service you know.
  • A simple customer journey map with one friction point and the outcome you would measure after fixing it.
  • A before and after operating note: what changed in process, data, and accountability, not only tooling.

Learning contract

Foundations outcomes

About 3 hours

Read the explanation first, then use the tools to test the idea. Skip any tool that is not useful for your goal.

  1. Understand what digitalisation means and how it differs from digitisation and automation.
  2. Explain how data, processes, and people fit together in a digital operating model.
  3. Apply basic journey and outcome thinking to a simple service.
  4. Evaluate common digital trade offs between speed, risk, and reliability.
Loading content...

Next step

Practise this level, then move on

I recommend you use the practice assessment for Foundations to test your understanding and write a short reflection. Timed assessments are being prepared for this track.

Practice

Assessment

No timer

Pace

Reflection

Evidence

Practice assessment

Start the practice assessment for Foundations

It is designed for confidence and evidence, and you can retry as often as you need.

The timed assessment for this level is being prepared. Use the practice assessment and labs until it is ready.

Sign in to save progress and keep your pass record

You can complete the course while signed out, and your progress saves in this browser. Sign in before assessments so your pass record is attached to your account.

Courses and assessments are free. There is no paywall for the learning path, practice questions, or formal assessments. Optional donations support hosting, maintenance, and ongoing updates.

During timed assessments, copy and the context menu are restricted to reduce casual cheating. Passed assessments are recorded in your account as evidence.

Course materials are protected by intellectual property rights.View terms