Why Most Competency Frameworks Get Shelved Within Eighteen Months

Most competency frameworks are not failures of intelligence. They are failures of adoption strategy. The documents themselves are often genuinely good: well-researched, coherently structured, behaviourally anchored, and aligned to the organisation’s stated strategic direction. The design teams that produce them are typically composed of capable HR professionals who have done the analytical work thoroughly. And yet the frameworks are shelved within eighteen months of launch in the majority of cases, quietly superseded by the next initiative, referenced in job descriptions but absent from performance conversations, cited in succession reviews but unknown to the managers who are supposed to use them every day.

I have observed this pattern across organisations in financial services, manufacturing, technology, and professional services. The failure is not sector-specific and it is not a function of organisation size. It is a design failure, but the design flaw is not in the competency architecture itself. It is in the fundamental misunderstanding of what adoption actually requires, and in the chronic underinvestment in the conditions that make a framework genuinely operational rather than merely technically sound.

The seduction of the comprehensive framework is part of the problem. HR teams are drawn toward completeness, toward frameworks that account for every level, every functional role, every leadership dimension. The result is a document that is intellectually satisfying and practically unmanageable. A framework with twenty-two competencies across four leadership levels, each with five behavioural indicators at three proficiency levels, is not a management tool. It is a reference document, and reference documents do not change behaviour. BEHAVIOUR CHANGES WHEN PEOPLE HAVE A SHORT LIST OF OBSERVABLE ACTIONS THEY CAN REMEMBER WITHOUT OPENING A DOCUMENT. The more comprehensive the framework, the less likely it is to live in the daily working vocabulary of the managers it is designed to equip.

This is not an argument against rigour. It is an argument for a specific kind of rigour, one that is as focused on operational simplicity as it is on theoretical completeness. The best competency frameworks I have worked with in my career have not been the most comprehensive. They have been the ones where the organisation made a deliberate choice about what was most important, had the discipline to cut everything else, and then invested heavily in making the remaining content genuinely familiar to the people who were expected to use it.

The second failure mode is in the design process itself, specifically in who is and is not involved. Competency frameworks are almost universally designed by the HR function, validated by HR leadership, and then handed to the business. In some cases, senior leaders are consulted in focus groups or validation interviews. In fewer cases, managers are consulted. In almost no cases are managers substantively involved in the act of creation: in deciding what to include, how to express it, what it should look like in practice in the specific contexts of their own work.

This matters enormously, and the reason it matters is not simply about buy-in, though buy-in is relevant. It matters because competency frameworks describe behaviour in language, and language that has been generated by HR professionals describing leadership behaviour is consistently different from the language that managers use to think about and discuss the same behaviour with their teams. THE TRANSLATION GAP BETWEEN HR LANGUAGE AND MANAGER LANGUAGE is one of the primary adoption killers, and it is entirely preventable with a different design process.

I worked with one organisation in the financial sector where we ran a retrospective analysis of their competency framework launch eighteen months after deployment. The adoption data was poor: only 31% of managers reported using the framework in performance conversations with any regularity, and qualitative interviews revealed that the primary reason was language. Managers could not see themselves or their teams in the descriptions. The competency language felt like it had been written for a different organisation, or for a generic version of leadership that did not correspond to the specific demands of their context. The framework was technically accurate. It described the right things. But it did not speak in a voice that the organisation’s managers recognised as their own.

The third failure mode, and the one with the most direct operational consequence, is the absence of an explicit connection between the competency framework and the performance conversation. Frameworks that are designed as standalone documents, as descriptions of ideal leadership behaviour that exist independently of the organisation’s performance management process, are dead on arrival regardless of their quality. Behaviour changes when it is assessed, discussed, and held to account in the recurring conversations that managers and their direct reports have about performance. A competency framework that does not appear in those conversations does not change behaviour.

This sounds obvious, but the execution is consistently weak. Organisations that invest significantly in competency framework design invest proportionally far less in redesigning the performance conversation structure to reflect the framework. They may update the performance review form to include a competency section, but they do not equip managers with the conversational skills and structured approaches needed to discuss competency evidence effectively. ADDING A COMPETENCY SECTION TO A PERFORMANCE FORM IS NOT INTEGRATION. It is addition. Integration requires that managers understand how to observe competency indicators, how to gather evidence, how to give specific and actionable feedback against a competency anchor, and how to have a developmental conversation that helps a team member understand exactly what change is expected and what it would look like.

The organisations where I have seen competency frameworks genuinely operational, where they are discussed in team meetings, referenced in development conversations, used in promotion decisions and succession reviews, have one thing in common: they treated the rollout not as a communication exercise but as a CAPABILITY DEVELOPMENT PROGRAMME for managers. The investment in manager capability was as significant as the investment in framework design. The two were explicitly linked. And the framework itself was kept short enough that managers could internalise it rather than consult it.

Behavioural anchors are supposed to solve the abstraction problem. The idea is sound: instead of defining competencies in terms of qualities or dispositions, the framework describes specific, observable actions that a person demonstrating the competency would take. “Collaborates effectively” becomes “proactively shares relevant information with team members before being asked” or “seeks input from adjacent functions before finalising plans with cross-functional impact.” The behaviour is visible, specific, and discussable.

In practice, the behavioural anchors in most frameworks are not behavioural enough. They use action verbs, which creates the appearance of behavioural specificity, but the actions they describe are frequently still at a level of abstraction that requires interpretation. “Demonstrates strategic thinking by anticipating the longer-term implications of decisions” is nominally a behaviour, but what does “anticipating” look like in a specific context? How would a manager recognise it? How would a team member know they were doing it? THE GAP BETWEEN THE ANCHOR AND THE OBSERVABLE ACTION is often the difference between a framework that functions in performance conversations and one that does not.

The frameworks I have found most useful in my own advisory work are the ones that take behavioural anchoring seriously enough to be context-specific. That means going through the additional design step of asking managers in specific roles and functions: in your context, what does this competency look like on a Tuesday morning? What would you observe? What would you hear? What would be different about the work? That level of specificity requires more design investment upfront. It produces a framework that is less universally generalisable. And it produces a framework that managers actually use, because it describes behaviour in a language that corresponds to their working reality.

Rebuilding a competency framework for adoption requires a willingness to sacrifice comprehensiveness for usability, which is a harder trade-off than it sounds because HR functions are built to value completeness. The strategic choice is to design for the manager’s daily working reality rather than for the HR function’s theoretical requirements, and that choice has implications throughout the process.

Start with the performance conversation, not with the competency architecture. Ask: what do managers most need to be able to discuss with their direct reports about leadership behaviour, capability development, and readiness for increased responsibility? Design the framework to answer that question, and hold everything that does not directly serve that answer out of the core framework. It can live in appendices, in supporting documentation, in role-specific supplements. THE CORE FRAMEWORK SHOULD FIT ON ONE PAGE and be comprehensible at a glance by a manager who has not attended a training session on it.

Then invest proportionally in manager capability. Design the performance conversation structure explicitly. Provide worked examples of how the competency framework is used in a development discussion, a performance review, a promotion conversation, and a succession calibration. Run manager workshops that are not about understanding the framework but about practising the conversations it is supposed to enable. And build in the accountability mechanisms: the competency framework should appear in recurring performance processes, not as a bureaucratic addition but as the shared vocabulary through which development discussions are held.