Competency Framework

What goes into a competency framework

A typical framework has three layers:

• Core competencies that apply to everyone, such as customer focus, accountability or working with others.
• Functional or technical competencies tied to a job family: workforce planning for operations analysts, claims adjudication for adjusters, sourcing for recruiters.
• Leadership competencies for people who manage others: coaching, decision-making, building teams.

Each competency gets a short definition and behavioral indicators at several proficiency levels, usually four or five (for example, Basic, Developing, Proficient, Advanced, Expert). Indicators should describe things you can observe. "Communicates well" is not an indicator. "Explains a policy change to the team in a five-minute huddle and checks understanding with questions" is.

Competency mapping is the step that connects the framework to roles: deciding which competencies each job needs and at what level. That mapping usually sits inside a wider job architecture.

Worked example: contact-center team lead

A customer service operation defines five competencies for team leads, with a target level of Proficient (3 of 5) for new leads and Advanced (4) after a year:

1. Coaching for performance. Proficient: holds weekly one-on-ones using call recordings, sets one specific goal per agent and follows up. Advanced: adapts coaching style to each agent and develops agents who become peer coaches.
2. Real-time floor management. Proficient: watches queue and adherence data during the shift and moves breaks to protect service level. Advanced: anticipates spikes and coordinates with workforce management before they hit.
3. Policy and compliance. Proficient: applies attendance and quality policy consistently and documents correctly. Advanced: spots policy gaps and proposes changes.
4. Customer escalation handling.
5. Communication and team engagement.

Interview questions for team lead candidates are written against these five; the new-lead program trains them; the six-month review rates them. One standard, used three ways.

Competencies versus skills

The terms overlap and people use them loosely. In general, a skill is a specific, often teachable ability (Excel pivot tables, Spanish fluency, forklift operation). A competency is broader: a cluster of skills, knowledge and behaviors that together produce good performance in a role, like "data-driven decision-making." A skills matrix tracks who has which specific skills on a team; a competency framework defines what good looks like across roles.

Many organizations are moving toward skills-based approaches with large skills taxonomies, partly because skills are easier to verify and update. The two can coexist: competencies for behaviors and leadership, skills for technical capability.

How to build one

1. Start small. Pick one job family with a clear business problem, such as high early turnover among new supervisors.
2. Gather evidence. Interview top performers and their managers about critical incidents: what did they do in hard situations that average performers didn't? Review job descriptions, quality data and exit interview themes.
3. Draft 5 to 8 competencies for the role. More than about ten becomes unusable.
4. Write behavioral indicators at each level, using plain language and real examples from the work.
5. Test with managers. Ask several to rate the same employees independently. If ratings vary widely, the indicators are too vague.
6. Connect it to processes: interview guides, training plans, reviews and promotion criteria. A framework used only in a slide deck changes nothing.
7. Review annually. Roles change, especially as tools and automation take over routine tasks.

Uses and legal notes

Competency frameworks support competency-based interviews, structured performance reviews, development plans and succession planning. Using the same job-related criteria across candidates and employees also helps defend selection decisions. Under the federal Uniform Guidelines on Employee Selection Procedures, employers whose selection methods cause adverse impact need evidence those methods are job-related, so base competencies on actual job analysis and avoid vague traits like "culture fit" or "energy" that invite bias.

Common mistakes

• Generic lists copied from another company that don't reflect your roles.
• Too many competencies, so nobody can remember or rate them.
• Indicators no one can observe.
• Building it and filing it. If it doesn't appear in hiring, training and reviews within six months, it won't stick.