A capability is the demonstrated ability of a person, team, organisation or system to produce a class of outcomes under stated conditions.
Teaching algebra, processing payments, manufacturing components, detecting fraud, restoring a service, forecasting demand and operating safely are all capabilities. Capabilities differ from skills because they combine people, tools, processes, resources, authority and readiness into something that can actually perform.
Quick answer: how should capabilities be categorised?
- Function: what outcome can the capability produce?
- Maturity: emerging, repeatable, managed, optimised?
- Capacity: how much can it deliver?
- Readiness: can it operate now under required conditions?
- Dependency: what people, systems, resources and authorities does it rely on?
- Evidence: what proves the capability exists?
- Resilience: how well does it perform under disruption?
- Transferability: can it operate in another context?
- Lifecycle: growing, stable, degrading, retired?
- Ownership: who maintains and develops it?
This article complements How to Categorise Skills, How to Categorise Resources and How to Categorise Roles. Skills are components of capability; capability is the integrated ability to perform.
Capability is not skill
A person may possess a skill without the tools, authority or operating conditions needed to turn that skill into organisational capability.
Capability is not capacity
Capability answers whether a function can be performed. Capacity answers how much of that function can be delivered over time.
Capability is not resource
Resources such as staff, money, machines and data are inputs. Capability is what those resources, combined with process and know-how, allow the system to do.
Functional capabilities describe what can be done
Teach, diagnose, manufacture, transport, analyse, publish, repair and govern are capability families defined by outcome.
Operational capabilities sustain current work
They keep the organisation or system functioning reliably under expected conditions.
Strategic capabilities create future advantage
Research, adaptation, learning, innovation and rapid reconfiguration can matter even when they are not used every day.
Core capabilities support the mission directly
They are central to the reason the organisation or system exists.
Enabling capabilities support other capabilities
Finance, IT, procurement, training and governance often enable core performance without being the final service themselves.
Maturity describes repeatability
An emerging capability may depend on a few individuals; a mature capability is documented, measurable, repeatable and less fragile.
Readiness describes present usability
A mature capability can still be temporarily unready because a critical dependency is unavailable, certification has expired or capacity is exhausted.
Capacity should be quantified where possible
Students taught per week, transactions processed per second, units manufactured per day or incidents handled per hour turn vague capability claims into measurable operating ranges.
Quality belongs beside capacity
High throughput with unacceptable error rates is not equivalent to high-performing capability.
Dependencies reveal fragility
A capability may rely on one expert, one supplier, one dataset or one platform. Dependency concentration should be part of capability classification.
Substitutability improves resilience
Cross-trained staff, interchangeable suppliers and modular systems reduce the chance that one missing dependency destroys capability.
Resilient capabilities preserve function under stress
They may use redundancy, degraded modes, buffers and recovery procedures to continue operating during disruption.
Transferable capabilities work across contexts
A capability tied tightly to one tool, market or individual may not transfer well. Transferability depends on what must remain constant for performance to persist.
Evidence should show performance, not aspiration
Plans, job descriptions and equipment lists do not prove capability. Demonstrated outcomes, tests, audits and operating history provide stronger evidence.
Latent capability differs from active capability
An organisation may retain trained people and designs for a function it is not currently exercising. Reactivation time and dependency readiness matter.
Capability decay is real
Skills fade, equipment ages, suppliers disappear and procedures become obsolete. Unused capability should not be assumed permanent.
Capability building has stages
Acquire knowledge, establish process, assemble resources, test, repeat, scale and govern. These stages can be classified separately from the final mature state.
Capability ownership should be explicit
Someone should own development, readiness, performance evidence and retirement even when many roles contribute.
Capability maps improve planning
Linking capabilities to goals, processes, roles, resources, risks and dependencies reveals where investment or redundancy will create the most value.
AI can appear capable without durable operating capability
A model demonstration under one prompt is not the same as a governed capability with repeatable quality, monitoring, permissions and recovery.
A practical capability record
- capability ID and name;
- function and outcomes;
- maturity;
- current readiness;
- capacity;
- quality measures;
- roles and skills required;
- resources and dependencies;
- authority and permissions;
- evidence of performance;
- resilience and recovery;
- transferability;
- owner;
- lifecycle state and version.
The deeper idea
Capability is potential made operational. It exists only when knowledge, resources, authority and process come together strongly enough to produce repeatable outcomes.
To categorise a capability well is to know what outcome it can produce, how mature and ready it is, how much it can deliver, what it depends on and what evidence proves the ability is real.
Final answer
Categorise capabilities by function, maturity, capacity, readiness, dependency, evidence, resilience, transferability, ownership and lifecycle. Keep capability separate from individual skill or raw resources, and require demonstrated performance before treating an intended ability as an operational one.