How to Design a Competency Framework: An 8-Step Practitioner Guide for Indian Organisations

Home Blog How to Design a Competency Framework: An 8-Step Practitioner Guide for Indian Organisations

April 8, 2026
Smita Dinesh
10:29 am

At a Glance:

Designing a competency framework means translating your organisation’s strategy into observable, assessable behaviours that define what good performance looks like at every role level. The process involves eight steps: defining purpose and scope, conducting a structured job analysis, identifying and defining competencies, writing behavioural indicators, designing proficiency levels, mapping competencies to roles, validating the framework through expert review and statistical methods, and embedding it into talent management systems. Done well, it anchors hiring decisions, career development plans, performance management, and succession planning in a single coherent structure.

Why Most Organisations Get This Wrong From the Start

In our experience working with mid-size Indian organisations across BFSI, manufacturing, IT services, and pharma, the most common failure point in competency framework design is not technical. It is strategic. Organisations build frameworks without asking the most important question first: what specific talent decisions will this framework actually inform?

We have sat across the table from HR heads who spent six to nine months developing a 40-competency model, only to find that assessors had no training in using it, managers considered it another compliance document, and the framework never made it into a single career conversation. The investment was real. The impact was close to zero.

A well-designed competency framework for organisations is not a dictionary of desirable traits. It is a decision-support tool. It tells hiring managers what to look for in candidates. It tells L&D teams where skill gaps exist. It tells business leaders who is ready for the next role in the succession pipeline. When that functional clarity is present from day one, every subsequent design decision becomes sharper.

This guide lays out the eight-step process we use when working with organisations on competency model development consulting. It is written for HR leaders and L&D heads who want to move beyond generic frameworks borrowed from global competency libraries and build something that reflects the actual performance reality of their organisation.

Why the Indian Organisational Context Demands a Different Approach

Most global frameworks, including the widely-used Lominger 67 competencies and Spencer and Spencer’s competency dictionary, were validated primarily on Western corporate populations. When applied without adaptation to Indian organisations, several structural mismatches appear.

First, hierarchy and authority dynamics in Indian workplaces mean that behavioural indicators around influencing upward, speaking truth to power, or taking initiative without managerial approval require different calibration. What looks like low initiative in a Western model may be contextually appropriate deference in an Indian manufacturing or BFSI setting.

Second, the diversity of language, educational background, and professional socialisation across regions means that generic indicator language often fails to translate into consistent assessor understanding. A behavioural indicator written for a Bengaluru IT services firm may produce very different assessor interpretations when applied to a branch operations team in a Tier 2 city.

Third, mid-size Indian organisations typically sit in a growth phase where role boundaries are fluid, job descriptions are aspirational, and the gap between what a role demands today and what it will demand in 18 months is significant. Competency frameworks must therefore be built with a performance horizon in mind, not just the current job description.

These are not peripheral concerns. They shape every design decision from Step 1 onwards.

The 8-Step Process to Design a Competency Framework

Step 1: Define the Purpose and Scope

Before any data is gathered, the design team must document the specific talent decisions the framework will support. Will it be used for hiring, for annual appraisals, for promotion decisions, for identifying high-potential talent, for succession planning, or some combination?

Each use case places different demands on the framework. A framework used for skill gap analysis and learning prioritisation needs broader coverage and developmental language. A framework used for assessment centres and promotion decisions needs precision, observable indicators, and assessor reliability. Trying to do everything with one undifferentiated framework is the fastest route to a document that sits in a folder and does nothing.

Scope decisions at this stage include: which functions or levels will be covered in this phase, whether the organisation needs a single universal framework or a modular architecture with a core plus functional clusters, and what the realistic implementation timeline looks like. In our consulting work, we rarely recommend launching an organisation-wide framework in one go. A phased approach, starting with the roles or functions under highest talent pressure, produces faster adoption and cleaner validation data.

