Digitalisation Foundations · Module 5
Platforms, journeys, and dashboards
A platform keeps digital work consistent.
Previously
Data, standards, and interoperability
A dataset is only useful when people trust it.
This module
Platforms, journeys, and dashboards
A platform keeps digital work consistent.
Next
Risks, governance, and people
Digitalisation creates new risks.
Progress
Mark this module complete when you can explain it without rereading every paragraph.
Why this matters
Pick something boring: “change my direct debit”.
What you will be able to do
- 1 Explain platforms, journeys, and dashboards 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.
Before you begin
- No previous technical background required
- Read the section explanation before using tools
Common ways people get this wrong
- 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.
Main idea at a glance
Journey and platform view
Journeys run across systems, not inside them.
Stage 1
User touchpoints
Every interaction a user has with the service. Web forms, phone calls, app screens, emails, physical visits. Each touchpoint generates data about what worked and what did not.
I think most organisations focus on the touchpoints they built and ignore the ones users actually use. If half your customers still phone in, your digital channel is not working. Fix the journey, do not blame the user.
This loop is what turns a one-off project into a permanent capability. Without it, services degrade quietly.
A platform keeps digital work consistent. A journey shows where data and service design must line up. A user story keeps teams focused on real outcomes.
Dashboards turn journeys into signals. They show where digital journeys break, where demand changes, and where teams need to respond.
Worked example. The “simple” journey that exposes three hidden systems
Worked example. The “simple” journey that exposes three hidden systems
Pick something boring: “change my direct debit”. On paper it is one action. In many organisations it touches identity, billing, notifications, a case system, and maybe a manual approval queue. If those services are not platformed, you end up rebuilding the same flow again and again.
Common mistakes in journey thinking
Common mistake
Designing journeys inside one system boundary
Reality: Users experience the end-to-end journey, not your system. If it feels broken, it is broken, regardless of which system is at fault.
Common mistake
Building dashboards without operational signals
Reality: Knowing outcomes failed is not enough. You need leading indicators that tell you where to fix things before users complain.
Common mistake
Local optimisation that slows the whole journey
Reality: Making one stage faster can create bottlenecks elsewhere. Measure end-to-end, not just your part.
Verification. A minimum dashboard that earns trust
Minimum trusted dashboard pack
Track these four dimensions to prevent false confidence.
-
Adoption
Measure how many users complete the journey successfully.
-
Friction
Track drop-off and contact-us rates by step to isolate pain points.
-
Reliability
Monitor error rate and latency for key service calls.
-
Quality
Measure downstream rework frequency to expose hidden failure.
Reflection prompt
What is the one journey your users complain about most. If you could fix only one step of it this quarter, which step would you choose and how would you prove it improved.
Mental model
Platforms and journeys
Journeys are the user view. Platforms are the reuse view. Both must align.
-
1
Journey
-
2
APIs
-
3
Platform
-
4
Dashboards
Assumptions to keep in mind
- Journeys are mapped. If you do not map journeys, you optimise the wrong steps.
- Platforms are operable. A platform that teams cannot operate becomes a bottleneck.
Failure modes to notice
- 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.
Key terms
- platform
- A shared set of capabilities and services used across teams.
- journey
- The sequence of steps a user takes to achieve a goal.
- user story
- A short description of what a user needs and why.
Check yourself
Quick check. Platforms and journeys
0 of 7 opened
Why use a platform approach
It reduces duplication and keeps services consistent.
What is a journey
The steps a user takes to reach a goal.
Why are dashboards useful
They show evidence of where journeys work or fail.
What is the purpose of a user story
It keeps teams focused on user outcomes.
Scenario. A journey crosses five systems and users keep repeating details. What should you change first
Fix the end to end flow and shared data, not only one screen. Reduce handoffs, define ownership, and remove duplicate data entry.
What happens when journeys are designed per system
Users experience fragmented services and inconsistent data.
Why link platforms to data
Shared data keeps services aligned and measurable.
Artefact and reflection
Artefact
A short module note with one key definition and one practical example
Reflection
Where in your work would explain platforms, journeys, and dashboards in your own words and apply it to a realistic scenario. change a decision, and what evidence would make you trust that change?
Optional practice
Pick the signals you would track to prove a journey is improving.