Many competency frameworks are simply skill inventories. We list what people should know, add some behavioral descriptors, and possibly add proficiency levels. Then we wonder why performance remains inconsistent across individuals who supposedly possess the same competencies. The problem isn’t that we’re measuring the wrong things; it’s that we’re thinking about competency development in the wrong way.
What We Get Wrong About Competencies
Traditional competency mapping treats expertise like a collection of discrete components. “Strategic thinking” may be defined as planning, analysis, and decision-making. “Communication” becomes writing, presenting, and listening. We create these intricate taxonomies that appear impressive in frameworks but often fail when people attempt to apply them.
Real competency isn’t additive. You don’t get strategic thinking by combining planning skills with analytical thinking. You get it by repeatedly navigating complex situations where multiple valid options exist, stakeholders have competing interests, and incomplete information forces judgment calls.
Confusion About Competencies
Part of the problem is that “competency mapping” is used to describe different things by different people. Some people use it to mean curriculum mapping, which involves aligning courses with job requirements or KSAs. Others think it means creating competency frameworks with lists and proficiency levels. These aren’t the same thing as mapping how expertise actually develops and transfers to performance.
When we confuse the tool (frameworks) or the process (curriculum alignment) with the real work (understanding how people develop expertise in context), we end up with solutions that look comprehensive but don’t actually improve performance.
Context Changes Everything
Here’s what’s missing from most competency conversations: context isn’t background noise, it’s the whole point. Strategic thinking in federal environments means navigating stakeholder politics, compliance requirements, and mission constraints simultaneously. That’s not the same skill as strategic thinking in a startup, where you can pivot quickly and break things.
The competencies that matter aren’t just what people can do – they’re what people can do within the specific constraints, pressures, and expectations of their actual work environment.
What Competency Mapping Actually Reveals
When you map competencies the way work actually happens, patterns emerge that skills lists miss entirely. You begin to see how expertise develops through repeated exposure to authentic challenges, rather than through training modules that teach components in isolation.
You also discover that the most valuable competencies are often the ones we never thought to name. The ability to recognize when standard procedures won’t work. The judgment to know which stakeholder concerns are worth addressing and which are distractions. The skill of translating complex requirements into actionable guidance for people who don’t live in your technical world.
The Questions That Matter
Instead of asking “What should people know how to do?” try asking:
What are the situations where good performers consistently succeed and others struggle? What makes those situations challenging? What do successful people notice or prioritize that others miss?
When people fail at tasks they theoretically have the skills for, what’s actually happening? What contextual factors are they not accounting for?
What does expertise look like when things don’t go according to plan?
These questions reveal competencies that cannot be captured in skills inventories. They point toward the kind of learning experiences that actually prepare people for the complexity of real work.
Moving Beyond Lists
The competency mapping revolution isn’t about better taxonomies or more sophisticated measurement tools. It’s about recognizing that competency development happens through authentic practice in realistic contexts, not through decomposed skills training.
This doesn’t mean throwing out frameworks entirely. It means using them as starting points for deeper conversations about what expertise actually looks like in practice, rather than as endpoints that define what people need to know.
The question isn’t whether learners can demonstrate strategic thinking on an assessment. It’s whether they can navigate the messy, ambiguous, politically complex situations where strategic thinking actually matters.
And that’s a very different kind of mapping problem.
Resources for Implementation
If you’re dealing with competency confusion in your organization, I’ve created three templates that distinguish between competency frameworks, curriculum mapping, and competency mapping approaches. Each addresses different organizational needs:
- Competency Framework Template: For defining role standards and performance criteria
- Curriculum Mapping Template: For aligning learning experiences to job requirements
- Competency Mapping Template: For understanding how expertise develops in authentic work contexts
They’re designed to help teams understand which tool fits their actual needs and when to use each approach. The goal isn’t more sophisticated measurement – it’s clearer thinking about what we’re actually trying to develop.
