The Common Capability Currency

Why every workforce transformation fails without a shared language for work, skills and organisational capability.

‍

By Chris Woodward - Founder & Managing Director, Cello Consulting

‍

Finance would never dream of running without a chart of accounts. A global supply chain could not function for a single day without standard product definitions. Yet most large organisations describe their own workforce - their most expensive and most strategic asset - using hundreds of inconsistent job titles, half a dozen competing competency models, and whatever local frameworks each function happened to build when nobody was looking.

Then we wonder why workforce transformation is so hard.

I have come to believe that the single biggest reason these programmes stall has almost nothing to do with technology, budget or executive appetite. It is that the organisation has no common language for work. Recruitment describes a role one way, learning describes it another, succession a third, and the workforce planning team a fourth. Each dataset is perfectly sensible on its own. None of them connect. And you cannot make a good enterprise decision on data that refuses to join up.

Most organisations do not have a data problem. They have a language problem wearing a data problem's clothes.

The currency that is missing

I have started calling the thing that is missing a ‘common capability currency’ or ‘language for talent’. The metaphor is deliberate. A currency is only useful because everyone agrees what it represents and will accept it in exchange. Language because we all need to share and understand how to talk about it in a consistent way. It lets a farmer and a software engineer trade without bartering chickens for code. In exactly the same way, a common capability currency lets HR, finance, operations and strategy trade in workforce decisions using evidence they all recognise and trust.

Without it, every conversation degenerates into barter. Finance wants cost per head. Operations wants bodies on shift and utilisation. HR wants engagement scores. Strategy wants "digital capability," whatever that means this quarter. Everyone is arguing in a different denomination, and the exchange rate between them is often set by whoever shouts loudest in the meeting.

The organisations that break out of this do one unglamorous thing well. They agree, once, on how they will describe work and talent - and then they govern that agreement as carefully as finance governs the chart of accounts.

The four layers most organisations blur

Here is where it gets interesting, and where most well-intentioned skills programmes quietly come off the rails. In the work I do with clients, I insist on separating four things that are almost always mashed together, because blurring them is precisely what makes workforce data tricky to work with.

The first layer is organisational capability - a collective ability the enterprise must possess to deliver its outcomes. "The ability to certify a safety case," not "a safety engineer." The second is work and roles - the activities and accountabilities through which that capability is actually delivered. The third is skills, knowledge and behaviours - what an individual needs to perform the work. And the fourth is proficiency - the level at which they can perform it, including the autonomy and assurance the context demands.

These are not the same thing, and the boundary between them matters enormously. A strategic capability map is not a skills inventory, and the fastest way to sink a transformation is to confuse the two. I have watched organisations spend a fortune cataloguing thousands of individual skills in exquisite detail, only to find they still cannot answer the one question the board asked: are we capable of delivering the strategy or not? They had counted the trees so obsessively they had lost the entire forest.

A capability map is not a skills inventory. Confuse the two, and you will count trees until the forest burns down.

Where the technology finally earns its keep

For twenty years, the honest answer to "why don't organisations have this common language" was that building it by hand was brutally expensive. Mapping capability across thirty thousand people meant workshops, spreadsheets, and consultants - I’ve experienced this first hand - armed with sticky notes and optimism. By the time you finish, the organisation has moved on.

That constraint has genuinely changed, and this is where I part company with the sceptics. Modern skills-intelligence platforms can now infer capability from the work people actually do - the projects they deliver, the systems they touch, the learning they complete - rather than relying on someone remembering to update a profile once a year. AI can read across that evidence and connect it to external labour-market data, so an organisation can finally see its internal supply and the outside market in the same frame.

This is the terrain that Toby Culshaw maps out in his work on Talent Intelligence, that Rupert Morrison has argued for years in Data-Driven Organization Design, and that Adam Gibson sets out in Agile Workforce Planning: the idea that people, integrated capability planning expertise and organisational data, properly connected, become a genuine decision-making capability rather than an HR reporting chore. The technology has, at last, caught up with the ambition.

But - and this is the part the vendors tend to skip - the technology is not the point. The value was never in the map. It was always in the decisions the map makes possible.

The hidden talent problem

Let me make that concrete. A safety-critical nuclear organisation I worked with was quietly convinced it was running out of a particular specialist capability, and had begun the slow, expensive process of recruiting externally into a labour market where everyone else was fishing for the same rare people.

When we described the capability properly - not as a job title, but as the underlying ability and the proficiency the work demanded - a very different picture appeared. A meaningful pool of people already held most of that capability. They had grown it on adjacent programmes, or brought it from previous careers, and it was completely invisible to the system because their job titles said something else entirely. The organisation didn't need to buy that talent on the open market. It needed to see the talent it had already paid for and developed in other parts of the business or collaborate more at sector level to create bold and innovative sourcing strategies (eg secondment programmes and Regional development hubs as seen in the Defence Sector).

This is what a common capability currency actually buys you. It surfaces hidden talent. It lets you compare internal supply against future demand honestly. It turns the build-buy-borrow decision from a hunch into an evidence-based choice. And it changes the conversation you have with the executive team, from a defensive discussion about vacancies into a strategic one about capability risk, investment priority and resilience.

Say what the evidence can't yet tell you

I want to be careful here, because this field is full of people selling certainty. The evidence that capability language matters is strong - the World Economic Forum, Gartner and others have all shown that skills requirements are changing far faster than traditional job architectures can track. Gartner's own data has the number of skills attached to a single role climbing around 10% a year. But the evidence on which taxonomy to adopt, how granular to go, and how much to trust AI-inferred skills over human judgement is genuinely contested, and anyone who tells you otherwise is selling something.

So my advice to leaders is unfashionably modest. Do not start by buying the biggest skills library you can find. Start by deciding which handful of workforce decisions you most need to make well - where to invest, what is critical, what to build versus buy - and build only enough common language to make those decisions defensible. Let the decisions pull the architecture into being, not the other way round.

Capability becomes the language through which strategy is translated into action. Get that language right, governed and shared, and every other workforce discipline finally has something solid to stand on. Get it wrong, and you will keep bartering chickens for code - and calling it transformation.

Selected references

Toby Culshaw, Talent Intelligence (Kogan Page, 2022)

Rupert Morrison, Data-Driven Organization Design (Kogan Page)

Adam Gibson, Agile Workforce Planning (Kogan Page, 2021)

World Economic Forum, Future of Jobs 2025 · Gartner.

Cello Consulting - Better workforce decisions. Better workforce capability. Better organisational performance.