Workforce planning · The capability map · Element
The capability list
The capabilities themselves, named at a level that is neither a task nor a department.
The part
What it is
Named too narrowly, the list becomes a task inventory that changes every quarter. Named too broadly, everything resolves to “engineering” and the map stops distinguishing anything.
The workable level is the one where a capability could plausibly be recruited for, developed towards, or bought in.
The smallest level
The attributes it carries
Each attribute is one of the framework’s shared types. What a date is, and how it is written, is defined once for the whole model — the note here says what it means in this particular place.
Capability
The name is the whole map — too narrow and it becomes a task list, too broad and it explains nothing.
Text shared typeCategory
Grouping capabilities is what lets a gap in one area be seen as a pattern rather than an incident.
Choice shared typeCriticality
Separates capabilities the organisation could survive losing from the ones it could not.
Priority shared type