What is the difference between a capability framework and a competency framework?

The terms overlap and are often used interchangeably. In common Australian usage, a competency framework describes discrete skills or behaviours required to perform tasks, while a capability framework is broader — it covers the skills, knowledge and behaviours needed now and in the future, described at multiple proficiency levels and mapped across role families. The practical distinction is scope and levelling, not one being more rigorous than the other.

How many capabilities should a framework contain?

Fewer than most first drafts. Frameworks with twelve to twenty capabilities across three or four groups tend to stay usable; those with fifty become an assessment burden nobody sustains. If two capabilities are always assessed together, they are one capability.

How long does it take to build a capability framework?

For a single organisation of moderate size, expect a few months from first interviews to a tested, mapped framework — the drafting is fast, the consultation and role mapping are what take time. We scope each engagement individually rather than quoting a standard duration.

Can we adapt an existing public framework instead?

Often, yes, and it can be a sensible starting point. The APS and NSW public sector frameworks and SFIA are all freely available. We would still expect to rewrite the capability descriptions in your language and build the role profiles from your roles — that is the part that determines whether people use it.

How do we stop the framework being ignored once it is written?

By changing the processes that surround it in the same project. If position descriptions, selection criteria, development conversations and promotion decisions all reference the framework, it stays alive. If none of them do, no amount of launch communication will save it.

How do we know whether our existing framework is actually working?

Ask three questions of each capability in it: can you name the method that assesses it, can you show movement on it at team level over the last twelve months, and can you point to one decision in the last year where its result was referenced? The capabilities that survive all three are your real capability infrastructure. For most organisations the number is smaller than expected.

Free Organisational Health Check

Self-assessment of your organisation's health.Receive scored report at no cost, no obligation.Delivered by our sister company, Perceptn.

Service

Capability frameworks

Define what good looks like at every level, in language your people recognise.

What is a capability framework?

A capability framework is a written definition of the skills, knowledge and behaviours an organisation needs, described at each level of proficiency and mapped to its roles. It answers a question most organisations answer informally and inconsistently: what does good look like in this job, and what would the next level look like?

A framework is not a competency list, though it usually contains one. The list names the capabilities; the framework adds the levels, the observable behaviours at each level, and the connection to real roles — which is what makes it usable in recruitment, promotion, development and workforce planning rather than decorative.

How a capability framework is structured

Most workable frameworks share the same four layers. The detail differs; the architecture rarely does.

Capability groups — a small number of domains, typically covering technical or professional practice, personal effectiveness, working with others, and leadership or stewardship of resources.
Capabilities — the individual named capabilities inside each group, expressed in the organisation's own language rather than borrowed phrasing.
Proficiency levels — usually four or five, from foundational through to expert or strategic, each described by what a person at that level can be observed doing.
Role profiles — the required level of each capability for a given role or role family, so a person can compare where they are with what the role asks.

Published frameworks worth knowing

Several public frameworks are freely available and useful as reference points: the Australian Public Service Commission's Work Level Standards and integrated leadership material, the NSW Public Sector Capability Framework, and SFIA for digital and technology roles. They are well constructed and worth reading before commissioning anything.

They are also written for a workforce that is not yours. Adopting one wholesale usually produces a document people recognise as generic and quietly ignore. The productive approach is to borrow the architecture and write the content from your own roles, values and work.

What a capability framework is used for

A framework earns its place when it is wired into decisions rather than filed. Used well, the same document supports recruitment (job design and structured selection criteria), development (identifying the gap between current and required proficiency), promotion and progression (a defensible basis for a decision), workforce planning (where capability is concentrated and where it is thin), and succession (which critical roles have no viable internal successor).

Used poorly, it becomes a folder on the intranet. The difference is almost never the quality of the writing — it is whether the framework was built with the people who have to use it, and whether the existing processes were changed to reference it.

A framework nobody is measured against is decoration

