Training is the most over-funded and least diagnostic part of most S2P transformations. Slides are built. Sessions are delivered. Completion rates are logged. The programme moves on. Six months later, adoption is plateauing and the post-mortem starts with the same flat sentence: "but we trained everyone."
The problem is not that the training was bad. The problem is that training was the entire strategy.
A training plan asks what to deliver. A capability strategy asks what must remain after the programme leaves the building.
Training Is a Tactic. Capability Is a Strategy.
Most programmes have a training plan, not a capability strategy. The distinction matters.
A training plan asks: what sessions, for whom, by when? It is scoped against the platform feature list and measured by completion rates. It is a deliverable.
A capability strategy asks a harder question: who needs to be able to do what, how confidently, sustained over what period — and what's the actual gap today? It is scoped against the operating model's demand and measured by behavioural outcomes. It is a design.
Programmes default to the plan because the plan is easier to produce, easier to budget, and easier to declare complete. The strategy is harder, slower, and exposes uncomfortable truths about where capability genuinely sits today. Most programmes never write one.
Identify the Gap Before Designing the Intervention
Skill-gap analysis is the most skipped step in transformation capability planning. Without it, training becomes generic — the same modules for everyone, scoped by role title rather than by actual capability need.
Done properly, gap analysis maps three things and the spaces between them:
- What each role needs to do post-transformation — drawn directly from the operating model, not the platform configuration.
- What each role can actually do today — assessed by observation and structured self-report, not assumed.
- The delta — by role, by capability cluster, by criticality. That delta — not the platform feature list — is what training should be scoped against.
Programmes that skip this step end up training the wrong people on the wrong things at the wrong depth. The training looks comprehensive. It is in fact misdirected.
The Four Layers of Sustainable Capability
Training delivers knowledge. That is layer one. Sustainable adoption needs three more.
Each layer addresses a failure mode the previous one cannot. Knowledge without train-the-trainer dies when the partner leaves. Train-the-trainer without floor champions is too distant from the moment of use. Floor champions without reinforcement burn out and drift back to their day jobs. The layers compound; in their absence, training compounds nothing.
What Good Looks Like
A capability strategy designed alongside the operating model, not after it. Gap analysis completed before training content is built. Train-the-trainer treated as a deliberate sustainability investment with named principals, dedicated time, and post-deployment continuity. Floor champions identified, equipped, recognised — and given the authority to flag adoption signals before they become adoption problems.
The result is not a training programme that ran on time. It is capability that compounds — that survives go-live by years rather than weeks, and that gives the operating model the people it was designed for.
For your most recent S2P transformation: can you point to the document that mapped skill gaps by role before training content was designed? And can you name the floor champions still active in each operating unit today?
Did you build training — or did you build capability that compounds?