A competency is a defined, assessable cluster of skills, knowledge, and behaviors that a person needs to perform a specific part of a job to a required standard. A skill is something you can do. A competency is the job-relevant package of skills, knowledge, and judgment that produces a result, described precisely enough that two managers would rate the same person the same way.
I have spent eighteen years helping organizations write competencies, and the same thing happens every time. The first draft is a list of adjectives. "Strong communicator." "Detail-oriented." "Team player." Nobody can assess those, so nobody does, and the framework quietly dies in a shared drive. The definitions that survive are the ones written like engineering specs: an action, an object, an observable standard.
This guide covers what competencies are, how they differ from skills and proficiency, the four types most frameworks use, a dozen real examples across roles, and the method for writing definitions that hold up in an assessment.
What Is a Competency?
A competency describes what a person must be able to do, know, and demonstrate to carry out a critical work function. It sits one level above a skill. "Read a P&ID drawing" is a skill. "Diagnose process faults using P&ID drawings, instrument readings, and shift logs, and escalate per the site's response protocol" is a competency. The competency bundles several skills with the knowledge and judgment to apply them, and it points at an outcome the business cares about.
Three properties make something a competency rather than a trait or a task:
- It is tied to a work outcome. Competencies exist because the job requires a result. If you cannot name the result, you are describing a personality trait.
- It is observable or measurable. Someone can watch the work, review the output, or test the knowledge and reach a defensible rating.
- It has levels. A competency is not binary. People perform it at foundational, working, advanced, and expert levels, and those levels are described.
Competencies are the foundation of skill specifications. They define what a role demands, they anchor assessments, and they give learning initiatives a target. When they are vague, everything built on top of them wobbles: the assessment becomes an opinion survey, the training plan becomes a course catalog, and the succession plan becomes a list of people the executive team likes.
Competencies vs. Skills vs. Proficiency
The three terms get used interchangeably, and the confusion costs real money in badly scoped frameworks.
| Term | What it is | Example | How it is measured |
|---|---|---|---|
| Skill | A specific, learnable ability | Writing SQL queries | Often binary or a simple scale |
| Competency | A job-relevant cluster of skills, knowledge, and behavior tied to an outcome | Building reliable reporting pipelines that finance signs off on | Leveled rubric with behavioral anchors |
| Proficiency | How well a person performs a skill or competency, right now | Level 3 of 5 on reporting pipelines | Assessment against level descriptors |
Skills are the base unit. Competencies organize skills into something a role actually needs. Proficiency is the measurement of either. The full comparison, with worked examples, is in Skills vs. Competencies vs. Proficiency.
Types of Competencies
Most frameworks sort competencies into four types. The sorting matters because each type is written, assessed, and owned differently.
Core competencies
Core competencies apply to everyone in the organization regardless of role. They translate company values into observable behavior. At a logistics company, "Safety ownership" is a typical core competency: identifies hazards, stops unsafe work, reports near misses, and follows lockout procedures without being prompted. Core competencies are usually owned by HR and assessed annually.
Functional or technical competencies
These are the competencies specific to a job family: the engineering competencies, the nursing competencies, the sales competencies. They carry most of the assessment weight because they determine whether someone can do the job. A functional competency for a maintenance technician reads "Perform preventive maintenance on rotating equipment to the OEM schedule with documented completion." Owned by the function leader, assessed by managers and often by evidence.
Leadership competencies
Leadership competencies describe what the organization expects from people who direct others: setting priorities, developing people, making decisions with incomplete information, holding standards. They are leveled by scope. A first-line supervisor and a vice president both need "Develops people," but the behavioral anchors are different.
Behavioral competencies
Behavioral competencies cover how work gets done: collaboration, adaptability, customer focus, communication. They are the hardest to write well because they are the easiest to write badly. "Communicates effectively" is not a competency. "Explains technical findings to non-technical stakeholders so they can make a decision without a follow-up meeting" is.
Competency Examples
Twelve competencies from real frameworks, lightly genericized. Notice the pattern: verb, object, standard, and a result the business would recognize.
Data center technician: Critical environment response. Identifies alarms across power, cooling, and fire systems, executes the emergency operating procedure for the affected system, and completes the incident log within the shift.
Data center technician: Certification currency. Maintains required vendor and safety certifications, tracks expiry dates, and completes recertification before lapse so the site never operates below its qualified headcount.
Nurse: Medication administration. Verifies patient identity, dose, route, and timing against the order, documents administration in the EHR, and escalates discrepancies before administering.
Nurse: Patient handoff. Delivers structured shift handoffs covering condition, pending results, and risks, so the receiving nurse can act without re-reading the chart.
Project manager: Scope control. Documents baseline scope, runs a change process that quantifies cost and schedule impact, and secures sponsor sign-off before absorbing any change.
Project manager: Risk management. Maintains a risk register with owners and triggers, reviews it at each stage gate, and activates mitigations before risks convert to issues.
Sales engineer: Technical discovery. Maps a prospect's current architecture, constraints, and success criteria in the first two calls and produces a solution outline the account executive can price.
Sales engineer: Proof-of-concept delivery. Scopes, builds, and demonstrates a proof of concept against agreed success criteria within the committed timeline.
Line supervisor: Shift planning. Assigns qualified operators to every station using the current skills matrix, covers absences without dropping below required certification levels, and records the plan before shift start.
Line supervisor: Quality escalation. Recognizes out-of-spec conditions, stops the line per the control plan, and initiates containment and root-cause steps within the documented window.
Financial analyst: Variance analysis. Explains budget-to-actual variances with quantified drivers and a recommended action, delivered by the close calendar.
Software engineer: Production readiness. Ships changes with tests, monitoring, and rollback paths, and can explain the failure modes to an on-call peer.
Each of these can be assessed by watching the work, reviewing artifacts, or testing knowledge. None of them contains the word "good."
How to Write a Competency Definition
The method has not changed in the years I have been teaching it. It works because it forces precision.
- Start with a present-tense action verb. Diagnoses, builds, verifies, escalates, documents. The verb tells you what to observe.
- Give the verb an object. "Verifies patient identity." "Documents baseline scope." Verb plus object is the skeleton of the definition.
- Add the standard. Against what? By when? To whose satisfaction? "Before administering." "Within the shift." "So finance signs off." The standard is what separates a competency from a wish.
- Base it on performance, not attendance. Completing a course is not a competency. Doing the work the course taught, to the standard, is.
- Strip every evaluative adjective. Good, strong, effective, appropriate, successful. If the word cannot be measured, it does not belong. Replace it with the observable behavior you actually mean.
A worked example. First draft: "Strong spreadsheet skills." Second draft: "Uses standard formulas and functions, formats and modifies content, and builds spreadsheets, charts, and graphs." Final draft: "Builds spreadsheet models with documented formulas and validation checks that a reviewer can audit without the author present." The final version names the object, the standard, and the result. It can be assessed by opening the file.
The deeper craft, including how to handle knowledge versus behavior and how to avoid definitions that only the author understands, is in The 4 Pillars of Writing Competency Definitions.
Competencies vs. learning goals
The definitions above are not learning objectives, and confusing the two is a common early mistake. A learning goal describes what a learner should be able to do at the end of a course. A competency describes what the job requires, regardless of how the person acquired it. Learning goals are the path. Competencies are the destination that validates the path was worth walking. A spreadsheet course has the goal "construct formulas using relative and absolute references." The competency it serves is the auditable model above.
Competency Frameworks and Models
A single competency is useful. A competency framework is where the value compounds. The framework organizes competencies by role and job family, assigns the required proficiency level for each, and connects them to hiring, assessment, development, and succession. It is the structure that lets an organization say, with evidence, "these 40 people are qualified for that work, these 12 are one level away, and here is the training that closes the gap."
Frameworks are built in one of a handful of ways: adapting a published model, deriving competencies from top performers, working backward from strategy, or a hybrid. Each has trade-offs in speed, ownership, and fit. The comparison is in 4 Types of Competency Models. The one rule that holds across all of them: write the framework in your organization's language. Imported taxonomies look complete in a demo and wither once real managers have to rate real people against words they never use.
How Competencies Are Assessed
A competency definition is only as valuable as the assessment behind it. Assessment turns the definition from a document into data: this person, this competency, this level, this date, this evidence.
Three things make competency assessment credible. First, a leveled proficiency scale with behavioral anchors for each level, so "3" means the same thing across managers and sites. How to build those scales is covered in Proficiency Levels: Scales, Examples, and How to Define Them. Second, more than one rater. Self-assessment paired with manager assessment surfaces the gaps in perception, and the delta is where the useful coaching conversation lives. Third, evidence. A rating with a reason attached, whether an observed task, a work sample, or a test, holds up in a promotion discussion and in an audit.
This is the point where competencies stop being an HR artifact and become operational infrastructure. In SkillsDB, competencies are a primitive: they live in the competency framework, they carry leveled proficiency scales, and every proficiency assessment writes a dated, evidenced score against them. The definition, the level, and the assessment are one record, which is what makes gap analysis, staffing, and succession answerable with data rather than memory.
Definitions Are the Foundation
Every downstream workforce decision inherits the quality of the competency definitions underneath it. Write them as observable behaviors with standards and outcomes, level them, and assess against them with evidence. Skip that discipline and the framework becomes a vocabulary list. Apply it and competencies become the most useful data an organization holds about its own capability.