Forget Job Descriptions: Why Capability is the Only Workforce Metric That Matters

Years ago I sat my final pianoforte exam and passed. I still have the certificate. I could not, however, sit down and play in public today, let alone take my place in an orchestra. The skills were real once, and the credential is real still, but neither tells you what I am capable of now. I keep coming back to that gap, because it runs straight through the way we hire, train and deploy people for work.

It also makes me wary of the current rush to predict the future of work. There is no shortage of futurists at the moment. Open LinkedIn and you will find confident forecasts about AI, automation, agents and the end of work as we know it. Yet it is worth remembering that only a few years ago the same certainty pointed in one direction “coding”. Learn to code, people were told. Coding bootcamps multiplied, software engineering was sold as the safe bet for the next generation, and thousands of people reorganised their study and their careers around that forecast. Many of them are now entering a market where entry-level technology roles have contracted sharply and junior positions are among the hardest to find in years. The prediction was confident. For a lot of the people who acted on it, it was also wrong.

That is the problem with forecasting dressed up as certainty. Many of the loudest voices have never hired a single employee, run a business through a cashflow crisis, supervised an apprentice, or spent years working at the intersection of industry, training and skills policy.

I have spent too many years in standards development, workforce development, and regulation and small business policy. I have worked with employers who cannot find the people they need, with workers trying to prove what they can do, and with governments attempting to solve workforce shortages that never quite go away.

If you want to understand the future of work, follow the skills.

The constraint isn’t technology

The real limit on the future of work is not technology. It is our inability to see capability. For more than a century we have organised labour markets around job titles. We recruit for job titles, train to job descriptions, pay according to job titles and promote people through them. Yet job titles are becoming poor indicators of what a person can do.

The OECD’s work on skills-first labour markets describes a steady shift away from traditional signals such as degrees and job titles, and towards demonstrated skills and the recognition of capability wherever it was acquired. LinkedIn’s Economic Graph research points the same way. When employers assess candidates on their skills rather than their past job titles, the available talent pool expands dramatically, by close to ten times on average across industries.

The labour market of the future will ask what you can do, rather than what job you have done. That single change reshapes almost everything that follows.

The death of the job description

The traditional job description assumes that work is stable, that occupations stay broadly the same for years, and that a qualification is a dependable proxy for capability. None of those assumptions holds as well as it once did. AI is changing the tasks inside roles faster than most organisations can rewrite their position descriptions. Project-based work is replacing rigid structures. People now build careers across several employers, industries and types of work.

What matters is no longer the job title on someone’s contract. It is the portfolio of things they are capable of doing. The unit of analysis is moving from jobs to skills, and from skills to capability.

Skills and capability are not the same thing

One of the most common mistakes in workforce conversations is to treat skills and capability as interchangeable. They are not. Skills are the inputs. Capability is what those inputs produce when they are current, combined and applied in context.

Return to that piano for a moment. Reading music, keeping time, sight-reading and playing the notes are all skills. Performing well in an orchestra is a capability, and it exists only when those skills are current, combined and applied alongside other players in a live setting. My certificate records that I once had the skills. It says nothing about whether I could hold a seat in the orchestra today.

The same holds in any workplace. Negotiation, communication, project planning, data analysis and stakeholder engagement are all skills. Leading a complex transformation program is a capability built from them. Capability is what employers ultimately pay for, and a qualification earned years ago is a weak guide to whether someone has it today. That is why granularity matters. “Project Manager” is a job title. The dozens of skills sitting beneath it are what tell you whether a person can actually do the work.

Why apprenticeships are under strain

This problem is easy to see in the apprenticeship system. The issue is not that employers have stopped valuing training. It is that, for many small businesses, the economics have become too hard to justify. Small firms still carry much of the cost of training Australia’s future workforce while absorbing rising wages, higher insurance premiums, growing compliance obligations and constant cashflow pressure.

A small business will often invest years in an apprentice, wearing the reduced productivity, the supervision time and the direct cost of training, only to watch that person be recruited by a larger organisation offering higher pay soon after they qualify. Nobody sensible argues against labour mobility. But from the perspective of the employer who made the investment, the business that paid for the training is frequently not the one that receives the return. If enough employers decide the numbers no longer add up, fewer of them will take part, and no amount of talk about skills shortages will fix the structural gap that follows.

