Ask an HR leader and a frontline supervisor what their people can do, and you’ll get two good answers that probably won’t match. The supervisor will name competencies like “setting alarm limits on the 4 West tele monitors” or “locking out the Line 2 filler before a changeover,” specific work they watched someone prove on last week’s shift. The HR leader will name skills like “patient assessment” or “preventive maintenance,” broader abilities that sit in a job profile and point to a career path. Both are describing what people can do, just from different distances.
On the frontline, a competency is a specific piece of work someone has proven they can do to a set standard, confirmed on the job by a qualified validator. Competencies are granular on purpose. They’re often tied to a procedure, a piece of equipment, or a regulatory requirement, and they tell supervisors, educators, and safety teams exactly who is ready for which task on a given shift.
Talent and HR leaders look at the same workforce from a wider view. For them, skills are the consistent units of work the organization hires, develops, and plans around across every site and role. That broader language is what makes internal mobility, succession planning, and workforce planning possible, and it’s the language the skills-based organization conversation is built on.
Capabilities connect the two views. A capability is an integrated piece of work the organization needs people to be able to do, like telemetry monitoring or multi-axis CNC setup, and each one draws on several competencies proven at specific sites. In Workday and most other HR systems, capabilities are recorded as skills, so when HR talks about skills, it’s usually talking about capabilities. The challenge is that few organizations can see what their frontline can collectively do, because the evidence lives in competencies that rarely make it into enterprise HR systems.
Frontline teams work in competencies, and HR works in skills, which is where most of the skills vs. competencies confusion starts. It plays out the same way in healthcare, manufacturing, energy, and field services.
Table of Contents
Three Takeaways
- Competencies, skills, and capabilities describe the same workforce at different distances. The frontline proves specific competencies, while HR plans with broader skills. In Workday and most HR systems, those skills play the same role as capabilities.
- Nobody has to give up their language. Each site can keep the competencies it already validates, and those competencies can still count toward consistent capabilities the whole enterprise can plan around.
- Evidence and recency make the data trustworthy. A capability is only as reliable as the current, validated competencies behind it, and a qualification on file shows authorization, not proof that someone can still do the work today.
Why Skills, Competencies, and Capabilities Get Confused on the Frontline
HR and operations usually start from different places. HR thinks about skills as broader, consistent units of work that support hiring, mobility, development, and workforce planning. Operations, clinical education, and safety teams think in terms of specific tasks done to procedure, the work that keeps people safe, operations running smoothly, and equipment from failing when a step is missed. Both viewpoints are valid, but they rarely line up on their own.
In a Kahuna panel with leaders from Workday, Marsh, and Deloitte on making skills data work across the enterprise, Bill Hehr, Director of Healthcare Strategy at Workday, described “a huge language barrier within healthcare.” He explained that HR talks about workforce planning, talent strategies, and career development, “whereas the clinical side is focused on patient outcomes and patient readiness and compliance.” To HR, a skill might be something broad like patient assessment that shows who could grow into a new role. To a clinical educator, what matters is whether each nurse has proven a specific competency, like aseptic technique, before the next shift.
Kahuna hears the same thing from customers. One healthcare leader noted that HR “wouldn’t necessarily call” hands-on tasks like starting an IV or changing a sterile dressing a skill, even though those are exactly what clinical teams observe and validate every year. Another found that the “competencies” in their HR system behaved more like performance goals, which made that data hard to use for staffing decisions.
Hehr noted that the same divide shows up across other highly regulated industries. When a plant brings in contractors alongside its own employees for a turnaround, leaders need to know that the same work means the same thing for both groups, even when each one describes it differently.
When one word means different things to different teams, the effects add up quickly. Reports from HR and operations don’t match, skills projects stall in debates over definitions, and frontline leaders stop trusting data that doesn’t reflect how their work actually gets done. Jai Shah, CEO at Kahuna, framed the core challenge this way: frontline data is very specific, very granular, and often driven by regulatory requirements, so the question becomes how to translate it into a language the entire enterprise can speak.
Why You'll See These Terms Defined Differently Across the Frontline and HR
Search for the difference between skills and competencies, and most answers describe skills as the building blocks of a competency, with skills at the bottom and competencies above them. The bottom of that ladder matches how many frontline teams talk. They often use “skill” or “skill check” for a specific task or procedure checked on the job, which is part of how someone proves a competency.
The difference shows up at the top. In HR systems, “skill” usually means the broad unit HR plans around, which sits above competencies and plays the same role as a capability. The same word ends up at both ends of the ladder, and that’s where much of the confusion between HR and operations comes from.
| Term | On the Frontline | In HR Systems & the Skills-Based Org Conversation | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Skill | A specific task or procedure checked on the job, often part of proving a competency | The broad, consistent unit HR hires, develops, and plans around, recorded in Workday and most HR systems | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Competency | Work someone has proven on the job to a set standard, confirmed by a qualified assessor | Often skills combined with knowledge and behaviors, and in some HR systems, tied to performance reviews | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Capability | An integrated piece of work that draws on several competencies | Usually recorded as a skill | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The Difference Between Competencies, Skills, and Capabilities
In the skills-based organization conversation, the clearest way to understand skills vs. competencies vs. capabilities is to follow the evidence. Competencies are proven at the site, and skills and capabilities give the enterprise a consistent way to plan around them.
Competency: How the Frontline Proves the Work
A competency is a specific piece of work someone has proven they can do to a set standard. Because it’s observable, a qualified validator can watch the work and confirm it meets the standard. Some teams call this a competency, while others call it a sign-off or a skill check, but the idea is the same. It draws on the knowledge, skills, abilities, and experiences someone brings to the job, applied in a real work setting.
Competencies vary widely in size. Some are specific to one site or one piece of equipment, like telemetry monitor setup and alarm limits on a cardiac step-down unit or lockout/tagout on the Line 2 filler. Others apply almost anywhere the work happens, like arrhythmia recognition and response or reading GD&T on an engineering print. Even a broad competency is still one thing a qualified validator can confirm, which is what keeps it distinct from a capability.
The specific ones are often the most valuable on the floor, and that precision is a strength, not a problem to fix. “Lockout/tagout on the Line 2 filler” tells a validator exactly which equipment, energy sources, and steps to check, while a generic “lockout/tagout” label doesn’t. Flattening every site’s competencies into one corporate list strips out that detail, and supervisors stop recognizing their own work in the data.
Competencies also age. Procedures change, equipment changes, and people who haven’t done a task in a year may not do it the same way today. Expiration and reassessment rules keep competency data tied to what someone can do now, not what they did once.
Skill: How HR Describes the Work
In most HR systems, including Workday, a skill is a consistent unit of work the organization hires, develops, and plans around, such as patient assessment or preventive maintenance. Skills give talent teams a shared language across every site and role, which is what makes internal mobility, succession planning, and workforce planning possible.
The gap is evidence. For office roles, skills data can flow in from resumes, learning records, and employee profiles. For frontline roles, those sources rarely capture what people can actually do, because the proof lives in competencies validated on the job.
Capability: Where the Two Views Meet
A capability is an integrated piece of work the organization needs people to be able to do, described the same way at every site. It’s the same broad unit HR calls a skill, and in Workday and most other HR systems, that’s how it’s recorded. Some examples:
- Telemetry and cardiac rhythm monitoring
- Multi-axis CNC machining setup
- Rotating equipment condition monitoring
Each one draws on several competencies, and it’s described the same way at every site. The competencies people have proven are the evidence behind each capability. Look at everyone who holds it across a unit, plant, or company, and you see how deep the bench is for that work.
Calling it a capability keeps it from colliding with the frontline’s everyday use of skill, but your HR system can keep calling it a skill. It plays the same role and sits at the level where workforce decisions get made, from who to hire and develop to who can float to another unit and which sites are thin on coverage.
A capability is the right size when it’s broad enough that no single sign-off proves it, and specific enough that you could staff a shift or plan a hire around it. “Maintenance” or “patient care” is too broad, since knowing someone can “do maintenance” doesn’t tell you who to send to a failing compressor. A single task or procedure is too narrow, because it’s the scope of a competency.
How Site-Level Competencies Connect to Capabilities
Most frontline organizations run more than one site, and each site tends to name and assess its work a little differently. A large organization can easily have 20 or more competencies, each named differently across its hospitals, plants, or rigs, that cover essentially the same work. Without a connection, the enterprise sees 20 unrelated records. With one, they all count toward a single capability, and one broad competency can count toward more than one. GD&T interpretation, for example, matters for both CNC setup and dimensional inspection.
| Organization | Competencies Behind It (What the Frontline Proves) | Capability (What HR Plans With) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Hospital A | Tele Box Setup and Alarm Limits, 4 West | Telemetry and Cardiac Rhythm Monitoring | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Hospital B | Cardiac Monitor Setup, PCU | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Hospital C | Telemetry Monitoring, Step-Down | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Organization | Competencies Behind It (What the Frontline Proves) | Capability (What HR Plans With) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Manufacturing Plant A | Five-Axis Fixture Setup, Cell 3 | Multi-Axis CNC Machining Setup | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Manufacturing Plant B | Trunnion Table Setup | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Manufacturing Plant C | 5-Axis Machine Setup and Offsets | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Organization | Competencies Behind It (What the Frontline Proves) | Capability (What HR Plans With) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Energy Site A | Vibration Route, Compressor Train B | Rotation Equipment Condition Monitoring | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Energy Site B | Monthly Pump Vibration Readings | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Energy Site C | Compressor Condition Checks | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
With this model, no site needs to rename anything. In healthcare, Hospital A’s educators keep “Tele box setup and alarm limits, 4 West,” and for a manufacturing organization, Plant B’s supervisors keep “Trunnion table setup.” The competencies stay exactly as each site validates them, and they still add up to one consistent capability the enterprise can compare across every hospital, plant, or site. HR and operations can then see who holds what at each site, how deep that bench is, and where coverage is getting thin, without asking a single nurse, machinist, or technician to change how their work is checked.
Where Do Qualifications Fit?
A qualification is the formal authorization, certification, or license that confirms someone is legally, procedurally, or operationally cleared to do the work. A state RN license, BLS or ACLS certification, IADC WellSharp certification, and a forklift operator certification are all qualifications. They usually expire, and they’re central to compliance and audit or survey readiness.
Qualifications don’t sit neatly on the same ladder as competencies and capabilities, because the relationship depends on the work. A qualification can be:
- A prerequisite where a nurse needs a current state RN license before any unit competency counts.
- Part of the evidence where an ACLS certification can count toward a code-response competency, alongside a mock code observed on the unit.
- The proof itself, where for some work, a current certification is what the organization accepts as proof of competency, such as a forklift operator certification that already includes a practical evaluation.
Whatever the relationship, the difference between a competency and a qualification comes down to ability versus authorization. A competency shows someone has done the work to standard, while a qualification shows they hold the authorization the work requires. Most frontline organizations need both. A credential on file doesn’t always show someone can still do the work safely today, and a strong record of competencies doesn’t authorize anyone to practice without a required license. In practice, the strongest definition of “qualified” means holding the credential and current, validated evidence for the work behind it.
How Different Leaders Use the Same Skills Data
Different leaders need different views of the same evidence, because each one makes a different set of decisions. A supervisor running a single shift needs very different information than an HR leader planning across every site.
- Frontline supervisors work with competencies and qualifications, in their site’s own language. They’re accountable for every shift running safely, so they need to know exactly what each person on the crew has proven and which credentials are current.
- Training and education managers also work with competencies and qualifications. They’re responsible for people being ready to work and for passing audits and surveys, so they keep assessments current as procedures and equipment change and keep credentials from lapsing.
- HR and talent leaders work with capabilities, which are the skills in their HR system. They plan hiring, development, internal mobility, and pay across every site, so they need one consistent view and a clear picture of where coverage is thin.
- Operations and staffing leaders use both. Capabilities tell them how many people can do the work at each site, while competencies and qualifications confirm that a specific person is ready for a specific job on a specific shift.
Each of these views depends on the others. The competencies a supervisor confirms on the floor are the evidence behind every capability HR and operations leaders plan and staff around. When the terms connect from one view to the next, everyone works from the same validated data, just zoomed in or out to fit the decisions they make.
Pass/Fail or Skill Proficiency Levels? Why Frontline Teams Often Need Both
Once the terms are clear, the next debate is usually about measurement. Frontline managers often want a simple check, like whether someone can isolate a valve safely. Corporate talent teams often want skill proficiency levels that show growth over time. As one energy leader asked the Kahuna team, “Our competencies are binary…how are we going to define the proficiency?”
Both sides have a point, and each approach has trade-offs.
| Approach | Why It Works | Where It Falls Short | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Pass/Fail | Clear, objective, and easy to tie to a procedure. For a lockout/tagout check, for example, the person either met the standard or didn’t. | It can’t tell someone who passed yesterday under close supervision from a 10-year veteran who coaches others, It tracks compliance, not development. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Multi-Level Proficiency Scale | Shows a path from novice to expert and feeds succession, mobility, and development planning | Generic labels feel subjective on the floor. A “3 out of 5” on equipment operation means little without clear criteria around it. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
A scale is only as useful as the evidence behind each level. When every level is tied to specific, observable tasks, a validator isn’t guessing whether someone is “advanced.” They’re confirming the person did what that level requires, so the scale works like a series of stacked pass/fail checks that stay objective enough for the floor while still showing growth.
There’s no single right number of levels, because it depends on the program, the work, and what the data will be used for. Many organizations keep strict safety and compliance procedures, like emergency shutdowns, confined space entry, or sterile field preparation, as pass/fail. Others use three levels for frontline work, such as “performs with supervision,” “performs independently to standard,” and “leads and teaches others,” and more levels for broad technical work on a multi-year career path, like drilling fluid management. Whatever the number, each level needs to be one a busy validator can reliably tell apart from the next, or the data loses credibility.
Molly Leeds, Skills Solutions Lead at Marsh, notes that the right measure depends on its purpose, whether that’s moving people along a career path, certifying them in a role, developing them, or paying them differently. For some competencies, that means no scale at all.
Connecting competencies to capabilities also takes pressure off the debate. Pass/fail checks can stay pass/fail at the competency level, where supervisors need them. The enterprise still gets a view of depth at the capability level, such as who has proven a wide range of the work behind a capability and who has proven only part of it so far. Pass/fail shows who can do a specific task today. The capability view shows who is ready to take on more, and where development will close the gap fastest.
No matter which scale fits, the most reliable proficiency data comes from validated evidence. On the frontline, that means someone observed the work and a qualified validator confirmed it, rather than relying on self-reported checkboxes or skills inferred from a resume.
How Competencies, Skills, and Capabilities Connect in Practice
Connecting the terms doesn’t require a massive taxonomy project. Mapping a single frontline role from end to end is one of the fastest ways to see how they fit. Sorting that role’s work into the competencies people prove on the floor, the capabilities HR plans around, and the qualifications the role requires tends to surface gaps and disagreements quickly, long before they show up in a system rollout.
Capabilities also help leaders look past job titles, because they describe what people can actually do rather than the title on their badge. A reliability technician at one plant and a maintenance mechanic at another may hold the same capabilities, and someone in a different role entirely may be the right person to cover a gap. Molly Leeds describes a practical test: if two roles with different titles share more than 80% of the same skills, they may really be the same job, which opens the door to more internal mobility. Looking at capabilities makes those comparisons possible across roles and sites, while each site keeps its own competencies.
The connections only hold if someone keeps them current as work changes and new sites come on board, and deciding who does that is one of the first conversations HR and operations need to have. Once they do, the definitions become more than a glossary. As Deloitte’s research puts it, skills create value “when they are applied with intention,” and on the frontline, that starts with competencies, skills, and capabilities that all point back to the same validated evidence.
Where Kahuna Fits
Kahuna started on the frontline, capturing validated competencies where the work happens. With Skills Aggregator, that same evidence now feeds the capabilities the enterprise plans with, so the frontline and HR can work from one set of data.
- Kahuna Skills Manager captures competencies where the work happens, with each one proven on the job and confirmed by a qualified validator. Sites keep their own names and procedures, and expiration and reassessment rules keep the record current.
- Kahuna CertIQ tracks licenses and certifications and their expirations, so credentials and demonstrated competencies sit side by side instead of in separate systems.
- Kahuna Skills Aggregator turns validated competencies from every site into consistent enterprise capabilities, showing who is capable of what, how deep each bench is, and where coverage is thin. Those capabilities flow into Workday, Oracle, Infor, SAP, and other HR systems as skills.
The frontline doesn’t have to change how it works, and HR doesn’t have to change its vocabulary.
Frequently Asked Questions About Skills, Competencies, and Capabilities
What is the difference between skills, competencies, and capabilities?
In frontline organizations, a competency is a specific piece of work someone has proven they can do to a set standard, confirmed on the job by a qualified validator. A skill, as most HR systems use the word, is a broader and more consistent unit of work the organization hires, develops, and plans around. A capability is an integrated piece of work the organization needs people to be able to do, such as telemetry monitoring or multi-axis CNC setup, and it draws on several competencies. On the frontline, ‘skill’ often means a specific task checked on the job, so it helps to agree on which meaning a conversation is using.
What is the difference between skills and competencies?
A competency is a specific, observable piece of work someone has proven on the job, such as programming an infusion pump to protocol or completing lockout/tagout on a packaging line. A skill, as HR systems like Workday use the term, is a broader unit such as patient assessment or preventive maintenance that supports hiring, development, and workforce planning. In frontline organizations, competencies are the evidence and skills are the enterprise language, and the goal is to connect the two.
Are skills and capabilities the same?
In most HR systems, they play the same role. A capability is an integrated piece of work the organization needs people to be able to do, described consistently across every site, and Workday and most other HR systems record that same unit as a skill. Using a separate word keeps it distinct from the frontline’s everyday use of “skill” for specific, site-level tasks.
What is the difference between a competency and a capability?
A competency is one specific piece of work someone has proven, like 12-lead ECG acquisition or vibration fault diagnosis. A capability is a broader piece of work that draws on several competencies, like cardiac rhythm monitoring or rotating equipment condition monitoring, and no single sign-off can prove it. The competencies people have proven are the evidence behind each capability. Look at everyone who holds it across a unit, plant, or company, and you see how deep the bench is for that work.
When should a frontline competency be pass/fail instead of on a proficiency scale?
Pass/fail often fits work where the main question is whether someone can do the task independently to standard, which is true of many safety procedures like lockout/tagout, emergency shutdowns, and sterile field preparation. A proficiency scale adds value when depth changes how people are staffed, developed, or promoted. Many organizations use both, keeping pass/fail checks for some competencies while still getting a view of depth at the capability level.
What should you look for in software that tracks frontline competencies, skills, and capabilities?
Look for a platform that:
- Captures competencies in the flow of work, in the field or on the floor, and has them confirmed by a qualified validator
- Works for the frontline, deskless worker
- Supports both pass/fail and multi-level proficiency scales
- Tracks certifications and expirations alongside demonstrated competencies
- Lets each site keep its own names while connecting them to consistent enterprise capabilities
- Delivers that data to your HR systems as skills, so HR and operations work from the same evidence
