There is a competency framework sitting on a shared drive somewhere in your organisation. It was built in 2019. A cross-functional working group spent four months on it. There were workshops. There was a vendor. There was a colour-coded grid with proficiency levels, behavioural indicators, and a maturity ladder that ran from Foundational to Strategic. It was beautiful. It was signed off by the leadership team. It became the backbone of every development plan, every learning path, every promotion conversation for the next four years.
About a third of what it described no longer matters.
Not because the working group was wrong. They were right, in 2019. They captured the skills that defined good performance in the roles as the roles existed then. The problem is that the roles did not hold still. The tools changed. The market changed. The thing the business actually needed people to be good at moved, quietly, while the framework stayed exactly where it was. And the L&D function kept training to the map long after the territory had been redrawn.
The Half-Life Nobody Prices In.
Every skill has a half-life. Some are long. Judgment, the ability to listen, the capacity to make a decision when the data is incomplete and the room is tense. These age slowly, if at all. Others are short. The specific platform, the specific process, the specific way a task was done in a specific tool that has since been deprecated, acquired, or replaced by something that did not exist when the curriculum was written.
The trouble is that competency frameworks treat all skills as if they have the same half-life. A line item that reads "proficient in stakeholder reporting using the current BI suite" sits next to a line item that reads "navigates ambiguity and aligns competing priorities" as though they decay at the same rate. They do not. One of them was obsolete within eighteen months. The other will still be relevant in 2040. The framework cannot tell them apart, because it was built to be comprehensive, not to be durable.
So the L&D team does what the framework instructs. It builds learning paths against the whole grid. It tracks completion against the whole grid. And a meaningful slice of that effort is spent moving people toward proficiency in things that will not survive the next reorganisation.
This is the quiet waste that never shows up in a budget review. It is not the cost of the training that was cancelled. It is the cost of the training that ran perfectly, was completed enthusiastically, scored well on the reaction survey, and developed a skill the business had already stopped needing.
How the Map Ages Faster Than the Curriculum.
Here is the mechanical reason this keeps happening, and it has nothing to do with anyone being lazy or unobservant.
A competency framework is expensive to build and politically expensive to change. Building it required consensus across functions. Changing it requires re-opening that consensus. Nobody wants to be the person who says the framework the CHRO approved two years ago is now partly wrong, because that conversation implicates everyone who signed off on it. So the framework calcifies. It becomes a fixed reference point in a moving system, and its authority grows precisely because nobody updates it. People stop questioning it. They start treating it as the definition of good, rather than as one snapshot of good taken at one moment under one set of conditions.
Meanwhile the actual work moves continuously. A function adopts a new tool in March. A market shift in June changes which decisions matter most. A reorganisation in September collapses two roles into one, and the blended role needs a kind of judgment neither original role required. None of this triggers a framework update, because framework updates are annual at best and the work does not operate on an annual cycle.
The gap between the framework and the work does not appear suddenly. It widens by a few degrees every quarter. By year three it is wide enough that managers quietly ignore the framework when they have the real development conversation, and then dutifully fill in the grid afterward so the system has its data. The framework is no longer guiding development. It is being retrofitted to it. The L&D function is collecting evidence of compliance with a map the organisation stopped following some time ago.
A competency framework does not fail loudly. It fails by becoming the thing everyone documents against and nobody actually develops toward.
The Skill That Was Never on the Grid.
Consider the manager who was developed flawlessly against the 2019 framework. Every box ticked. Strong on the technical competencies, strong on the process competencies, certified on the tools. On paper, a complete leader.
Then the tool gets replaced. The process gets automated. The market the strategy was built for shifts. And the question the business now needs this manager to answer is not in the framework at all, because in 2019 nobody knew it would be the question. The framework prepared them to be excellent at a job that has partially ceased to exist. It did not prepare them to recognise that the job had changed, or to decide well once the old playbook stopped applying.
That recognition. That capacity to operate when the map is wrong. That is the actual durable skill. And it is precisely the one a competency grid is worst at capturing, because it cannot be reduced to a proficiency level. You cannot be Level 3 in "noticing the framework is obsolete." It does not decompose into behavioural indicators. It lives in how someone responds when the situation matches nothing they were trained for, which is the one situation a comprehensive framework guarantees they were never trained for.
The Turn.
Here is the part most L&D functions have backwards. The fix for an ageing competency framework is not a better, faster, more frequently updated competency framework. Organisations have tried that. They build dynamic skills taxonomies, they buy skills-inference engines, they re-baseline annually instead of every three years. It helps at the margin and it misses the point entirely. A map that updates faster is still a map. It still trains people toward known answers to known questions. It still has nothing to say about the moment the questions change.
The durable asset was never a current list of the right skills. It was the judgment that lets a person perform when the list is out of date, which it always eventually is. Organisations that keep chasing a more accurate framework are optimising the wrong layer. They are sharpening the map while the territory is the problem.
What Rebuilding Looks Like.
A development system built for a world that moves looks different from a competency grid, and the difference is not cosmetic.
It separates the perishable from the durable, openly. Tool proficiency, process fluency, and current-method skills are treated as exactly what they are: necessary, valuable, and expiring. They are trained efficiently and replaced without ceremony when they expire. The system does not pretend they are permanent, and the organisation does not measure a leader's development primarily by them. They are the floor, not the building.
It develops judgment as the load-bearing layer. Not as a soft competency tucked into the corner of the grid, but as the central thing the system is designed to build and surface. How does this person decide when the data is incomplete? How do they respond when the situation does not match the training? What do they do in the first ninety seconds of a problem they have never seen before? These are developable. They are also observable, if you build the right conditions to observe them, which is a very different exercise from scoring someone against a checklist.
And it accepts a harder truth about what the L&D function actually owes the business. The job was never to certify people against a fixed definition of good. The job is to build people who stay good while the definition moves. That is a systems problem, not a curriculum problem, and it cannot be solved by writing a better grid.
This is the work SSUNDAR is built for. Many of our engagements begin with an organisation that has an immaculate competency framework and a leadership population that struggles the moment a situation falls outside it. The framework is rarely the thing we rebuild first. The thing we rebuild is the architecture underneath it, the part that decides whether the organisation is developing judgment or just maintaining an inventory of skills with an expiry date nobody printed on the label.
The skill they built in 2019 is gone. The leaders who could see it going are the only ones the framework never measured.