Most organizations say they want skills-based learning. Far fewer have done the foundational work that makes skills-based learning possible: defining what competencies matter, mapping them to roles, and connecting them to the content and experiences that build those competencies. Without that scaffolding, learning programs drift toward whatever is popular or whatever a stakeholder requests loudest. A well-built competency framework changes the game. It gives you a structured, defensible way to decide what to offer, who to offer it to, and how to measure whether it worked.
Before diving into the how, it helps to be precise about vocabulary. A competency is a combination of knowledge, skills, and behaviors that enables someone to perform effectively in a specific context. It is broader than a single skill. "Data analysis" is a skill. "Evidence-based decision making" is a competency — it includes data analysis but also critical thinking, the ability to communicate findings, and the judgment to know when the data is sufficient. Competencies sit at the intersection of what someone knows, what they can do, and how they show up. That distinction matters because it shapes how you write competency definitions and how you assess them.
Defining competencies well is the first hard step. Vague competencies like "leadership" or "communication" are almost useless because they mean different things to different people. Strong competency definitions include a clear label, a concise description of what the competency looks like in practice, and a set of proficiency levels that describe the progression from novice to expert. Proficiency levels are critical. They turn a static label into a developmental continuum. For example, at a foundational level, someone might be able to apply a standard process. At an advanced level, they can adapt the process for novel situations and coach others. Three to five proficiency levels is usually enough to capture meaningful differences without creating bureaucratic overhead.
Where do the competencies come from? The best frameworks draw on multiple sources. Job descriptions and role expectations are an obvious starting point, but they tend to describe the current state rather than where the organization is heading. Strategic plans and workforce planning documents help you identify the competencies you will need in the next two to three years, not just the ones that matter today. Conversations with high performers and their managers reveal the often-unwritten behaviors that separate adequate performance from outstanding performance. And reviewing industry frameworks — many professional associations publish competency models for their fields — provides useful benchmarks. The goal is to synthesize these inputs into a framework that is specific enough to be actionable and stable enough to last more than one budget cycle.
Once you have a set of well-defined competencies, the next step is mapping them to roles. This does not mean creating a unique competency profile for every job title in the organization. Start by grouping roles into families — clusters of jobs that share similar competency requirements even if the titles differ. For each role family, identify the core competencies and the expected proficiency level. A junior project coordinator and a senior program manager might both need stakeholder management, but at very different levels. This mapping gives you a clear picture of what development looks like for someone moving between roles, and it makes career pathing conversations much more concrete.
The real payoff for L&D comes when you connect the competency framework to learning content and experiences. Every course, workshop, coaching engagement, or stretch assignment in your portfolio should be tagged to one or more competencies and the proficiency level it targets. This is where many organizations stall, because the tagging work is unglamorous and time-consuming. But without it, you cannot answer basic questions like: Do we have adequate learning options for someone trying to move from foundational to intermediate in data literacy? Are we over-investing in content for competencies that are already well-developed across the workforce? Tagging also enables personalized learning recommendations — if an employee and their manager agree on a target proficiency level, you can surface the specific resources that close that gap.
A competency framework is not a one-time project. It needs ongoing stewardship. Plan to review the framework annually, retiring competencies that no longer align with business needs and adding ones that reflect new strategic priorities. Assign ownership — someone or some team needs to be accountable for the integrity of the framework. And invest in helping managers use it. A framework that lives only in the L&D team's toolkit has limited impact. When managers use it in performance conversations, hiring decisions, and succession planning, it becomes an organizational operating system.
Finally, resist the urge to over-engineer. A framework with two hundred competencies and seven proficiency levels each will collapse under its own weight. Start with the fifteen to twenty-five competencies that matter most to your organization. Get them right, get them adopted, and expand from there. The value of a competency framework is not its completeness — it is its usefulness. If people actually use it to make better decisions about development, hiring, and deployment, you have succeeded. If it sits in a SharePoint folder gathering digital dust, the number of competencies it contains is irrelevant.