Here is a belief that survives in many HR departments: a competency framework is a poster. Twelve words, such as Integrity, Teamwork, Customer Focus, Innovation, Ownership, each with a one-line definition, printed on the wall near the cafeteria and copied into the appraisal form. If you have worked in a mid-sized Indian company, you have probably seen one. And if you have, you also know it changes nothing about how anyone is hired, rated or promoted. That is the belief worth taking apart, because the poster is not the framework. It is the cover page.
A competency is not a trait and not a skill
Start with the word itself. A competency is a cluster of knowledge, skill and behaviour that produces good performance in a job. It is something you can watch a person do. “Is a team player” is a trait claim; you cannot observe it directly. “Shares draft work with peers before the review meeting and incorporates their comments” is a behaviour; you can see it, or notice its absence.
A skill, on the other hand, is narrower. Writing SQL is a skill. Structuring an ambiguous data problem so that someone else can act on it is closer to a competency, because it combines skills, judgement and habit. Frameworks usually contain both, and trouble starts when they are not separated: technical skills tested through assessments sit in one list, behavioural competencies assessed through observation sit in another.
Myth: the competency name carries the meaning
It does not. “Ownership” means one thing to a founder and another to a payroll executive. The meaning lives in the behavioural indicators, short statements of what the competency looks like in practice, written level by level. Take an illustrative insurance firm in Jaipur that defines “Customer Focus” for its claims team.
- Level 1 (claims executive): Responds to customer queries within the stated service time and records the outcome in the system.
- Level 2 (senior executive): Anticipates what documents a customer will be missing and asks for them in the first call, so the file does not bounce.
- Level 3 (team lead): Reads rejection patterns across the team and changes the process or script that is causing them.
- Level 4 (head of claims): Takes customer complaint themes to product and underwriting and gets rules changed.
Look at what has changed from level to level. It is not “more” customer focus. It is a wider scope: the individual, then the case, then the team, then the system. That progression of scope and complexity is what makes a framework usable for promotion decisions, and it is what a one-line poster definition cannot do.
Myth: one framework for everybody
A company-wide set of core competencies (values-based, applying to all) is fine, usually four to six. But the useful parts are role-family frameworks: the competencies that separate strong from average people in sales, in engineering, in finance operations. These are found by actually studying the job, through interviews with strong performers and their managers, and review of what differentiates them. The classic method is the behavioural event interview associated with David McClelland’s work and later refined by consulting firms; you do not need the full academic version, but you do need evidence from real performers rather than a brainstorm in a conference room.
The brainstorm approach tends to produce what leaders wish were true of the organisation. Studying real people produces what is true of the people who actually perform. Those two lists differ more often than anyone expects, and the second is the one worth hiring against.
Myth: more competencies means more rigour
Raters cannot hold twenty items in mind. Research on rating and common experience agree that when a form has many competencies, managers rate them in a clump (everything a 3, or everything a 4) because they form one overall impression and then fill in the boxes. A smaller set, with sharp indicators, gets better discrimination. Eight to ten per role family is already generous.
Where the framework earns its keep
Four places stand out.
- Hiring. Structured interview questions are drawn from the indicators for the target level. Interviewers know what a strong answer would contain, instead of reacting to charm.
- Appraisal. The conversation moves from “you were good this year” to “here are two examples where you showed Level 2 behaviour and one where it was Level 1”.
- Promotion. The question becomes whether the person is already showing the next level’s behaviour consistently, which is much fairer than “he has been here five years”.
- Development. Gaps are specific, so training can be specific. Someone who needs to move from Level 2 to 3 in customer focus needs exposure to pattern analysis, not a generic soft-skills workshop.
How frameworks die
They die in three ways. They are written by a consultant, handed over, and never revisited, so within three years they describe jobs that no longer exist. They are used only in the appraisal form and never in hiring or promotion, so managers treat them as paperwork. Or the indicators are so abstract (“demonstrates excellence”) that two raters cannot agree on a single example. A test worth running: give two managers the same one-page account of an employee’s work and ask them independently to place it at a level. If they disagree on most competencies, the wording needs work, not the managers.
Where a company is small, say under a hundred people, a full framework may be more machinery than it needs. A half-page of what good looks like for each role, written with the best people in that role, does most of the job. The point was never the framework. It was making “good” describable enough that people can aim at it.
Figures and names in the examples are illustrative.
Leave a Reply