What Is the People Capability System?

In most organisations the causality runs backwards. The work exists, the roles exist, the frameworks exist, and the strategy gets retrofitted onto all of it afterwards as a mapping exercise. Nobody ever sat down and derived the work from the bets. They described the bets in terms of the work they were already doing.

The People Capability System exists to invert that. The full argument is at peoplecapabilitysystem.com. This is the short version.

What is the People Capability System?

The People Capability System is a single architecture with four layers, strategy, capability, competency and skill, that intends the work to the strategy rather than the other way around. It is built once from the top down and run continuously from the bottom up, producing a clear and accepted line from a strategic bet to a discrete task.

Every construct in it is decades old. The contribution is the architecture and the operating model, not the pieces.

The problem: the work is not architected to the strategy

Ask a senior leader which capabilities the strategy actually requires, and at what level. In most organisations the answer takes three weeks, involves four people, and arrives as an opinion.

That is not a measurement failure. It is an architecture failure. The work was never derived from the strategy in the first place, so there is no line to read back. What exists instead is a mapping, drawn after the fact between two structures that were written independently, and a mapping quietly stops being true the moment either side moves.

The symptoms are familiar. A capability framework in a slide deck from a project two years ago. Competencies inside position descriptions that have drifted from the work. A learning catalogue that maps to nothing. A skills field in the HR system that nobody trusts. Every one of those parts is fine on its own. None of them was intended to a strategic bet, and none of them can be traced back to one.

Artificial intelligence is what makes this unignorable. As tasks shift to automation and augmentation, the live question becomes what humans still do and to what level. That question is asked at the task layer and is answerable only if the task connects upward to a bet. A retrofitted architecture cannot answer it.

The line has to be clear and accepted

Two properties, and both are load-bearing.

Clear means traceable in both directions. Point at any skill and you can name the bet it serves. Point at any bet and you can name the work that delivers it. If you cannot do both, you have a diagram rather than a line.

Accepted means leadership owns the bets as the real ones, and the people in the roles accept that the line genuinely runs through their work. This is the part everyone skips. A line nobody in the role believes is a line that gets ignored the first time it costs someone something, and it will not survive a reorganisation.

The four layers

The system depends on keeping the layers distinct. The moment they blur, nothing can be traced.

• Strategy. The bets the organisation is making. Strategy is not a layer the system builds. It is the input everything below is derived from and answerable to.
• Capability. A broad, durable area of ability a person owns and carries across roles and contexts. This is human capability, not organisational capability, defined once across all roles and held by individuals. I have written a fuller treatment of what capability frameworks actually are.
• Competency. The integration of skills, knowledge, judgement and behaviour, applied in the context of a role, described as observable behaviour at a defined level of proficiency. Scoped to the role, and not a task. See what competency means if that distinction is not settled for you.
• Skill. A discrete, learned ability to do something specific. Granular and transient. At assessment it is close to binary. A person has it at the level required, or there is a gap.

Capability sits above competency because it is what a person keeps when the role changes, which puts it closer to strategy. Competency and skill sit lower because they describe the present role and the present task. The layers nest rather than sit side by side, because the system has to roll one up into the next. Skills evidence a competency, competencies express a capability, capability answers a bet. A structure of siblings cannot roll up. A nesting can.

How does the People Capability System work?

Two activities in two directions.

You build it once, top down. Name the bets with leadership rather than for them. Derive the human capabilities those bets require. Define the competencies each role needs to turn those capabilities into delivered work. Specify the skills under each competency. Every step is answerable to the step above it, so by the time you reach a skill you can trace back to a bet. That is intent, and it is the opposite of mapping.

You run it forever, bottom up. Check whether a person has the skill at the level the role needs. Evidence whether the competency is held rather than claimed. Read whether capability is deep enough across the workforce. Roll it into one question: given the people we have, is this strategy executable.

Build is design with an end date. Run is business as usual with no end date. Most capability work is all build and no run, which is why so much of it ends up on a shelf.

What the People Capability System produces

Each layer below strategy produces exactly one governing artefact. Capability produces a capability framework. Competency produces a competency framework with proficiency levels and observable indicators. Skill produces a skills taxonomy, so a skill means the same thing wherever it appears. Australia's National Skills Taxonomy is building exactly this kind of shared language at national level.

Position descriptions are the case that proves the point. In most organisations they are authored by hand and drift from the work inside a year. Here they are not authored at all. They are a composite generated from the competency framework and the skills taxonomy. Change the framework and the position descriptions move with it, because they are drawn from it rather than copied out of it once. That is what keeps the line intact as the work changes.

What the People Capability System is not

• It is not a rating engine. It measures capability in order to develop it. It does not rank people and it does not conduct dismissals. The moment a development system is repurposed as a policing tool, people stop giving it honest evidence.
• It is not organisational capability. Dynamic capabilities describe what an organisation can sense and reconfigure. That is a different construct, deliberately out of scope.
• It is not a platform. It does not depend on a vendor. It does need a system of record, because the artefacts have to live somewhere queryable.
• It is not a whole people strategy. It does not replace leadership, work design, culture or fair reward.
• It is not a validated result. It is a coherent design resting on credible components. Proving the assembled composite is the next piece of work, and the paper says so.

Where it earns its keep

Once the line exists and is run, the evidence falls out of it. Clause 7.2 of ISO 9001 requires organisations to determine necessary competence, act on gaps and retain documented evidence. Lack of role clarity is a named psychosocial hazard under Safe Work Australia's model Code of Practice, and a clear, levelled role standard is a documentable control for it. You build and run the system so the work is architected to the strategy. The evidence comes as a by-product rather than as separate work.

FAQ

What problem does the People Capability System solve?It ensures the work being done is architected to the strategy. In most organisations strategy is retrofitted onto work that already existed, so no line can be traced from a bet to a task.

Is the People Capability System a capability framework?No. A capability framework is one artefact the system produces. The system is the architecture that connects that framework upward to strategy and downward to competencies and skills, and then runs it.

What does a clear and accepted line mean?Clear means traceable in both directions, from a bet to a task and back. Accepted means leadership owns the bets and the people in the roles agree the line genuinely runs through their work.

How is capability different from competency here?Capability is durable and belongs to the person across roles. Competency is scoped to a role and describes what good looks like in it, at a defined level. Capability survives a change of job. Role competencies are rebuilt around the new one.

Is there evidence behind it?The components are individually well evidenced. The assembled system is a proposition rather than a proven result, and the working paper is explicit about that gap.

‍