Is Your Organisation Ready to Build a Competency Framework? Let Us Help You Define the Right Scope.

Step 2: Conduct a Thorough Job Analysis

A competency framework is only as valid as the data it is built on. Job analysis is the process of systematically gathering evidence about what high performers in a given role actually do, think, and decide, and what distinguishes them from average performers.

The most rigorous method for this is the Behavioural Event Interview, or BEI, developed by David McClelland and refined by Lyle and Signe Spencer. In a BEI, you ask high performers to walk you through three to five critical incidents from their work, describing what the situation was, what they personally thought and felt, what they decided to do, and what actually happened. The interview is not about hypotheticals. It is about real events, told in real behavioural detail.

In practice, we combine BEI with structured focus groups of line managers and business leaders, role observation where feasible, and a review of existing performance data and job documentation. For a mid-size organisation of 1,500 to 5,000 employees, a robust job analysis phase typically requires four to eight weeks and covers a representative sample of performers across functions and geographies.

The output is a raw behavioural data set: specific, observable actions and decisions that distinguish high performers. This data becomes the raw material for competency identification in Step 3.

Step 3: Identify and Define Core Competencies

From the behavioural data gathered in Step 2, the design team conducts a thematic analysis to identify patterns. Behaviours that cluster together under a common performance theme become the basis for a competency definition.

A competency, at its core, is a combination of knowledge, skill, and underlying motive or value that drives consistently superior performance in a particular role or context. It is not a personality trait and it is not a job skill in isolation. The phrase good communication skills is not a competency. Proactively sharing information with stakeholders before they need to ask, in a way that builds trust and enables timely decision-making, is the kind of behavioural precision that makes a competency definition actionable.

For most mid-size Indian organisations, a practical framework architecture includes eight to twelve core competencies applicable to all employees, a cluster of four to six leadership competencies for managers and above, and functional competencies at the department or role family level. Resist the temptation to include every virtue you can think of. Fifteen to twenty well-defined, rigorously validated competencies are more powerful than forty vague ones.

Competency Layer	Who It Applies To	Typical Count
Core Competencies	All employees	8 to 12
Leadership Competencies	Managers and above	4 to 6
Functional Competencies	Role family or department	4 to 8 per cluster

Step 4: Design Behavioural Indicators for Each Competency

Behavioural indicators are the specific, observable actions that demonstrate a competency in practice. They are the most critical design element in the entire framework, and the most frequently done poorly.

A well-written behavioural indicator uses active language, describes a specific action the person takes, and is observable by someone watching the person work. It does not describe attitudes, values, or personality. Compare these two examples for the competency of Customer Orientation. A weak indicator reads: Has a customer-first attitude. A strong indicator reads: Seeks to understand the customer’s underlying need before proposing a solution, and adjusts the approach when the initial proposal does not address the root problem.

For each competency, we recommend writing four to six indicators that together cover the full range of situations in which the competency is expressed. These indicators also serve as the foundation for structured interview questions, assessment centre exercises, and 360-degree feedback tools.

Step 5: Define Competency Proficiency Levels

Not all employees are expected to demonstrate a competency at the same depth. A junior analyst and a senior director may both need to show Commercial Acumen, but the expected proficiency level differs significantly. Proficiency levels make this gradient explicit and assessable.

A typical four-level structure used in competency framework proficiency level design includes a Foundation level for individual contributors, a Developing level for experienced contributors and team leads, a Proficient level for managers and senior professionals, and an Advanced or Expert level for senior leaders and executives.

Each level should have its own set of behavioural indicators. This means the framework grows in specificity as it grows in level, rather than simply expecting more of the same behaviour at higher levels. Advanced leadership competency, for example, is not just more frequent influencing; it is influencing at a systems level, shaping strategy and organisational culture across functions.

