The Problem the People Capability System Solves

The problem is not that organisations lack capability. It is that the work being done was never architected to the strategy. It was already there, and the strategy got laid over the top of it afterwards.

That single inversion is what the People Capability System exists to correct. The full working paper is at peoplecapabilitysystem.com.

What problem does the People Capability System solve?

The People Capability System solves the problem of work that is not architected to the strategy. In most organisations, the roles, frameworks and skills came first, and the strategy was mapped onto them afterwards. The system reverses the direction, so the work is intended to the strategy, with a clear and accepted line from a strategic bet down to a discrete task.

Everything else in this article is a consequence of that.

Mapping is not architecture

This is the distinction the whole argument turns on, so it is worth being exact.

A mapping takes two structures that were written independently and draws lines between them. The capability framework was built from the work as it currently stands. The strategy was written by the executive. Somebody then produced a slide showing which capabilities support which priority. It looks like alignment. It is an annotation.

An architecture derives each layer from the layer above it. The capabilities exist because a bet required them. The competencies exist because a capability had to be delivered in a role. The skills exist because a competency needed them. Nothing was written independently, so there is nothing to reconcile.

The test is simple. If a strategic bet changes, does anything below it move on its own? In a mapped structure, nothing moves, because the connections were commentary. In an architected one, everything below has a derivation that now has to be revisited.

Almost every capability architecture I have audited is a mapping wearing an architecture's clothes.

What a mapped architecture costs you

It shows up as ordinary questions that should be answerable in a morning and are not answerable at all.

• Which capabilities does this strategy require, and at what level? There is no answer, because the capabilities were derived from the current work, not from the bets.
• Is this role staffed to the standard it should meet? The position description was authored by hand two years ago and the competencies in it have drifted, so the standard itself is unreliable and the comparison is meaningless.
• Where is the gap, and what closes it? The learning catalogue is not derived from the competency framework, so spend goes to whatever content exists rather than to the gap that matters.
• Can we execute this strategy with the people we have? Nobody can answer this, so it gets replaced with a headcount number, which is a different question.
• Where is your evidence of competence? It gets assembled by hand, from sources never designed to talk to each other, every time an auditor asks.

None of these is exotic. They are the basic questions the people function exists to answer.

‍

‍

The line has to be clear

Clear means traceable in both directions.

Point at any skill in the organisation and you should be able to name the bet it serves. Point at any bet and you should be able to name the work that delivers it, in which roles, at what level. If you can only do one of those, you have half a line. If you can do neither, you have a diagram.

This is not an aesthetic standard. It is the operational one. Directing development spend, deciding what to automate, and answering whether the strategy is executable all require the line to be walkable in both directions.

The line has to be accepted

This is the part everyone skips, and I would put it above the design work in terms of what determines success.

Leadership has to own the bets. Not endorse them. Own them, as the actual bets the business is making, rather than as a communications artefact produced for the annual report. If the bets are not real, everything derived from them is derived from nothing.

The people in the roles have to accept the line runs through their work. A line they do not believe is a line they will ignore the first time it costs them something, and it will not survive the next reorganisation. This is where most capability architectures quietly die, and it is a behavioural and political problem rather than a methodological one.

An architecture that is correct and unaccepted produces nothing. I would rather have a rougher line that people believe than a perfect one they do not.

Why artificial intelligence makes this urgent

Fragmented, retrofitted people architecture is not a new problem. It has become an unignorable one.

As tasks shift to automation and augmentation, the live question inside every organisation is what humans still do and to what level they need to do it. That question is asked at the task and skill layer. It is answerable only if the skill layer connects upward to role competencies, to durable human capability, and finally to a strategic bet.

So the organisations that most need to reason about work at the task level are precisely the ones whose people architecture is least able to. They can tell you what people do. They cannot tell you which of it the strategy actually needs.

Why another framework does not fix it

The reflex is to commission a better framework. I have been paid to do exactly that, and it is usually the wrong move.

A new framework built the same way, from the work as it stands, mapped to strategy at the end, fails in exactly the way the old one did. The quality of the artefact was never the variable. The direction of derivation was. This is the failure mode I keep returning to when I write about capability frameworks, and adding a fifth domain fixes none of it.

How the system answers it

One architecture, four layers, built once from the top and run continuously from the bottom.

Building downward creates the line. Name the bets. Derive the human capabilities those bets require, across all roles. Define the competencies each role needs, with proficiency levels and observable indicators. Specify the skills underneath. Generate the position descriptions from the competency framework and the skills taxonomy rather than writing them freehand, so they cannot drift away from the line.

Running upward reads it. Is the skill present at the required level. Is the competency evidenced rather than claimed. Is capability deep enough across the workforce. Given the people we have, is this strategy executable.

The questions at the top of this article stop being research projects and become reads.

The by-product

There is a second problem the system solves that nobody goes looking for.

Three separate obligations already ask you to hold versions of the same material. Clause 7.2 of ISO 9001 requires you to determine the competence necessary for work affecting quality, act on gaps, and retain documented evidence. Lack of role clarity is a named psychosocial hazard in Safe Work Australia's model Code of Practice, and a clear, levelled role standard is a documentable control for it. And when the Fair Work Commission weighs whether a dismissal was harsh, unjust or unreasonable, it looks at whether the person was held to a clear expectation and given a real opportunity to improve, under section 387 of the Fair Work Act.

All three want a clear standard for the role, evidence of competence against it, and a record of the development offered to close the gap. Architect the work to the strategy and run it, and that material is ordinary output. The system informs those regimes. It does not discharge any of them, and it should never be sold as if it does.

FAQ

What is the core problem the People Capability System solves?The work is not architected to the strategy. Roles, frameworks and skills came first, and strategy was mapped onto them afterwards, so there is no line to trace from a bet to a task.

What is the difference between mapping and architecting?A mapping annotates two structures written independently, and it decays because neither moves when the other does. Architecting derives each layer from the one above, so the connection is structural.

Why does the line need to be accepted as well as clear?Because an unaccepted line gets ignored the first time it costs someone something. Leadership has to own the bets, and the people in the roles have to agree the line runs through their work.

Why can't a better capability framework solve this?Because a framework built from the current work and mapped to strategy afterwards fails the same way regardless of how well it is written. The direction of derivation is the variable, not the quality of the artefact.

Does the system solve compliance problems too?It informs them. Running it produces the competence evidence and documented role standard that quality, safety and fair-process obligations separately ask for. It does not replace a quality management system, a safety programme or a properly run process.

‍