What the People Capability System Is Not
A system is more trustworthy when it is clear about what it does not do. Most things in this field are sold on their reach, which is why they end up promising to run performance management, fix culture, satisfy the regulator and improve retention, all from the same slide. The People Capability System is deliberately narrower, and this article is about the boundaries.
The full working paper, including the limits section this draws on, is at peoplecapabilitysystem.com.
What is the People Capability System not?
The People Capability System is not a rating engine, not a performance management process, not an organisational capability model, not a software platform, not a compliance product, and not a validated result. It is an architecture that intends the work to the strategy and produces a clear and accepted line from a strategic bet to a discrete task, so that capability can be seen and developed.
Everything below is a boundary I would hold under pressure.
It is not a strategy
Worth saying first, because it is the boundary the framing invites people to miss.
The system architects the work to the strategy. It does not produce the strategy. Strategy is the input, and it is the one layer the system does not build. If the bets are not explicit, or leadership will not own them as the actual bets rather than as a communications artefact, the system has nothing to derive from and it will fail. It cannot rescue a vague strategy. It exposes one, which is uncomfortable and useful, and which is not the same as fixing it.
It is not a rating engine
The system measures capability in order to develop it. It does not rank people. It does not rate them. It does not discipline anyone.
This is the sharpest boundary in the whole thing, and it is not a philosophical preference. It is a design constraint that keeps the system working. The moment a development system is repurposed as a surveillance or policing tool, people stop giving it honest evidence, and the data that made it useful degrades within a cycle. You end up with inflated self-assessments, defensive supervisors, and a matrix nobody believes.
It is also how you lose acceptance, which is fatal. A line the people in the roles believe is being used against them is a line they will resist. Keeping the system development-only is what keeps it working.
It does not run performance management
The related and most commonly misunderstood boundary.
The system holds the documented standard for the role and the evidence of where a person sits against it. A performance process can draw on that material, and it will be better for having it, because a great deal of manager time goes into constructing a standard from scratch every time one is needed. What the system does not do is run the conversation, own the outcome, or produce a rating.
It informs performance management. It is not performance management. If you have read my writing on competency frameworks you will know I hold the same line there, for the same reason.
It is not organisational capability
Capability here is human. It is a broad, durable area of ability a person owns and carries across roles.
What an organisation collectively can do is a different construct. The dynamic capabilities literature describes how firms sense and reconfigure under change, and it is genuinely useful work. It is deliberately out of scope, because letting the word capability mean both things at once is precisely the conflation that stops an architecture from tracing anything.
If your framework uses capability to mean organisational capacity, that is a legitimate usage. It is just not this one, and the two should not run in the same structure.
It is not a skills taxonomy, and it is not a capability framework
Both are artefacts the system produces. Neither is the system.
A skills taxonomy classifies skills so a skill means the same thing wherever it appears. A capability framework is the organisation-wide structure of durable human capabilities. Each sits at one layer. The system is the derivation that connects the layers to the strategy, plus the operating model that runs them.
This matters because the field has a habit of buying an artefact and expecting it to behave like a system. It will not, and it never has.
It is not a software platform
The system does not depend on any vendor and it is not something you procure.
It does need a system of record, because the artefacts have to live somewhere queryable rather than in documents and slide decks. That is usually the HR system you already run. Buying a tool without designing the architecture is the same mistake as building the framework without designing the run.
It is not a compliance product
Running the system produces evidence that quality, safety and fair-process obligations already ask you to hold. That is a real by-product. It is not a discharge of any duty.
It does not replace a quality management system. Clause 7.2 of ISO 9001 requires determined competence, action on gaps, and retained documented evidence, and the system produces that material. The audit is still an audit.
It does not run a workplace safety programme. Lack of role clarity is one named psychosocial hazard in Safe Work Australia's model Code of Practice, and a clear levelled role standard is a documentable control for that one hazard. The duty is broad, covering job demands, support, organisational justice and much else the system does not touch. Controlling role clarity is one control, not a discharge of the duty, and it should always be presented that way. Anyone telling you otherwise is overselling.
It does not conduct dismissals. What it holds is the documented role standard and the record of development offered against it, which a separate and properly run process can draw on.
It is not a whole people strategy
The system is an architecture for capability. It is not a substitute for leadership, for the design of the work itself, for culture, or for fair reward. Those things sit outside it and matter as much.
The claim is bounded. This is the structure that architects the work to the strategy and produces a clear, current, role-based view of human capability. It is not the whole of the people function, and a capability architecture inside a badly led organisation will produce excellent evidence of a problem it cannot solve.
It is not a validated result
The most important boundary, and one I would rather state myself than have someone else state for me.
What the working paper sets out is a case that the architecture is coherent, that its parts are individually credible, and that the assembly should produce performance and evidence. It is not an empirical study of this specific assembly in a specific organisation. The components are evidenced one layer at a time, and a set of individually validated parts does not entail a validated whole.
The honest status is a well-grounded design awaiting evidence. The paper states its propositions so that a negative result is possible, which is the point of stating them. Scepticism until that proof exists is the correct response, and it is the response I am asking for.
FAQ
Is the People Capability System a performance management system?No. It holds the documented role standard and the evidence of where a person sits against it. A performance process can draw on that. It does not rate, rank or run the conversation.
Does the People Capability System produce the strategy?No. Strategy is the input, and it is the one layer the system does not build. It cannot rescue a vague strategy, though it will expose one.
Does it replace my capability framework?No. A capability framework is one of the artefacts it produces, sitting at one layer. The system is the architecture that derives the layers from the strategy and runs them.
Does it satisfy the psychosocial hazard duty?No. A clear, levelled role standard is a documentable control for one named hazard, lack of role clarity. The duty is broad and covers much the system does not address.
Has it been proven to work?No. The components are well evidenced individually. The assembled system is a proposition, and the paper sets out testable propositions precisely so it can be falsified.