Warm up
Visit the Thinking Gym for a short logic puzzle before the summary.
Digitalisation summary and games
CPD tracking
Fixed hours for this level: 4. Timed assessment time is included once on pass.
View in My CPDThis recap reinforces digital practice habits relevant to ITIL 4 style service thinking and TOGAF oriented architecture communication.
You made it to the recap. This page is here to tighten your mental model, test your instincts, and give you a few games to keep it practical.
Big picture recap
Digitalisation matters because it changes how value is created and trusted, not just which tools are used. It joins policy, data, platforms, and people into one system that must work together.
When someone says “we are doing digital”, ask three questions: (1) what user outcome improved, (2) what system behaviour changed, (3) what evidence would prove it.
Big picture map
Policy, data and platforms shape outcomes together.
Policy and regulation
Targets, reporting duties, and trust rules.
Data and standards
Shared meaning, stable identifiers, clean lineage.
Platforms and tools
APIs, workflows, dashboards, and automation.
Outcomes and trust
Service quality, safety, and public confidence.
If you can explain digitalisation without naming a vendor, you understand the idea, not just the tools.
Quick check: the big picture
Scenario: A team replaces paper forms with PDFs and calls it transformation. What would you ask to test that claim
What keeps digitalisation focused
Scenario: Users do not trust the service, so adoption drops. What do you fix first
What links policy to delivery
What is a simple sign of healthy digitalisation
Key tools, standards and patterns
Scale journey
How change moves from pilots to business as usual.
Keep a clear legend for data, platforms, and people so everyone reads the journey the same way.
Quick check: tools and standards
Why are APIs central to digitalisation
What does a data catalogue solve
Scenario: Two operators publish outage data in different formats. Why use CIM style models
Scenario: Teams keep shipping breaking changes to a shared feed. What is the risk of unmanaged standards
Why track signals, not just outputs
What makes a platform reusable
Real world scenarios
Use these as short practice rounds. Pick a scenario and decide the first two changes you would make.
- One-page definition note: digitisation vs digitalisation vs transformation, with one example from your organisation.
- Control loop sketch: measure, decide, act, and the delay. Add one failure mode and one safeguard.
- Integration contract review: pick one API or data feed and write the versioning and rollback expectations.
- Measurement pack: outcome, adoption, reliability, risk. Name owners and review cadence.
Scenario pack
Each one tests a different instinct.
Shared outage updates
Two operators publish outage data in different formats. Which standard do you choose and why.
Customer journey reset
A service journey has high drop off. Which signals prove the fix worked.
Platform overload
Everyone wants new features. Which platform capability should be funded first.
Data quality drift
Reports no longer match. Which owner and checks should be called first.
Games and drills
More practice games
Explore all practice games including cybersecurity, digitalisation, and cross-topic drills.
View All Practice Games →
Quick check: scenarios and games
Why start with outcomes in a scenario
What does a good standard decision consider
Why do journeys need signals
What is a common cause of platform overload
Why call owners early in data quality issues
Scenario: A game gives you a 'right answer' without showing trade-offs. What is missing
Next steps, CPD and further learning
Use the tools below to plan your next learning sprint and log the hours for CPD.
Mini strategy sprint
Write once, reuse for any context.
Focus and outcomes
Pick the first problem and the two outcomes you will measure after one year.
Capabilities and platforms
Name the two weakest capabilities and the shared platforms you will prioritise.
Governance and partners
List the decisions that need governance and the partners you must involve early.
Roadmap reality
Sketch a three year path where year one does not depend on year three.
If you can write this clearly once, you can adapt it and repeat for many contexts.
You do not need to know everything. You need to know how to decide when the stakes are unclear.