Organizations spend enormous amounts of time defining what good leadership should look like. Competency models translate that ambition into observable language: strategic thinking, collaboration, accountability, adaptability, customer orientation, enterprise mindset, developing others. Once established, those competencies can influence hiring, performance management, leadership development, succession, assessment, and promotion decisions. A well-designed model creates consistency across systems that might otherwise operate with different definitions of effective leadership. The problem begins when the existence of that definition is mistaken for organizational capability.
An organization can have an elegant competency model and still promote leaders who struggle at the next level. It can assess people against clearly articulated behaviors while failing to give them the experiences through which those behaviors become meaningful. It can tell leaders to demonstrate enterprise thinking while structures, incentives, decision rights, and performance expectations continue to reward functional optimization. It can define adaptability as essential while making it extraordinarily difficult for leaders to experiment, challenge established assumptions, or make decisions outside narrow boundaries. In each case, the competency itself may be perfectly reasonable. The organizational environment surrounding it is not.
That distinction matters because competency models describe expectations at the level of the individual, while leadership effectiveness emerges through an interaction between the individual and the system in which that person is expected to perform. Executives therefore need to ask a different question when evaluating a competency model. The question is not merely whether the organization has accurately described the leaders it wants. It is whether the organization has created the conditions in which those leaders can actually emerge and succeed.
When the Model Becomes the Answer
The appeal of a competency model is understandable because leadership is difficult to define, evaluate, and develop consistently, particularly across a large organization. A common framework gives leaders and employees shared language for expectations that might otherwise remain subjective. Done well, competency models can also connect organizational strategy to employee behavior and create greater consistency across talent practices. The problem is that the model can gradually become the answer to a question it was only designed to help clarify.
Once competencies are embedded across performance management, leadership development, succession, selection, and promotion, the organization can begin evaluating talent through the framework rather than evaluating whether the framework still represents what the business requires. “Strategic thinking,” “collaboration,” or “enterprise leadership” may remain in the model for years because each continues to sound important. The labels survive changes in strategy, operating model, technology, customer expectations, and organizational complexity. What appears to be consistency can eventually become inertia.
This is one of the central limitations of treating leadership effectiveness as a stable collection of attributes. The issue is therefore not whether competencies are inherently valid or invalid. It is whether the organization continues to treat the model as a hypothesis about what effective performance requires, or begins treating it as an enduring definition of effectiveness. That difference becomes particularly important when strategy changes faster than the talent architecture surrounding it.
Consider an organization moving toward faster innovation, greater cross-functional integration, distributed decision-making, and different technology. Its model may already include adaptability, collaboration, and strategic thinking, yet the demands beneath those familiar labels may have changed substantially.
Collaboration may now require resolving competing enterprise priorities rather than simply building relationships across functions. Strategic thinking may require investment choices under uncertainty rather than producing a long-range functional plan. The labels remain stable while the performance requirements change. The competency label remains the same while the performance requirement underneath it changes.
This is how competency models can create an illusion of precision. The organization appears to have defined what good leadership looks like because the language is clear, the behaviors are documented, and the model is embedded across talent systems. But clarity of language does not guarantee accuracy of representation. A model can be internally consistent and still become progressively disconnected from the conditions under which leaders must perform.
The problem is therefore not that competency models do not work. Their value depends partly on keeping the connection between strategy and competency alive. A competency model should never become organizational scripture. It is an interpretation of what the organization currently believes effective performance requires. When strategy, work, technology, structure, or customer expectations change materially, that interpretation should be tested again.
Defining Capability Is Not the Same as Building It
Even a competency model that accurately reflects current business requirements faces a second limitation: describing a capability does not create it.
An organization can define “enterprise mindset” with extraordinary precision and still operate through incentives that encourage leaders to protect their own functions. It can establish “empowerment” as a leadership expectation while requiring decisions to travel through several layers of approval. It can tell leaders to “develop others” while rewarding them primarily for immediate operating results and giving little recognition to talent development. It can emphasize “innovation” while responding to failed experiments in ways that teach leaders to avoid risk. In those circumstances, the competency model and the organizational system are sending different messages. Employees usually learn which message matters.
This is where competency conversations can become too individually focused. When leaders fail to demonstrate a desired behavior, the organization may conclude that a development gap exists. Sometimes that conclusion is correct. But the same pattern can also indicate a structural constraint, conflicting incentive, unclear decision right, workload problem, leadership norm, or other organizational condition that makes the desired behavior difficult or irrational.
The distinction matters because the interventions are completely different. Coaching an individual to become more collaborative will accomplish little if the operating model consistently places functions in competition for resources and rewards local optimization. Developing stronger decision-making capability will have limited effect if leaders are rarely allowed to make consequential decisions. Teaching adaptability cannot compensate indefinitely for governance that makes adaptation unnecessarily difficult.
A competency model tells the organization what it wants people to demonstrate. It does not explain why they are or are not demonstrating it. That requires a broader organizational diagnosis. This is also why competency models should be connected to the actual work through which capability develops. Leadership is not produced simply by understanding the behaviors associated with effective leadership. It develops through experience, feedback, reflection, increasingly difficult responsibility, and performance under real organizational conditions.
The executive implication is significant. If an organization invests heavily in defining competencies but does not examine the systems, experiences, and operating conditions through which those competencies must be demonstrated, it can create a sophisticated description of capability without materially increasing capability itself. That is not a failure of vocabulary. It is a failure to connect the talent system to the organization it is supposed to serve.
The Model Should Be Tested Against the Organization
The answer is not to abandon competency models, but to stop treating them as finished products. A useful competency model should remain connected to the strategic and organizational conditions that gave rise to it. Their value therefore depends not only on the quality of the definitions, but on whether those definitions remain aligned with what the organization is trying to accomplish and how work actually gets done.
Leaders should periodically test the model against reality. What capabilities does the strategy now demand? Which decisions are becoming more consequential? Where has work become more complex? What behaviors distinguish leaders who are succeeding under those conditions? The point is not to rewrite the framework whenever the business shifts. It is to determine whether the performance requirements beneath its labels have materially changed.
The same discipline applies when expected behaviors are absent. If leaders consistently struggle to operate across boundaries, the response should not automatically be another intervention around collaboration. Decision rights, incentives, structures, goals, or resource allocation may be reinforcing the boundaries leaders are being asked to cross. The model is more valuable when it helps generate that inquiry rather than prematurely locating the problem in the individual.
That creates a different standard for whether the model is working. Instead of asking how broadly it has been embedded across HR processes, executives can ask whether it improves the organization's ability to recognize, develop, and deploy the capabilities required for execution.
Organizations should also resist solving complexity by continually adding competencies, subcompetencies, behaviors, and proficiency levels. More detail can make a framework appear sophisticated while obscuring what matters most. More detail is useful only when it improves the organization’s ability to distinguish what matters and use the model well.
The executive objective is strategic discrimination, not descriptive completeness. The model should make the capabilities most consequential to organizational performance clear enough to inform better talent decisions.
What Great Organizations Do Differently
Great organizations do not treat a competency model as a finished product that becomes more valuable simply because it is embedded across more talent processes. They use it as a working interpretation of what effective performance requires, and they remain willing to test that interpretation as the business changes.
That starts with strategy and work, not the competency library itself. Great organizations periodically ask whether the capabilities they are emphasizing still reflect the demands leaders actually face. They look at how decisions are changing, where complexity is increasing, what new forms of coordination are required, how technology is altering the work, and which leadership behaviors now make a disproportionate difference to execution. If the meaning beneath familiar competency labels has shifted, the organization updates the expectations rather than assuming the existing language is still sufficient.
They are also more careful about what a competency gap actually represents. When leaders consistently struggle to demonstrate a desired behavior, stronger organizations do not immediately assume the solution is development. They examine the environment in which that behavior is expected to occur. If leaders are being asked to collaborate across boundaries while incentives reward functional performance, the constraint may be organizational rather than individual. If empowerment is expected but decision authority remains tightly centralized, the system may be limiting the very behavior the model says it values. This distinction is central to the article’s argument that a competency model can describe desired behavior without explaining why that behavior is or is not appearing.
Great organizations also connect competency expectations to the experiences through which capability is actually developed. They do not assume that assessment, training, or a development plan is sufficient simply because those mechanisms reference the model. They consider where leaders will have the opportunity to make difficult decisions, operate across boundaries, lead through uncertainty, build enterprise perspective, or take on responsibilities that generate real evidence of capability. The model helps clarify what matters, but the organization creates the conditions in which that capability can emerge.
They resist the temptation to solve every new business requirement by adding another competency, behavior, or proficiency level. More detail can create the appearance of rigor while making it harder for leaders to distinguish what truly matters. Great organizations make choices. They identify the capabilities most consequential to the strategy and accept that a useful framework does not need to describe every desirable characteristic of an effective leader.
They also judge the model by the decisions it improves. A competency framework should make selection, development, succession, promotion, or performance decisions more strategically relevant. If the model is widely embedded but leaders cannot explain which consequential decisions are better because it exists, the organization may have achieved consistency without achieving much strategic value.
The result is a different relationship with the model. Great organizations do not ask the competency framework to create leadership capability for them. They use it to clarify expectations, test whether those expectations still reflect the business, and improve the decisions through which capability is developed and deployed. That is what keeps the model connected to the organization rather than allowing the organization to become captive to the model.
A competency model should help leaders make better decisions about the capabilities the organization needs. These questions test whether it still serves that purpose.
1. Which competencies are genuinely differentiating for our strategy?
If nearly every desirable behavior appears in the model, it may describe a good leader without clarifying what this organization particularly needs. Leaders should be able to explain which capabilities matter disproportionately to execution and why.
2. What has changed in our business since this model was created?
Strategy, technology, structure, customer expectations, and work can change while competency frameworks remain untouched. The test is not whether the labels still sound relevant, but whether the demands beneath them remain accurate.
3. Are we diagnosing an individual capability problem or an organizational constraint?
Repeated gaps across leaders should prompt examination of the environment as well as the individual. Structure, incentives, governance, workload, or leadership norms may be contributing to the pattern.
4. Where do people actually acquire the capabilities we say matter?
If a capability is strategically important, leaders should know where people build and demonstrate it. Its presence in an assessment, development plan, or curriculum does not prove the organization creates meaningful opportunities to develop it.
5. What talent decision becomes better because this model exists?
Competency models can support selection, development, assessment, and performance management. But integration is not impact. If leaders cannot identify a consequential talent decision that becomes better because the model exists, its sophistication may be exceeding its strategic value.
Competency models are most useful when they help an organization make explicit choices about the capabilities required for performance. They become less useful when the framework itself becomes the objective.
Leadership effectiveness does not occur independently of organizational context. A model can describe desired behavior without capturing every condition that enables, constrains, or changes what effective leadership requires.
That should change how executives interpret competency gaps. When a desired behavior is absent, leaders should first determine what the evidence represents. The organization may have an individual capability gap, the wrong capability for the work, an environment suppressing the behavior it claims to value, or a business that changed while the competency architecture did not.
None of this makes competency models irrelevant. Thoughtfully constructed models can provide useful behavioral language and help translate strategic priorities into expectations. The mistake is expecting the model to substitute for the organizational systems through which capability is developed and demonstrated.
The stronger standard is whether the model still represents the capabilities the strategy requires and improves consequential talent decisions. A competency framework should serve the organization, not become an artifact the organization feels obligated to preserve.
A competency model can define what capability should look like. It cannot create the conditions that make capability possible.
Supporting Research
- Campion, M. A., Fink, A. A., Ruggeberg, B. J., Carr, L., Phillips, G. M., & Odman, R. B. (2011). Doing competencies well: Best practices in competency modeling. Personnel Psychology, 64(1), 225–262.
- Campion, M. C., Schepker, D. J., Campion, M. A., & Sanchez, J. I. (2020). Competency modeling: A theoretical and empirical examination of the strategy dissemination process. Human Resource Management, 59(3), 291–306.
- Hollenbeck, G. P., McCall, M. W., Jr., & Silzer, R. F. (2006). Leadership competency models. The Leadership Quarterly, 17(4), 398–413.
- Oc, B. (2018). Contextual leadership: A systematic review of how contextual factors shape leadership and its outcomes. The Leadership Quarterly, 29(1), 218–235.
