How to Build a Role-Relevant Capability Plan

Most capability plans start in the wrong place

The default way to build a learning plan is to open a course catalogue, pick titles that sound relevant to a job family, and assign them. It feels thorough because it produces a long list, and it feels fair because everyone in the same role gets the same list. It is also, more often than not, a plan built around what a training provider is able to sell rather than what the role actually requires.

The result is predictable: completion rates that look healthy on a dashboard, and a gap between what people were taught and what their job actually asks of them that nobody notices until a decision goes wrong. A capability plan that starts from the catalogue is optimising for the wrong variable from the first step.

Start from the decisions the role owns

A better starting point is the decisions the role is actually accountable for — not tasks, decisions. A category manager does not just 'manage suppliers'; they decide which supplier gets awarded, at what price threshold, under what risk tolerance, and when to escalate rather than decide alone. Those decisions, written down explicitly, are the real job description, and they are what the capability plan has to serve.

Mapping decisions rather than tasks also surfaces judgement that a task list hides. Two people can both 'run a tender process' while one of them is making sound risk trade-offs and the other is not; the decision map is what exposes which parts of the role actually require developed judgement versus which parts are procedural and can be supported by a checklist instead of a course.

Name the evidence of competence before naming the training

For each decision on the map, the next step is to name what evidence would show someone is genuinely capable of making it well — not 'completed a course on negotiation' but 'can structure a negotiation position that accounts for total cost of ownership, not just unit price, and can defend that position under counter-pressure.' Evidence, stated this concretely, is testable; a course title is not.

This step is where most organisations skip ahead, and it is the step that determines whether the eventual plan closes a real gap or just adds a line to a training record. Evidence of competence is also what later lets an organisation measure whether the investment worked, rather than only whether it was consumed.

Find the actual gap, not the assumed one

With decisions and evidence defined, the gap is found by comparing what the evidence requires against what the role currently demonstrates — through manager assessment, work samples, or a structured capability assessment rather than a self-rated survey, which reliably over- or under-states real ability depending on who is answering.

This is usually where the plan gets smaller, not bigger. A team that looked like it needed six courses often needs two targeted interventions and one process change; the rest of the perceived gap was a tooling problem or an authority problem, not a skills problem, and no amount of training closes a gap that was never a skills gap.

Choose learning last, and choose it to match the evidence

Only now does the plan choose specific learning — and the choice should be driven by which format actually produces the named evidence. A judgement-heavy decision (supplier risk trade-offs under uncertainty) is usually better served by case-based or cohort learning with feedback than by a self-paced module; a procedural gap (a new system, a new compliance form) is usually well served by a short, focused module and does not need a multi-week programme.

A worked example: a procurement analyst whose decision map shows spend-classification judgement as the live gap gets a short applied module on classification frameworks plus supervised practice on real spend data, evaluated against the earlier evidence statement — not a general 'procurement fundamentals' certificate that covers the ground they already know alongside the one thing they do not.

Measure it a year later, against the decision, not the completion

The plan is only proven a year on, and the test is whether the original decision is now being made better — fewer escalations for the same reason, faster resolution with the same or better outcome, or a measurable change in the outcome itself — not whether the training record shows a completed course. Completion data measures compliance; decision data measures capability.

Organisations that make this the standard, rather than the exception, tend to find their capability spend goes down even as capability goes up, because the plan stops paying for courses that were never going to move the decision that mattered. That is the entire case for starting from the role's decisions instead of the catalogue: it is not a more virtuous way to plan, it is a cheaper and more accurate one.