Proficiency Level	Typical Role Band	Indicator Depth
Foundation	Graduate hires and junior professionals	Core task-level observable behaviours
Developing	Experienced contributors and team leads	Context-adaptive behaviours with some complexity
Proficient	Managers and senior professionals	Cross-functional impact, coaching others
Advanced / Expert	Senior leaders and executives	Systemic influence, strategy-level application

Step 6: Map Competencies to Roles and Levels

Once the competencies and proficiency levels are defined, the framework must be mapped to the organisation’s role architecture. This means specifying, for each role family and level, which competencies are required, at what proficiency level, and whether they are threshold (minimum required to perform the job) or differentiating (what distinguishes high performers from average performers).

This mapping exercise is also the stage at which the framework connects directly to skill mapping, career development plan design, and performance management framework architecture. When a competency is mapped to a role and proficiency level, it immediately generates questions such as: who currently meets this standard, who has gaps, what learning interventions would close those gaps, and who is ready to step up to the next level?

In our experience working with Indian organisations in growth phases, this mapping step is where the framework starts producing real business value. It creates the shared language that HR and business leaders need to have honest, specific conversations about talent readiness.

Building a Competency Framework for Your Organisation? Get a No-Obligation Consultation with Our Practitioners.

Step 7: Validate the Framework

A competency framework that has not been validated is a hypothesis, not a tool. Validation is the process of testing whether the framework actually predicts or reflects high performance, and whether it is interpreted consistently by different users.

Competency framework validation methods include content validity review, which involves structured feedback from a panel of subject matter experts and senior leaders who assess whether each competency and indicator accurately reflects performance in the role; criterion validity testing, where the framework is used to assess a sample of employees and the results are correlated with existing performance ratings or outcomes; and inter-rater reliability assessment, which measures whether different assessors using the same framework reach consistent conclusions when observing the same behaviour.

In a realistic organisational context, full statistical validation may not be feasible in the first design cycle. What is always feasible is a structured expert review process with a panel of at least eight to twelve informed stakeholders, followed by a pilot application with a small group and a structured feedback loop before organisation-wide rollout.

Honest advice here: plan for at least one significant revision after the pilot. The frameworks that hold up over time are the ones that were tested against real assessor experience and revised accordingly, not the ones that were declared final after the design team approved them.

Step 8: Integrate, Launch, and Sustain

A competency framework earns its value at the integration stage. This means embedding it into every talent process that touches the competencies it defines: job descriptions and hiring criteria, structured interview question banks aligned to competency-based interviewing, the performance management framework, individual development plans and career development plan structures, employee competency assessment processes such as 360-degree feedback and assessment centres, and succession planning criteria.

Launch planning matters as much as technical design. Assessors need training. Managers need a clear explanation of how the framework connects to their day-to-day people decisions. Employees need to understand it as a development tool, not a surveillance instrument. Without this stakeholder preparation, even the most rigorously designed framework will be resisted or ignored.

Sustainability requires a review mechanism. We recommend a formal review every 18 to 24 months, with a lighter-touch indicator review annually. Roles change, strategies shift, and the behaviours that predicted success in 2022 may not be the ones that predict success in 2026. A framework that was once well-calibrated and never updated becomes a liability rather than an asset.

How Competency Frameworks Drive Talent Management Strategy

The clearest signal that a competency framework is working is when it starts to inform decisions rather than document past ones. In our consulting work across Indian organisations, we have seen frameworks shift three major talent conversations.

First, they sharpen succession planning. When leaders can assess candidates against explicit leadership competency criteria and proficiency levels, succession decisions become less dependent on tenure, familiarity, and informal reputation, and more grounded in demonstrated readiness. This is particularly important in Indian organisations where succession planning has historically been dominated by functional loyalty and years of service rather than leadership capability.

Second, they make skill gap analysis and learning investment decisions defensible. When an organisation can show that a specific development programme addresses a validated competency gap at a particular level, L&D teams gain business credibility that generic training calendars never achieve.

Third, they enable consistent employee competency assessment across geographies, functions, and assessors. For organisations scaling into new markets or integrating acquisitions, this consistency is a significant operational advantage.

