Plan a Digital Transformation Programme
Digital Transformation · 2–4 weeks · Advanced
The job
Structure a digital transformation from diagnosis through prioritisation to change management, keeping the human experience at the centre.
What the sponsor gets
Each canvas and map from this playbook — PESTLE Canvas, Cynefin Framework, Stakeholder Map, Pre-Mortem Canvas, OKR Canvas, Journey map — exports as a PDF, or as PowerPoint on Pro, straight from the session, and the whole run exports as one PowerPoint for the sponsor. Nothing is redrawn.
The method
Assess current digital maturity
Audit current systems, processes, and digital capabilities across the organisation. Interview leaders and frontline staff to understand the gap between ambition and reality.
Tip: The biggest gap is usually not technology — it's skills, culture, and willingness to change working practices.
Scan external digital forces
Create a PESTLE canvas focused specifically on technology, regulatory, and competitive pressures driving digitalisation.
Tip: Distinguish between "we should do this" (strategic choice) and "we must do this" (regulatory or competitive necessity).
Categorise transformation domains
Use Cynefin to classify each transformation initiative by complexity. Simple (automate it), complicated (expert-led), complex (experiment and learn), chaotic (act now).
Tip: Most digital transformations fail because leaders treat complex problems (culture change) as if they were complicated (just hire an expert).
Map programme stakeholders
Create a Stakeholder Map for the transformation. Identify sponsors, champions, affected staff, customers, and suppliers.
Tip: IT is a stakeholder, not the owner — digital transformation is a business programme, not an IT project.
Map the change journey for staff
Create a Change Management journey for how employees will experience the transformation. This is the people plan, not the project plan.
Tip: The biggest risk to any digital transformation is employee disengagement — address it proactively, not reactively.
Pre-mortem the programme
Ask "It's 18 months from now and this transformation has stalled. What went wrong?" This surfaces the real risks.
Tip: The three most common answers will be: leadership lost interest, change fatigue set in, and we didn't invest in training.
Set Year 1 targets
Create OKRs for the first year. Include both technology milestones (systems live) and people milestones (adoption rates, capability uplift).
Tip: If your OKRs are all about technology delivery and none about people adoption, your transformation will deliver systems nobody uses.
The canvases and maps
- PESTLE Canvas
- Six fixed boxes — political, economic, social, technological, legal and environmental — so the room scans the whole outside world, not just the two forces it already worries about.
- Cynefin Framework
- Complex, complicated, chaotic and clear, with disorder beneath for anything not yet sorted, so the team agrees what kind of problem it has before it chooses how to tackle it.
- Stakeholder Map
- Power against interest in four quadrants, so engagement effort goes where it matters and nobody important is handled by accident.
- Pre-Mortem Canvas
- It starts from failure — the project, how it failed, root causes, mitigations and early warnings — so people can voice doubts as foresight rather than dissent.
- OKR Canvas
- One objective, three key results and the initiatives beneath them, so ambition and measurement sit on the same page and no initiative floats free of a result.
- Journey map
- Stages run across and lanes run beneath them, so the experience reads in the order people live it and each low point lines up with what causes it.
What it doesn't do
It doesn't run the room for you or decide for the client. The steps, canvases and duration are a starting point you adapt; the judgement stays yours.