The most common state of capability work in large organisations is a well-designed model on the intranet that no one is assessed against. A framework that is not measured cannot be used as evidence, so promotion, development spend and succession decisions carry on being made on impression — borrowing the framework's vocabulary to give the conversation a structured appearance.

Three conditions separate a measured framework from a published one: every capability has an assessment method a manager or peer can complete about another person; assessment runs on a cadence so movement is visible over time; and decisions visibly reference the results. Test your own framework with three questions per capability — can you name the method that assesses it, can you show movement at team level over the last twelve months, and can you point to one decision in the last year that cited it?

The remedy is rarely a new framework. Most existing ones are serviceable; the work is instrumenting the one you have. Where validated multi-rater measurement is needed for that, we work alongside Perceptn.

The problem

Without a shared definition of capability, recruitment, promotion and development decisions rest on individual judgment. That's inconsistent at best and indefensible at worst — and it makes career progression invisible to the people who most want to see it.

The other common failure is the opposite one: a framework exists, but it was bought rather than built, describes generic behaviours nobody recognises, and has never been connected to a single real decision.

The method

We build capability frameworks grounded in the organisation's own values and work: role profiles, proficiency levels for each capability, and career pathways that show people what the next step actually requires.

The work runs in four stages. We start with the work itself — role documentation, interviews and observation — before drafting anything. We then draft a capability taxonomy and proficiency scale and test it with the people who will be assessed against it. We map role profiles and career pathways. Finally we set out how recruitment, development and performance processes need to change so the framework is actually used.

What you receive

A capability taxonomy expressed in your organisation's language
Proficiency levels with observable behavioural indicators at each level
Role profiles with required proficiency by capability
Career pathways showing realistic progression routes
A capability heatmap identifying strengths and development priorities
Implementation guidance for recruitment, development and performance processes

Who this suits

Organisations formalising workforce planning, addressing succession risk, or responding to staff who can't see a future with them.

Capability frameworks that get used

Our whitepaper on the four layers of a workable framework, the three ways levelling usually fails, a four-stage build method, and a commissioning checklist.

Read the whitepaper

Common questions

What is the difference between a capability framework and a competency framework?: The terms overlap and are often used interchangeably. In common Australian usage, a competency framework describes discrete skills or behaviours required to perform tasks, while a capability framework is broader — it covers the skills, knowledge and behaviours needed now and in the future, described at multiple proficiency levels and mapped across role families. The practical distinction is scope and levelling, not one being more rigorous than the other.
How many capabilities should a framework contain?: Fewer than most first drafts. Frameworks with twelve to twenty capabilities across three or four groups tend to stay usable; those with fifty become an assessment burden nobody sustains. If two capabilities are always assessed together, they are one capability.
How long does it take to build a capability framework?: For a single organisation of moderate size, expect a few months from first interviews to a tested, mapped framework — the drafting is fast, the consultation and role mapping are what take time. We scope each engagement individually rather than quoting a standard duration.
Can we adapt an existing public framework instead?: Often, yes, and it can be a sensible starting point. The APS and NSW public sector frameworks and SFIA are all freely available. We would still expect to rewrite the capability descriptions in your language and build the role profiles from your roles — that is the part that determines whether people use it.
How do we stop the framework being ignored once it is written?: By changing the processes that surround it in the same project. If position descriptions, selection criteria, development conversations and promotion decisions all reference the framework, it stays alive. If none of them do, no amount of launch communication will save it.
How do we know whether our existing framework is actually working?: Ask three questions of each capability in it: can you name the method that assesses it, can you show movement on it at team level over the last twelve months, and can you point to one decision in the last year where its result was referenced? The capabilities that survive all three are your real capability infrastructure. For most organisations the number is smaller than expected.

Discuss an engagement

Most engagements begin with a short, confidential conversation about the question you are trying to answer. There is no cost or obligation attached to that discussion.

Make an enquiry