Skills are everywhere; visibility is not

Here is the workforce problem almost nobody names. Skills are everywhere. Visibility is not.

Most workforce systems can tell you what qualifications a person holds, what courses they have finished, what role they occupy and where they sit on an organisational chart. What those systems struggle to show is whether that same person has coordinated disaster-relief volunteers, managed the care of an ageing parent, run a small business, led a community organisation, or held a household budget together through a hard year.

Those experiences build exactly the capabilities employers say they cannot find: leadership, resilience, negotiation, problem solving, risk management and planning. The capabilities exist. They are simply invisible to the systems we use to look for them.

Enterprise systems solve the employer’s half of the problem

Enterprise platforms have made real progress here. Workday’s Skills Cloud, for example, gives organisations sophisticated skills intelligence, inferring the skills present in a workforce and supporting internal mobility and workforce planning. These are important advances, but they answer a specific question: what skills do we already have inside this organisation? That is different from asking what a person is capable of across their whole life.

Most enterprise systems, by design, see only the data that sits inside the employer, such as current role, learning records, internal projects and performance history. The harder and more valuable question concerns the capability people build outside paid work. The volunteer firefighter who is also a logistics manager. The parent who has coordinated years of complex care. The community leader who has quietly mastered stakeholder engagement. The small business owner who learned financial management, negotiation and crisis leadership the hard way. That capability is real and valuable, and it usually goes unrecorded.

From hiring for jobs to deploying for capability

The next shift goes further than hiring for skills instead of job titles. Organisations are starting to deploy people according to the capabilities a piece of work actually requires. In Work Without Jobs, Ravin Jesuthasan and John Boudreau argue that organisations will increasingly break jobs down into their component parts and reassemble work around skills and capabilities rather than fixed roles. Research on project-based organisations points in the same direction, treating workforce planning as the continual matching of people’s capabilities to the demands of the work in front of them.

Consider how work is increasingly organised: around projects, transformation programs, innovation initiatives and specific customer problems, rather than static positions. When a team is assembled for one of these, the organisation does not simply need “a project manager” or “an analyst.” It needs a particular combination of capabilities, including problem solving, communication, data literacy, risk management, stakeholder engagement, leadership and adaptability. The job title matters less. The capability matters more. Employers will increasingly hire for skills, but they will deploy for capability.

The next frontier is lifewide skills visibility

This is where I believe we are heading. Not towards bigger skills inventories, but towards better skills visibility, and not only of workplace skills. Lifewide skills, built through employment, volunteering, entrepreneurship, community leadership, caring responsibilities, informal learning and lived experience.

Careers no longer belong to organisations. People move between employers, industries, self-employment, contract work, study and volunteering across a working life. There is no good reason for the evidence of what they can do to stay locked inside a single employer’s system. A workforce may belong to an employer, but skills belong to the person. The next generation of skills infrastructure has to let individuals capture, own and carry that evidence with them.

Visibility will matter more than credentials

The OECD identifies one of the central challenges of a skills-first labour market as the difficulty of recognising, validating and trusting skills that sit outside formal credentials. That is the problem worth solving. Not more qualifications, more job titles or more occupational classifications, but visibility that is trusted and portable. Capability we cannot see cannot be matched. Capability we cannot match cannot be deployed. And capability that is never deployed becomes lost productivity for the person, the organisation and the wider economy.

Capability is the point

This is why SkillsAware is working with Capability Co. For a long time we measured qualifications, and more recently we started counting skills. The frontier now is understanding capability. My piano certificate proves I once passed an exam; it says nothing about whether I could perform today. Organisations are no different. They do not create value from isolated skills, or from credentials earned years ago, but from the capability that emerges when current skills are combined and applied in context.

The advantage will belong to employers who can see skills at a granular level, understand how those skills add up to capability, and put people to work on the projects and problems where they will make the most difference. By connecting granular skills visibility with capability thinking, SkillsAware and Capability Co are trying to move the conversation on from “what qualifications do people have?” to a more useful question: “what are people capable of achieving?” That may turn out to be the most important workforce question of the coming decade.