We used to call it a competency framework.
When AbilityMap was first built, the language seemed straightforward. Competency was the term every HR professional knew. It’s what the textbooks used, what the job ads referenced, what the industry conferences put in their session titles. If you were building a framework to assess people, you called it a competency framework. So we did too.
But then a rather impassioned internal debate ensued. CEO and co-founder Mike Erlin had spent years in the higher education sector at Blackboard, where competency meant one thing: certification. A checklist. A credential. Always backward-looking. And what fellow co-founder Kevin Chandler had built with AbilityMap was something fundamentally different: a criterion-referenced, forward-looking modelling tool.
The NSW public sector had recently switched terminology from competency to capability. Mike was adamant, AbilityMap needed to follow suit. โCalling it a competency framework felt like putting a backwards label on a forward-looking product.โ
To most people, the words feel interchangeable. But thereโs a nuance in the difference that really matters. A difference that HR leaders should understand and care about.
The problem wasn’t the framework. It was the word.
The capability vs competency question isn’t new. People in talent management have been circling it for years. But most of the time it gets treated as a terminology debate, two words that roughly mean the same thing. They don’t.
Competency, in most organisations, has come to mean one thing: can this person do the job? It’s a backwards-looking lens. Competency refers to a set of demonstrated knowledge, skills and behaviours that someone has shown in previous roles. You assess someone’s competency by looking at what they’ve already performed. Their experience. Their qualifications. Their track record. You build the framework by documenting what a successful person in the role has done before, and then you measure new candidates against that template.
This works fine when the job stays the same. When the environment is stable, the role is well-defined, and tomorrow looks roughly like yesterday. For a lot of the 20th century, that was a reasonable assumption.
It’s not a reasonable assumption anymore.
Roles are changing faster than job descriptions can keep up with. Entire human abilities that mattered five years ago are being automated. The skills that got someone hired eighteen months ago may already be outdated. In this environment, competency refers to a snapshot that’s already fading by the time you take it. And the biggest predictor of whether someone will succeed in a role isn’t whether they’ve done it before. It’s whether they have the underlying behavioural and cognitive capacity to adapt, learn and perform in an environment they haven’t encountered yet.
That’s not competency. That’s capability.
What competency actually measures (and what it misses)
The competency approach asks one question: has this person demonstrated the required knowledge, skills and behaviours in the past?
That question has value. Nobody is arguing it doesn’t. But it has three significant blind spots.
It rewards experience over potential. The competency approach inherently favours people who have had the opportunity to demonstrate behavioural competencies in previous roles. That means candidates from the right universities, the right companies, the right career paths. It systematically disadvantages people who have the underlying ability but haven’t yet had the chance to prove it. Graduates, career changers, people from non-traditional backgrounds. The talent pool narrows before you’ve even started assessing.
Vanessa Goryl, AbilityMap’s Outcomes Director, puts it bluntly: competency only captures what’s been observed and demonstrated while someone was being watched. People might have extraordinary capability in areas they’ve simply never had the opportunity to show, or that they’ve shown, but not while anyone with a clipboard was paying attention. That’s not a true reflection of someone’s ability, and it’s certainly not a reflection of their potential.
It assumes the role is static. Competency models are built by studying what successful people in a role do today. They help employees self-assess against a clear description of behaviours at different levels, which is useful for performance management and career progression. But what if the role changes? What if the organisation restructures, the technology shifts, the market moves? A model built around competencies in 2022 might be measuring the wrong things by 2025. The Association for Talent Development recognised this problem so clearly that they retired their own competency model and replaced it with a capability model, specifically because competency described a fixed state while capability described the power to generate outcomes in changing conditions.
It confuses “has done” with “will do.” Someone can demonstrate competency in one environment and fail completely in another. The behaviours that made them successful at their previous company may not transfer. Competency assessment tells you what someone did. It doesn’t tell you what they’ll do in your environment, under your kind of pressure, within your team dynamics. Two people can hold the same qualification, complete the same training, and demonstrate the same skill in a controlled environment. But only one of them might have the underlying capability to apply that skill consistently when the pressure is real and the conditions are messy.
What capability measures instead
Capability is a different question entirely. It doesn’t ask “can this person do the job?” It asks: does this person have the desire, will, and stamina to apply their skills consistently in the conditions this work demands?
The distinction between capability and competency is subtle but consequential.
A competency is a state of being. You either have it or you don’t, based on evidence of past performance. A capability is a capacity for action. It’s about propensity, motivation and the drive to persist. It doesn’t require that someone has already done the thing. It assesses whether they will do it, naturally and sustainably, when the situation demands it. Capability sits between having a skill and actually using it. It governs whether those skills are applied, sustained, and effective in the real work context.
Put simply: when businesses compare capability and competency side by side, the roles become clear. Competencies drive performance management and recruitment against current requirements. Capabilities drive business strategy and future planning. Competency development is about training people in current tools and behaviours. Capability development is about building the capacity for future growth. Both matter. But they answer very different questions.
Consider something like communication skills. A competency-based approach asks whether a communications manager has demonstrated strong client interactions and issue resolution in the past. A capability framework asks whether they have the underlying communication capabilities (active listening, empathy, clarity under pressure) to handle situations they haven’t encountered yet. The competency tells you what they did at their last company. The capability tells you what they’ll do at yours.
But communication is also a good example of why precision matters. Take two bodies of work that both “require strong communication”: business development and account management. At a surface level, they look similar. But business development requires building networks fast, initiating contact, opening doors. Account management requires building relationships in depth over time. Trust. Continuity. Nuance. Both are trained as communication skills. Both draw on different underlying capabilities. Treat them as interchangeable, and you introduce friction that reduces the impact of even well-designed training.
Here’s another example. Take two candidates for a business development role. Both have experience in sales. Both can point to deals they’ve closed. By any competency model, they’d score similarly.
But one of them lights up in a room full of strangers. They initiate conversations, build rapport quickly, and leave feeling energised. The other can do it, but it costs them. They prepare extensively, perform well in the meeting, and then need to recover afterward. Both are competent. Only one has high capability in that behaviour. And that difference shows up three months into the role, when the first candidate is thriving and the second is burning out.
As AbilityMap’s CEO Mike Erlin frames it: “Everyone’s been trained and certified. How come one person performs and one doesn’t? Capability. They have natural capability for that environment.”
Competency told you they could both do the job. Capability tells you which one will still be doing it well a year from now.
Why the industry is shifting
AbilityMap isn’t alone in making this move. The capability vs competency conversation is happening across the talent management industry, and the shift toward capability is driven by three forces.
The skills half-life is shrinking. Technical skills that took years to develop now become obsolete in months. Frameworks built around specific competencies age out faster than organisations can update them. Capability frameworks, because they measure underlying behavioural and cognitive traits rather than specific technical skills, remain relevant even as the surface-level requirements of a role change. Soft skills like critical thinking, emotional intelligence and continuous learning don’t expire the way a software certification does. That’s why organizational capabilities built around these traits have become a strategic driver for companies planning beyond the next quarter.
AI has made competency easier to fake. When candidates can use AI to polish their CV, rehearse interview answers, and generate work samples, the traditional markers of competency become unreliable. You can’t assess competency through a cover letter anymore. Capability assessment goes beneath the surface to measure traits that can’t be fabricated: how someone processes information, how they respond to pressure, how they naturally interact with others.
Organisations need to assess propensity, not just performance. This is especially true in graduate hiring, internal mobility and succession planning, where the whole point is to identify people who will grow into roles they haven’t done yet. A competency-based model is structurally incapable of doing this, because it requires evidence of past performance that doesn’t exist. A capability framework defines the role requirements differently. It asks what resources and traits should be in place for someone to meet long-term business goals, not just today’s job description. That means it can assess someone’s suitability for a role they’ve never held, based on the behavioural and cognitive patterns that predict success in that environment.
Australia’s public sector made this shift years ago, retiring competency frameworks in favour of capability frameworks across state and federal government. However, despite being somewhat ahead of the curve, in large part, the measurement and assessment often still relies on observed behaviour and manager judgement. The language moved forward. The methodology, in many cases, didn’t. That’s the gap AbilityMap set out to close.
Why we changed the name (and what it cost us)
The capability and competency debate isn’t academic. When AbilityMap switched from “competency” to “capability,” it wasn’t a marketing exercise. It was a product decision that came with real trade-offs.
“Competency framework” is the term most HR professionals search for. It has roughly four times the search volume of “capability framework.” Every time someone types “competency framework” into Google, they’re using the language we deliberately walked away from. From a pure visibility standpoint, it would have been easier to keep using the competency label and benefit from the existing demand.
We chose not to, because the language shapes the thinking. If you call it a competency framework, people use it like one: as a checklist of demonstrated skills. They look backwards. They hire for what someone has done, not what they’ll do. They build static models that age out. They default to the limitations we were trying to solve.
Calling it a capability framework forces a different conversation. It shifts the focus from “has this person proven they can do the job?” to “does this person have the capacity to thrive in this environment?” That’s a fundamentally different question, and it leads to fundamentally different hiring, development and deployment decisions. The difference between capability and competency isn’t semantic. It’s structural.
The 31 capabilities in AbilityMap’s framework aren’t a list of things someone has done. They’re a map of how someone thinks, works, communicates, solves problems, leads, learns and manages themselves. Measured across 8 domains (Communication, Teamwork, Managing People, Planning & Organising, Initiative & Enterprise, Learning, Self-Management and Problem Solving), they paint a picture of the whole person, not just their resume.
What this means in practice
None of this is to say the competency approach is useless. It’s not. In regulated industries where you need to verify that someone can perform a specific procedure to a defined standard, competency assessment is exactly the right tool. You wouldn’t want your surgeon to be assessed on “potential.” And organisational competencies still have a clear role in everyday task execution, ensuring that a computer technician has the technical skills to maintain system security, or that customer service staff can meet the specific skills required to be productive in their role.
But for the vast majority of knowledge work, professional services, graduate hiring and leadership development, the question that matters most isn’t whether someone has done the job before. It’s whether they have the underlying desire and stamina to do it well, in your specific context, over the long term.
That’s what capability assessment answers. The gap between capability and competency isn’t theoretical. It shows up in every hire that looks perfect on paper and underdelivers in the role. And it’s why we made the switch.
Understanding employee capabilities changes how managers assign work, structure teams and plan professional development. When you map employee capabilities properly, you stop slotting people into job descriptions based on what they’ve done and start deploying them based on what they’re actually wired to do well. Organizational capabilities grow from the bottom up when individuals are placed where their natural strengths meet the work that needs doing. That’s how organizational capabilities become a genuine competitive advantage rather than a buzzword in the annual report. Capabilities underpin any training and development program worth running, because they ensure that all learning activities align with business strategy and desired outcomes rather than just ticking a compliance box.
When organisations understand the real difference between capability and competency, they stop treating people as a list of past achievements and start treating them as a set of possibilities. The competitive advantage isn’t just in hiring better. It’s in knowing what your people are actually capable of, and building around that.
If you’re still using a competency-based approach and it’s working for your organisation, there’s nothing wrong with that. But if you’re finding that your hires look good on paper and underperform in practice, that your frameworks feel static and disconnected from how work actually gets done, or that you’re missing high-potential candidates because they don’t fit the traditional profile, the problem might not be your people. It might be your lens.
The capability and competency distinction matters most when the stakes are highest: hiring for roles that don’t exist yet, developing leaders who’ll face problems nobody’s anticipated, and building teams that can adapt when the plan falls apart. AbilityMap’s Capability Framework measures 31 cognitive and behavioural capabilities across 8 domains. See how it works โ
