Picture this: an HR leader at a 1,000-person company decides it’s time to build a leadership competency model. She pulls up vendor decks, downloads a few white papers, and finds a 40-item framework that sounds impressive until she tries to apply it. Nobody on her leadership team can remember more than four of the competencies. The framework sits in a shared drive. Nothing changes.
This happens a lot. The problem isn’t that organizations don’t care about leadership quality. It’s that most competency models are built for consultants to sell, not for managers to use.
What actually works is simpler. A focused, three-layer model that leaders can recall without a cheat sheet, tied to real behaviors at different career stages. That’s what this guide walks through.
What a Leadership Competency Model Is
A leadership competency model is a structured way of naming the behaviors your organization expects from leaders at different levels. It answers a specific question: what does good leadership look like here, at this stage of someone’s career?
That last part matters. A competency model is different from a job description. A job description lists duties. A competency model describes behaviors. “Runs weekly team meetings” is a duty. “Creates space for dissenting opinions during group decision-making” is a behavior. One is a checkbox. The other tells you something about how a person actually leads.
When done well, a competency model gives you shared language for conversations that are usually uncomfortable: promotions, performance reviews, coaching plans, succession planning. Instead of a manager saying “she’s just not leadership material,” they can point to specific behaviors and ask what development would look like.
Most organizations use competency models for hiring, development, and promotion decisions. The problem is they often build them wrong, and then wonder why the model doesn’t stick.
The Three-Layer Framework That Actually Works
Three categories is the sweet spot for a leadership competency model. Not seven. Definitely not 40. Three.
Here’s why: when you have 40 items, leaders can’t internalize them. They skim the list, nod, and forget it. When you have seven categories, the distinctions blur and everything starts to feel like a variation of the same theme. Three categories are distinct enough to mean something and few enough to remember.
The three layers are Strategic, Operational, and People. They cover the full scope of what leaders do without overlapping in ways that create confusion.
Strategic competencies are about direction. They answer the question: can this person see where the organization needs to go and make sound choices in service of that?
The core strategic competencies are decision-making, systems thinking, and priority-setting. Decision-making includes how leaders handle ambiguity, what process they use when data is incomplete, and how they account for second-order effects. Systems thinking is the ability to see how parts of the organization interact, not just optimize one team or function in isolation. Priority-setting means knowing what not to do, which turns out to be harder than knowing what to do.
Operational competencies are about execution. Once direction is set, can this person translate it into work that actually gets done?
The core operational competencies are delegation, goal-setting, and accountability. Delegation is often misunderstood. It’s not just assigning tasks. It’s matching the right work to the right person and giving them the context to succeed without micromanagement. Goal-setting means writing goals that are specific enough to be useful and flexible enough to survive contact with reality. Accountability is the willingness to have direct conversations when outcomes fall short, before small issues become large ones.
People competencies are about relationships. A leader can have excellent strategy and strong operational discipline, and still fail if their team doesn’t trust them.
The core people competencies are active listening, giving and receiving feedback, and conflict resolution. Active listening is harder than it sounds and shows up in how leaders run one-on-ones, how they respond to pushback, and whether their team members feel heard. Feedback covers both directions: delivering it in ways that people can actually use, and being open to receiving it. Conflict resolution isn’t about keeping everyone happy. It’s about addressing tension early, when it’s still manageable.
Sample Competency Framework
This table shows how each competency looks at three career stages. Use it as a starting point, not a finished product.
| Category | Competency | Early-Career Behavior | Mid-Career Behavior | Senior-Level Behavior |
|---|---|---|---|---|
| Strategic | Decision-making | Makes decisions within defined scope using available data | Makes decisions under ambiguity, seeks input from peers | Makes high-stakes decisions with incomplete information; owns outcomes |
| Strategic | Systems thinking | Understands how their team’s work connects to adjacent teams | Identifies upstream and downstream dependencies across functions | Redesigns how parts of the organization interact to improve overall performance |
| Strategic | Priority-setting | Manages personal workload and flags competing demands | Sets team priorities aligned to quarterly goals; protects team focus | Allocates organizational resources across initiatives; says no at the right level |
| Operational | Delegation | Completes assigned work; starting to hand off simple tasks | Delegates work with clear expectations; checks in without micromanaging | Builds team capacity by delegating stretch assignments; develops successors |
| Operational | Goal-setting | Writes personal goals with support from manager | Sets team OKRs tied to departmental outcomes | Sets multi-team or cross-functional goals; adjusts goals as context shifts |
| Operational | Accountability | Raises issues when something goes off track | Holds team members accountable in direct, timely conversations | Creates team culture where accountability is expected and supported |
| People | Active listening | Listens without interrupting; asks clarifying questions | Synthesizes input from multiple stakeholders before acting | Creates forums for dissenting views; adjusts strategy based on what they hear |
| People | Feedback | Delivers specific positive feedback; starting to give developmental feedback | Delivers difficult feedback directly and constructively; models receiving feedback | Normalizes continuous feedback in team culture; coaches others to give better feedback |
| People | Conflict resolution | Addresses personal conflicts with support from manager | Mediates conflict within their team before it escalates | Resolves cross-functional tension; addresses structural causes of recurring conflict |
A few notes on using this table. First, don’t expect everyone to hit the exact stage marker for their title. Someone might be mid-career in delegation and early-career in systems thinking. That’s normal and useful to know. Second, the behavioral descriptions here are starting points. Your high performers will tell you what these actually look like in your organization.
How to Build Your Own Competency Model (5 Steps)
The fastest way to build a competency model that people actually use is to ground it in your own organization’s reality. A five-step process works well for teams under 500 people.
Step 1: Interview five high performers about how they actually lead.
Don’t ask them what they think good leadership is. Ask them to walk you through a recent situation where they had to make a hard call, deal with a team conflict, or reprioritize on the fly. What did they do? What did they consider? What did they do that a less experienced leader might have skipped? Their answers will give you behavioral language that’s specific to your context.
Step 2: Interview three leaders who struggled.
This step makes people uncomfortable, but it’s essential. A competency model built only on success stories misses the other half of the signal. What patterns showed up before someone plateaued or failed in a leadership role? These interviews often reveal the behaviors that separate adequate from excellent. Keep the conversations confidential and focus on behaviors, not personality.
Step 3: Extract the eight to twelve behaviors that keep showing up.
Look across your interviews for themes. You’ll start to see the same behaviors mentioned repeatedly in different words. Cluster them, then name them in plain language. If you can’t describe the behavior without jargon, it won’t be useful in a performance conversation.
Step 4: Write each behavior at three proficiency levels.
Use the table format above as a model. For each behavior, describe what it looks like when someone is learning it, practicing it with some consistency, and modeling it at a senior level. The three-level structure is what makes a competency model useful for development conversations, not just evaluation.
Step 5: Pilot with one team before rolling out.
Pick a willing manager and their team. Use the model in their next round of one-on-ones and at least one performance conversation. Ask the manager and team members what was useful and what felt off. Refine based on real feedback before you scale. This saves you from rolling out something that works in theory but breaks down in practice.
What Goes Wrong With Most Competency Models
Most competency models fail not because the behaviors they list are wrong, but because of how they’re designed and implemented. A few patterns show up repeatedly.
Too many items. Forty-two competencies is not a model. It’s a list. Nobody internalizes a list of 42 things. Leaders skim it once during onboarding and never open it again. If your model has more than 12 competencies, start cutting. Ask yourself what you’d drop if you could only keep half.
Abstract language. “Strategic thinking” means nothing on its own. Neither does “drives results” or “demonstrates integrity.” These phrases feel meaningful until you try to use them in a real conversation. What does strategic thinking look like in a bad quarter? What does it look like in a first-time manager? Abstract language gives evaluators nowhere to stand.
One-size-fits-all across levels. A behavior that’s impressive in a team lead is table stakes for a VP. When a competency model uses the same descriptions across every level, it can’t support promotion decisions or development conversations. It also tells senior leaders nothing they don’t already know about themselves.
Disconnected from promotion decisions. The surest way to kill a competency model is to build a parallel informal system for promotions. When leaders watch a peer get promoted based on relationships and tenure while the competency model sits unused, they learn exactly how much the model matters. If you’re not willing to anchor promotion criteria to the model, you probably don’t need a model.
Using the Model in Practice
A competency model is only as useful as the conversations it enables. Putting it to work across the talent lifecycle looks like this.
For hiring, translate each competency into a structured interview question. For active listening, you might ask: “Tell me about a time you changed your mind based on feedback from your team. What did you hear, and what did you do differently?” Structured questions based on competencies reduce the influence of first impressions and give you something to compare across candidates.
For development, use competencies as a starting point for one-on-one conversations. If a manager wants to grow their delegation skills, start with a delegation assessment to get a baseline before the conversation. It gives both the manager and their leader shared language for what development actually looks like.
For promotion decisions, use the three-level behavioral descriptions to make the case for or against readiness. “She’s making senior-level decisions on priority-setting but still at a mid-career level on conflict resolution” is a useful, specific conversation. It’s the kind of thing that helps a candidate understand what they need to work on, rather than feeling like the decision was arbitrary.
For coaching, the model works as an assessment starting point. Before a coaching engagement, a leader can take a look at where they stand across each competency cluster. An emotional intelligence assessment covers the people layer in depth. A coaching skills assessment helps leaders understand where they sit on the continuum from directing to coaching. These baselines make coaching conversations faster and more targeted.
The goal is to make the model part of normal conversations, not a once-a-year audit. When a manager uses competency language in their weekly one-on-one, the model starts to live in the team, not just in HR’s shared drive.
If you want to see where your leaders stand on the competencies that matter most, Merlin can help them get a baseline without making it feel like a formal review. Try it at /try-merlin/.
Frequently Asked Questions
How many competencies should a leadership competency model have?
Somewhere between eight and twelve is the practical range for most organizations. Fewer than eight and you’re likely missing something important. More than twelve and retention drops sharply. If your current model has 30 or more items, treat that as a signal to consolidate, not add more.
What’s the difference between a competency model and a skills framework?
A skills framework typically lists capabilities at a functional level: data analysis, project management, public speaking. A competency model describes behaviors that reflect how someone leads, regardless of function. Competency models are more relevant for leadership development because leadership is fundamentally behavioral. That said, they can complement each other when both are designed with enough specificity to be useful.
How often should we update a leadership competency model?
A thorough review every two to three years is usually enough, with lighter check-ins annually. The trigger for a real update is a significant shift in what the organization needs from its leaders, like rapid growth, a change in strategy, or a major shift in how teams are structured. Updating too frequently creates confusion. Updating too rarely makes the model feel dated.
Can the same model work for managers and senior leaders?
The same three-layer structure can work across levels, but the behavioral descriptions need to reflect different expectations at each stage. A model that describes the same behaviors for a team lead and a department head isn’t doing the work you need it to do. Build in the three-level proficiency descriptions and you get one model that scales.
How do we get leaders to actually use the model?
Tie it to real decisions. Use it in promotion calibrations. Reference it in performance reviews. Have managers bring it into one-on-one conversations. The model becomes part of the culture when leaders see it used in decisions that matter to them, not just announced in an all-hands and forgotten.
What’s the best way to assess current leadership competencies?
A combination of self-assessment and peer/team input gives you the most accurate picture. Self-assessments alone tend to skew optimistic. Tools like Risely’s leadership assessment combine both perspectives and benchmark against broader data, which helps leaders see where they actually stand relative to peers, not just relative to their own expectations.