Common Mistakes to Avoid

Several patterns consistently undermine competency framework projects, even in organisations with strong HR teams and genuine commitment to the work.

The first is scope creep during design. Stakeholders often want to include competencies that reflect organisational values rather than observable performance. Values belong in a culture framework. A competency framework must stay focused on behaviours that can be assessed in a structured way.

The second is skipping the job analysis phase in favour of adapting a generic competency library. Libraries such as Lominger or the Spencer and Spencer dictionary are useful as references and cross-checks. They are not substitutes for evidence gathered from your own organisation’s high performers. A framework built on borrowed indicators will produce generic results.

The third is launching without assessor calibration. Behavioural indicators are interpreted differently by different assessors unless they are trained together, tested on sample evidence, and brought to a shared understanding of what each proficiency level looks like in practice. Without this, 360-degree feedback data and assessment centre scores are not comparable across the organisation.

The fourth, and perhaps the most damaging, is treating the framework as a completion rather than a foundation. The design phase is the beginning, not the end. The organisations that get lasting value from their competency frameworks are the ones that keep asking whether it is still accurately reflecting what great performance looks like.

Smita Dinesh

Smita brings fresh and innovative thinking to every task and assignment. With an extensive industry experience of over 25 years, her passion for human behavior assessments and the ability to connect the dots, read the room, engage, facilitate, coach, and solutionize has left an indelible mark on individuals, teams, and organizations.

Frequently Asked Questions

How long does it take to build a competency framework for an Indian organisation?

For a mid-size organisation of 1,000 to 5,000 employees, a well-designed competency framework project typically takes four to six months from initiation to pilot launch. This includes four to eight weeks for job analysis and data gathering, four to six weeks for design and indicator writing, two to four weeks for validation and expert review, and four to six weeks for pilot application and revision. Organisations that compress this timeline significantly tend to produce frameworks that require extensive rework within 12 to 18 months.

What is the difference between a competency and a skill in the context of competency frameworks?

A skill is a learned technical capability, such as financial modelling, Python programming, or machine operation. A competency is a broader construct that combines knowledge, skill, and underlying personal characteristics such as values, motives, and self-concept that drive consistent superior performance. A skill can typically be trained. A competency, particularly at the deeper motive and value level, requires longer-term development and sometimes a different kind of person. Competency frameworks are designed to capture both surface-level skills and the deeper behavioural patterns that predict high performance.

How many competencies should be included in a framework for a mid-size Indian organisation?

A practical architecture for most mid-size Indian organisations includes eight to twelve core competencies that apply to all employees, four to six leadership competencies for managers and senior professionals, and four to eight functional competencies per role family or department. Total competency count across all layers should typically stay below 25 to 30. Frameworks with 40 or more competencies are rarely used consistently. Depth and precision in a smaller set produces better results than breadth across a large one.

Should Indian organisations adapt global competency models or build from scratch?

The most effective approach combines both. Global frameworks such as Lominger or the Spencer and Spencer dictionary provide a validated reference point and help ensure that important competency domains are not overlooked. However, they must be supplemented with India-specific job analysis data, particularly Behavioural Event Interview evidence from your own high performers. Context-specific behavioural indicators are non-negotiable if the framework is going to be used for assessments and talent decisions. A purely borrowed framework will produce assessor disagreements and low adoption. A purely bespoke framework built without reference to established research risks missing important competency domains.

How does a competency framework connect to performance management and career development plans?

A competency framework provides the shared language that connects performance management, career development, and succession planning into a coherent talent management system. In performance management, competency proficiency ratings complement outcome-based metrics by showing how results were achieved, not just whether they were achieved. In career development plan design, competencies define the specific behavioural gaps an employee needs to close to progress to the next level. In succession planning, they provide the criteria against which potential successors are assessed and developed. Without this shared language, each talent process operates in isolation.

Table of Contents