Building Capability Frameworks People Actually Use
Designing competency frameworks people actually use — not a document that gets published once and never opened again.
Why most frameworks gather dust
Most capability frameworks are built as compliance documents — something to point to when asked whether standards exist — rather than as working tools that inform assessment, development and workforce planning day to day.
The tell is simple: if nobody has opened the framework document since it was published, it isn't a capability framework. It's an artefact.
What makes a framework usable
A usable framework is built with its end use in mind from the start: can a manager use it to assess someone fairly, can HR use it to plan the workforce, can an individual use it to understand what progression actually requires.
That means involving the people who'll use it in its design, and testing early drafts against real assessment scenarios rather than finalising the document in isolation.
Multi-specialisation design
Organisations with multiple specialisations or role types often end up with inconsistent, locally-invented standards — because nobody owns a framework that spans all of them. Multi-specialisation design deliberately maps common ground across roles while preserving what's genuinely distinct about each.
Done well, this makes cross-specialisation workforce planning possible for the first time, because 'ready' means something comparable across the organisation.
The consistency test
The clearest test of whether a framework is working: can two different managers assess the same person against the same standard and reach the same conclusion? If the answer varies by manager, the framework isn't providing the consistency it was built for, however well-written the document is.
This is exactly the risk the Defence Capability Framework Design case study addressed — before the framework, 'ready' meant different things in different teams, which is an operational risk, not just an administrative inconvenience.
Proof it can work
That multi-specialisation framework and skills mapping exercise lifted operational readiness by 20% — not because the document itself changed anything, but because it was designed from the outset to be usable for assessment, development and workforce planning, and was actually adopted as a result.
Common questions on this topic.
Job descriptions describe a role. A capability framework defines the standard of competence expected — usable for assessing anyone against that standard, regardless of exact job title, and for planning the workforce against future needs.
Yes — a framework tied to a mission or operating model that has since changed will drift out of relevance quickly. Annual review, or review whenever the operating model shifts significantly, keeps it usable.
Scale down the ambition, not the discipline — a lightweight framework covering a handful of core roles can deliver the same consistency benefit for a small team as a multi-specialisation framework does for an enterprise.
Want this thinking applied to your organisation?
Insight is useful. Applied insight changes outcomes. Let's talk about yours.