What Makes the People Capability System Different?
Anyone claiming novelty in this field should be made to say what came before and where it stalled. Competency-based management has been running since the 1980s. Strategic workforce architecture has been running since the 1990s. Skills frameworks have been running for as long as anyone can remember. So what makes the People Capability System different, and is the difference worth anything?
The full argument, including the prior art section this draws on, is at peoplecapabilitysystem.com.
What makes the People Capability System different?
The People Capability System is not different in its constructs, which are borrowed. It is different in four ways: the work is intended to the strategy rather than mapped to it afterwards, build is explicitly separated from run, position descriptions are generated rather than authored, and a single run produces both the performance read and the regulatory evidence.
That is a narrow claim on purpose. The contribution is the architecture and the operating model, not a new theory of capability.
What came before, and where each lineage stalled
Competency-based management
The closest ancestor. McClelland argued that testing for competence predicts performance better than testing for intelligence in the abstract. Boyatzis modelled competency as the underlying characteristics behind effective performance. Spencer and Spencer codified it as behaviour causally linked to superior performance, assessed against observable indicators. Lawler argued for organisations built around competencies rather than fixed jobs.
This tradition produced the competency frameworks most organisations still run, and the constructs hold up. Where it stalled is well documented. The frameworks became static documents, cut off from operation, drifting from the work. The construct was sound. The operating model was missing.
Strategic human resource architecture
Lepak and Snell modelled how different parts of the workforce should be managed according to their strategic value. The workforce-architecture work associated with Becker, Huselid and Ulrich tied human resource systems to strategy and performance.
This established that the workforce should be architected against strategy, which is exactly right, and it is the closest anyone has come to the argument I am making. Where it stops short is granularity. It reasons at the level of workforce segments and human resource systems, not a line you can walk from a single strategic bet down to a task and back up again.
The skills-framework tradition
SFIA, O*NET, ESCO and Australia's National Skills Taxonomy level skills and give them a shared language. The SFIA Foundation's levels of responsibility remain the most widely used structure of this kind, and the levelling logic is genuinely good.
What this tradition does not carry is a durable human-capability layer above the role, or a run loop. It maps cleanly into the skill and competency layers here and stops there. That is not a criticism of SFIA. It is a description of its scope.
Difference one: intent, not mapping
This is the one I would lead with.
In most architectures, the framework is derived from the work that already exists and then mapped to the strategy at the end. In this one, every layer is derived from the layer above it. Capabilities exist because a bet required them. Competencies exist because a capability had to be delivered in a role. Skills exist because a competency needed them.
The difference shows when the strategy moves. A mapped architecture does not move, because the connections were annotations. An architected one has a derivation at every layer that now has to be revisited.
And the line that results has to be walkable in both directions and accepted by the people it runs through. Clear, so you can name the bet any skill serves and name the work any bet requires. Accepted, so leadership owns the bets and the people in the roles agree the line genuinely runs through their work. A correct line nobody believes is a diagram.
The human spine is what makes the derivation possible. Durable human capability above role competency above skill, with organisational capability deliberately left out. The layers nest rather than sit side by side, because the system has to roll one up into the next. A structure of siblings cannot do that. Keeping organisational capability out of scope is what stops the word capability doing two jobs at once, which is the conflation that quietly wrecks most architectures.
Difference two: build and run are separate activities
This is the one competency-based management never made operational, and it is the reason its frameworks shelved.
Build is design. It runs downward from strategy, it is a project, it has an end date. Run is operation. It runs upward from the work, it is business as usual, it has no end date. Collapsing them is a category error, and it produces a beautifully designed framework nobody has touched in two years.
I have argued this at length in why most capability frameworks fail, and I would defend the build-and-run separation harder than any other part of the system.
Difference three: the artefact chain
Each layer below strategy produces exactly one governing artefact. Capability produces a capability framework. Competency produces a competency framework. Skill produces a skills taxonomy.
Position descriptions are not a fourth artefact. They are a downstream composite, generated from the competency framework and the skills taxonomy rather than authored freehand. That is not an efficiency point. It is the mechanism that keeps the line intact, because the document people actually touch is drawn from the framework rather than copied out of it once and left to rot.
Models for specific roles and matrices for specific people are likewise generated from the frameworks, so there is one source of truth rather than a hundred local versions. That is what makes the system governable, and auditable.
Difference four: convergence
The fourth claim is the one that surprised me most when I worked it through.
One run produces both the performance read and the evidence separate obligations already ask for. Clause 7.2 of ISO 9001 wants determined competence, action on gaps, and retained documented evidence. Australia's psychosocial duty names lack of role clarity as a hazard, and a clear levelled role standard is a documentable control for it. Fair process in a capacity matter turns on a clear expectation and a real opportunity to improve.
Three different regimes, all asking for versions of the same material. Architect the work to the strategy, run it, and the material falls out. That is a property of the assembly. It is not a property any one of the parts has on its own.
What I am not claiming
Each of these moves has antecedents. The build-and-run distinction has ancestors in the older separation of capability as a stock from performance as a flow. The positioning here is a claim rather than an exhaustive literature review, and a fuller search may surface closer prior art. If it does, the novelty claim should narrow to match.
More importantly, the assembly is a proposition and not a result. The components are individually credible. The composite has not been tested. The central proposition is that the assembled system produces a better capability-to-performance outcome than the same components deployed separately, and that is what the whole argument should stand or fall on.
That is a less exciting claim than the field usually makes. It is the one I can defend.
FAQ
What makes the People Capability System different from a competency framework?A competency framework is one layer. The system is the architecture that derives that layer from durable capability and strategy above it, derives skills below it, and then operates the whole thing continuously.
What does intending the work to the strategy mean?It means each layer is derived from the layer above it, so the work exists because a strategic bet required it. The alternative, which is what most organisations do, is to describe the work as it stands and map the strategy onto it afterwards.
How is it different from SFIA?SFIA levels skills against responsibility and treats competence as a skill demonstrated in real situations, which maps into the skill and competency layers here. It carries no durable human-capability layer above the role and no run loop.
How is it different from strategic workforce architecture?That tradition reasons at the level of workforce segments and human resource systems. It does not produce a line you can walk from a single strategic bet down to a task and back up again.
Is the People Capability System new?The constructs are not. The architecture and the operating model are, and even that is a positioning claim rather than a settled fact.