Table of Contents
How to Create a Competency Framework Your Managers Will Actually Use
- October 10, 2026
- 11:21 am
It’s appraisal week, and a production manager is staring at a form.
The first competency reads: “Strategic Orientation, Level 3: Demonstrates alignment of operational priorities with organisational vision.”
She reads it twice. She thinks about the supervisor she’s rating, who is excellent at keeping a difficult shift running on time. She wonders whether that counts as “operational priorities”. She isn’t sure what “organisational vision” would look like on a Tuesday night.
She gives him a 3. Everyone gets a 3.
Here’s a question worth sitting with: if the people who use a competency framework can’t tell what it means, who exactly was it written for?
Learning how to create a competency framework that managers actually use isn’t mainly about models or methods. It’s about writing for the person filling in the form at 6 p.m. on a Thursday.
Why Managers Ignore Most Competency Frameworks
Most competency frameworks aren’t ignored because managers are careless. They’re ignored because the framework doesn’t help with the decisions managers actually make.
Managers need to hire someone, give feedback, decide on a promotion, or have a hard conversation about performance. If the framework doesn’t make any of those easier, it becomes another thing to get through.
What managers ignore | What managers use |
|---|---|
Abstract, corporate language | Words they already use at work |
Twelve or more competencies | Five to eight that clearly matter |
Same framework for every role | Content that fits their team |
Lives in an HR document | Built into forms they already use |
Unchanged for years | Updated as roles change |
The CIPD’s guidance on competency frameworks makes a similar point. When frameworks are designed well, they clarify expectations and connect individual performance to the organisation’s goals. When they’re designed poorly, they become bureaucratic and disconnected from real work. The difference is almost always in the design.
How to Create a Competency Framework Step by Step
1. Start with the decisions it should support
Before writing a single competency, decide what the framework is for. Hiring? Promotions? Development? Performance reviews? All of these?
The answer shapes everything. A framework built mainly for hiring needs behaviours an interviewer can assess in an hour. One built for development needs enough detail to show people how to grow.
2. Decide on the structure: role or job family
A role competency framework describes what good looks like in one specific role, such as a plant maintenance supervisor. A job competency framework usually covers a family of related jobs, such as all supervisory roles in operations, with shared competencies and some variation by role.
Most organisations need both, arranged in layers.
Layer | What it covers | Example |
|---|---|---|
Core | Behaviours expected of everyone | Ownership, customer focus |
Leadership | Behaviours by management level | Developing people, decision making |
Role or functional | Behaviours specific to the job | Safety discipline, client negotiation |
This structure keeps the framework consistent across the organisation without forcing a sales manager and a quality engineer into the same description of “good”.
3. Gather evidence from real work
Don’t start with a competency library. Start with the people who do the job well and the managers who see the difference between good and great.
Ask for specific stories. “Tell me about a time a new supervisor really impressed you. What did they actually do?” The answers reveal the real behaviours that matter in your organisation, and they give you language managers will recognise.
4. Write in the language of the workplace
This is where most frameworks lose managers. Test every behavioural indicator with one question: would a manager say this out loud?
“Demonstrates alignment of operational priorities with organisational vision” fails. “Explains to the team why this week’s targets matter for the customer” passes. Same idea. One gets used.
5. Keep it short
Five to eight competencies per role is usually enough. Each competency needs only three to five behavioural indicators. If the framework needs a training session just to read it, it’s too long.
6. Use proficiency levels sparingly
Levels are useful, but five levels for every competency quickly becomes unworkable. Many organisations do well with three: developing, proficient and advanced. Every level must describe a visibly different behaviour, not just a stronger adjective.
7. Test it on real decisions
Before launch, ask a few managers to use the draft on real people. Can they rate their team members with confidence? Does it describe their best performer accurately? Would it have helped with last year’s difficult promotion decision?
Their answers will show you exactly which parts need rewriting.
Build a Usable Competency Framework
Put It Where Managers Already Work
Even a well-written framework fails if managers have to go looking for it. The most important design decision is where the framework appears.
Manager moment | How the framework helps |
|---|---|
Interviewing a candidate | Ready-made behavioural questions per competency |
Monthly one-to-one | A shared language for feedback |
Promotion discussion | Clear criteria for readiness |
Appraisal | Ratings based on observable behaviour |
Development planning | Specific gaps to work on |
Build the framework into interview guides, appraisal forms and development templates. Connect it to promotion processes such as assessment and development centres, and align it with role-level KPIs, so that what people achieve and how they achieve it are discussed together.
When managers meet the framework naturally in the course of their work, they start using it without being asked.
Keep the Framework Alive
Roles change. New technology, new structures and new strategies all change what good looks like. A framework that hasn’t been reviewed in three years is probably describing a job that no longer exists in quite the same form.
A light annual review, involving a few managers from each function, keeps it current. It also builds ownership, because managers who help update the framework are far more likely to use it.
This is easier when the organisation has people who know how to maintain it. Many HR and OD teams build this capability through the Certification in Competency Mapping and Application (CCMA), an HRCI-accredited programme covering framework design, mapping methods and practical application. Where the work is larger, linked to a restructure or covering the whole organisation, our organisation development consulting team works alongside internal HR to design and embed it.
Since 2009, we’ve worked with more than 300 organisations. The frameworks that last aren’t the most sophisticated ones. They’re the ones written in the language of the people who use them. If you enjoy thinking about questions like these, the Friday Fulcrum explores them every week.
A competency framework succeeds the day a manager uses it to say something specific and useful to someone on their team. Everything else is just formatting.
Talk to Our OD Consultants
Smita Dinesh
Frequently Asked Questions
Start with the decisions the framework should support, choose a structure such as core, leadership and role-specific layers, gather evidence from high performers and their managers, write behavioural indicators in everyday workplace language, keep it to five to eight competencies per role, test it on real decisions and build it into existing HR processes.
A role competency framework describes the specific behaviours, skills and knowledge needed for success in one particular role. It gives managers a clear, detailed picture of what good performance looks like in that job.
A job competency framework covers a family of related roles, such as all supervisory or sales roles, with shared competencies and some variation by specific role. It keeps standards consistent across similar jobs.
Most roles work best with five to eight competencies, each with three to five behavioural indicators. More than that usually makes the framework harder for managers to remember and use.
Common reasons include abstract language, too many competencies, content that doesn’t fit their roles, and frameworks kept in separate documents rather than built into the interview, appraisal and development tools managers use.
A light annual review is a good rhythm for most organisations, with a fuller revision when roles, structures or business strategy change significantly.
Recent Blogs
Sales Competency Assessment: Spotting Real Sellers Before the Offer Letter
Most internal trainers in Indian organisations were never taught to facilitate. They were taught to present. The
How to Assess Candidates in Interviews When Everyone Has Rehearsed the Same Answers
Most internal trainers in Indian organisations were never taught to facilitate. They were taught to present. The
Pre Employment Assessment Solutions: What to Check Before You Choose One
Most internal trainers in Indian organisations were never taught to facilitate. They were taught to present. The