MOD Digital Skills for Defence (DS4D)
Defining the capability requirement before the learning.
1. The challenge
Defence was framing a digital problem as a training problem — but the real question was what digital capability Defence actually required, and how to align the workforce to it.
2. Context and constraints
Commissioning courses against an undefined capability requirement risks spending heavily and still missing the mission. The stakes were enterprise-wide digital readiness.
3. The approach
- Defined the digital capability requirements against mission and outcomes
- Mapped the skills, behaviours and workforce needs required to deliver them
- Aligned learning architecture to strategic outcomes — not the other way round
- Embedded governance and assurance so decisions stayed defensible
4. What was found
The challenge was never simply training. Once mission was mapped to capability, the gaps sat in undefined capability requirements, unmapped behaviours and workforce needs, and a learning estate that wasn’t aligned to strategic outcomes.
5. What changed
- An evidence-based digital capability requirement, mapped to mission
- A skills and behaviours framework for the digital workforce
- A learning architecture aligned to strategic outcomes
- A governance structure decision-makers could defend
6. Outcomes and evidence
- A clear, evidence-based view of future capability requirements
- Learning architecture aligned to strategic outcomes
- Decision-makers equipped to plan and defend digital capability investment
- Progress in ten weeks that had stalled for twelve months
7. Lessons learned
At enterprise scale, the first job is to define the capability the mission requires. Training plans built before that are course catalogues, not capability.
Where else this applies
The method — define the capability requirement before designing the learning — applies directly to any large organisation modernising a workforce against new technology, in or outside Defence.
Recognise this challenge?
Every organisation is different. The first conversation is about your problem, not a pitch.