In the past few years, skills have become the dominant unit of currency in organisational development. Almost every large organisation now has a skills initiative underway, platforms that map, tag, and visualise what their people can do. These systems promise better workforce decisions, clearer career pathways, and more targeted learning investment.
It's a compelling proposition. If we can catalogue the skills that exist within an organisation, we can see gaps, plan more precisely, and build with intention. But like any good ledger, what's written down only tells part of the story. What sits beneath the visible inventory of skills, the inner architecture of how people make sense of their work, is far more dynamic, and often invisible to the systems designed to assess it.
The Outer System and the Inner System
Organisations tend to think of skills as discrete and measurable. You can observe a person performing a task, you can record it, and you can validate it through assessment or certification. This makes skills easy to count and compare. Yet, behind every demonstrated skill sits an interpretive process, how a person perceives complexity, navigates ambiguity, and relates to others.
That interpretive process, what adult development theorists call developmental range, defines the space in which skills operate. Two people might share the same skill profile on paper, yet inhabit very different worlds of meaning. One might execute a process precisely, while another might adapt that process to fit shifting contexts, noticing emergent patterns or underlying relationships. The skill is the same, the developmental range is not.
When workforce systems treat skills as static units, they inadvertently compress this range. They can show what people can do, but not how they understand what they're doing, or what they might become capable of as they grow.
Development as Meaning-Making
Developmental range refers to the breadth and depth of a person's meaning-making capacity, the mental, emotional, and relational scaffolding through which they interpret experience. Robert Kegan's work in adult development, for example, describes the journey from subject (where we are defined by our beliefs and assumptions) to object (where we can hold those same beliefs and examine them).
In an organisational context, this matters because the demands of work are increasingly developmental rather than purely technical. It's not just that people need new skills, it's that they need to navigate greater complexity, ambiguity, and interdependence.
A person's developmental range influences how they handle uncertainty, collaborate across boundaries, and integrate feedback. It shapes how they learn and unlearn. And yet, most systems of assessment and validation stop at the outer layer, the skills themselves. We end up investing in training that extends the catalogue without expanding the capacity.
When Skills Outpace Sense-Making
This is often why large-scale skills initiatives feel curiously flat. Organisations proudly announce that they've "mapped 80,000 skills across 10,000 employees," yet struggle to convert that information into meaningful action.
The problem isn't the data. It's the developmental assumption beneath it, that performance and adaptability can be derived from visible skills alone.
When people's internal sense-making lags behind the complexity of their environment, even the most sophisticated skills data will mislead. You can teach systems thinking, but it doesn't mean someone can yet see systems. You can train for collaboration, but collaboration at scale requires a level of perspective-taking that only develops through deeper meaning-making processes.
In this way, skills can outpace development, like giving a powerful instrument to someone who hasn't yet learned to hear.
The Organisation as Ecosystem
If we think of an organisation as an ecosystem rather than a machine, then skills are the visible species, while developmental range is the invisible climate. The species can evolve and adapt only within the bounds the climate allows.
The ecosystem metaphor matters because it reframes the purpose of skills validation. It's not just about classifying capabilities; it's about cultivating the conditions under which those capabilities can thrive. Developmental range is not a HR metric, it's a system property. It defines how the organisation learns, not just how individuals perform.
When seen through this lens, the intersection of developmental range and skills validation becomes less about measurement and more about feedback. Skills data tells us where we are; developmental insight tells us how we got here, and what growth might require.
Bridging the Two Systems
The challenge, then, is integration. Skills validation systems and developmental frameworks have grown up separately. The first is data-rich, platform-driven, and externally oriented. The second is interpretive, slow, and deeply human.
But they need each other. Without developmental insight, skills data remains a surface map, informative but not transformative. Without skills data, developmental insight risks abstraction, insightful but unanchored.
A more integrated approach might look like this:
- Skills assessments that recognise the underlying developmental capacities required for mastery
- Learning programs that scaffold not just new tasks but new ways of thinking
- Performance reviews that explore not only "what was done" but "how it was made sense of"
This is what it means to treat development as an ecosystem, to see every skill as both an outcome and a portal into deeper meaning-making.
From Validation to Valuation
Perhaps what's needed is not better validation but a different kind of valuation. The question shifts from "What skills do our people have?" to "What's the depth and diversity of understanding that our organisation can hold right now?"
Skills frameworks will continue to improve, and rightly so, they help translate work into language. But language, to be alive, must evolve. Developmental range is that evolving grammar. It's how organisations learn to think in more complex ways, to see themselves not as collections of functions but as living systems of sense-making.
We can't manage what we don't understand, and we can't understand what we refuse to see. Skills are visible; development is often not. Yet both are present in every conversation, every decision, every act of learning.
The fog only clears when we learn to see through both layers at once.