Workforce Capability by Design
Why capability - not headcount - has become the new currency of organisational performance.
By Chris Woodward - Founder & Managing Director, Cello Consulting
There is a moment I have watched play out in more boardrooms than I can count. The strategy is signed off. The investment is committed. The transformation slides look immaculate. Then someone at the end of the table, often the least senior person there, asks the only question that really matters: do we actually have the people to deliver this?
What follows is usually silence. Not because the leaders in the room don't care about their people - they care enormously - but because nobody can answer with any confidence. Finance has one set of assumptions, operations another, HR a third. Recruitment is already scrambling. Learning is waiting for someone to raise a ticket. And the workforce plan, if it exists at all, is a spreadsheet somebody built for last year's budget round and hasn't opened since.
I spent nineteen years as an Army officer before I ever set foot in a corporate HR function, and six of those years were spent on operations where the gap between the plan and the people to deliver it was not an abstraction. It was the difference between a task that worked and one that didn't. That experience left me with a conviction I have never shaken: capability is not something you discover halfway through delivery. It is something you design in and develop from the start.
Capability should not be discovered halfway through a transformation. It should be designed from the beginning.
Capability by accident
Most organisations, if they are honest, plan their workforce by accident. They plan structures, grades and headcount, because those are the things finance understands and the payroll system can count. They fill vacancies as they appear. They react to the loudest business unit. And they call the sum of all that activity a workforce strategy.
The trouble is that headcount tells you how many people you employ. It tells you almost nothing about what those people can actually do, how quickly they could do something different, or whether the abilities your strategy depends on exist inside the building at all. A defence programme does not fail because you are three people short. It fails because the one systems engineer who understood the safety case has retired, and nobody knew how exposed the organisation was until she left.
This is why I have come to talk about Capability by Design. It is a deliberately unglamorous phrase, and I use it precisely because it forces a different starting point. Capability by Design begins with the strategy, not the vacancy. It asks which organisational capabilities will genuinely create value, which of them are truly critical, what work will have to change, where that capability already exists - often invisibly - and whether it should be built, bought, borrowed, automated or simply redesigned out of existence.
That is a very different conversation from "how many heads can we afford next year." And it is one that finance, strategy and operations can actually join, because it is expressed in the language of the business rather than the private dialect of HR.
The talent you already have
A few years ago I worked with a global engineering group of more than thirty thousand people. The leadership was convinced it had sufficient specialist engineers, line managers were maxed out and dock space was at a premium. However initial analysis through SWP revealed a compound demand for these critical roles between two and four years in the future. The instinct was to wait - an entirely reasonable one considering the timeframe - and then recruit its way out of the problem, topped up with a layer of contractors where required.
We didn't start with recruitment. We started by mapping capability rather than job titles, and two interesting things happened. Firstly it created resourcing strategy choices – an investment decision was made to fund £30M for apprenticeship and early careers pathways over this period to develop much of the right skills and experience that would be ‘waterfront ready’. Secondly, A great deal of the expertise the organisation believed it lacked was already there, sitting in different business units that each described the same work using different words. One division's "reliability engineer" was another's "asset integrity specialist." The skills existed. They were simply invisible, hidden behind inconsistent language, thereby reducing the investment required.
Once that capability became visible, internal deployment rose, the dependence on contractors fell, and investment could be aimed at the genuine gaps rather than the imagined ones. The lesson was almost embarrassingly simple. They did not lack talent. They lacked visibility.
They did not have a talent shortage. They had a visibility shortage. Most organisations do.
I have seen versions of this everywhere I have worked, from a national air traffic control provider struggling to objectively define digital and engineering requirements, to an international organisation serving dozens of member governments where the scarce capability was less technical, but the ability to broker agreement across competing national interests. In every case the organisation was richer in capability than it believed. It simply couldn't see what it had or what it needed.
Why this needs designing, not planning
None of this is solved by "better workforce planning" in the narrow sense. Better planning is necessary but nowhere near sufficient, because the failure is rarely in the plan itself. It is in the joins - between strategy and capability, between capability and finance, between the decision and the accountability for it.
That is why the method I now use with clients is built as a connected cycle rather than a linear plan. We diagnose the real problem and the quality of the evidence behind it; we envision the capability the strategy will genuinely require; we shape the choices and trade-offs; we implement through a real planning cycle rather than a slide; we grow the organisation's own ownership so it doesn't stay dependent on outside help; and we bake in adaptability, because the moment a strategy shifts, every assumption underneath it needs revisiting. The acronym is not the point. The point is that capability is a system, and systems fail at their weakest connection, not their weakest component.
The external evidence for all this is now hard to ignore, and it is worth being precise rather than waving vaguely at "the future of work." The World Economic Forum's 2025 Future of Jobs report estimates that 39% of workers' core skills will change by 2030, and that around 59% of the global workforce will need meaningful training within that window. Gartner's data shows the number of skills required for a single job rising by roughly 10% year on year, with a third of the skills listed in a job posting from only a few years ago already obsolete. IBM's research lands in the same territory - around 40% of the workforce needing to reskill over three years as AI reshapes work - while stressing that most roles will be augmented rather than eliminated.
You can argue with any single figure, and thoughtful people do. But the direction is not seriously in dispute: the half-life of capability is shrinking, and organisations that treat their workforce as a fixed stock of headcount rather than a designable, movable stock of capability are quietly accumulating risk they cannot see.
The shift that actually matters
The mindset change underneath all of this is simple to state and surprisingly hard to live. Headcount is no longer the primary planning currency. Capability is. Once you accept that, a lot of familiar arguments dissolve. The build-versus-buy debate becomes a build-versus-buy-versus-borrow-versus-automate-versus-redesign decision. The annual scrap over establishment numbers becomes a conversation about which capabilities are worth protecting and which are not.
And the role of HR changes too, which is where this series is heading. Because the organisations that will outperform over the next decade are not the ones that recruit the most people. They are the ones that make the best workforce decisions - earlier, with better evidence, and with the confidence that comes from having designed their capability rather than having stumbled into it. The strategy on the slide is the easy part. The capability to deliver it is the whole game.
Selected references
World Economic Forum, The Future of Jobs Report 2025
Gartner TalentNeuron skills data
IBM Institute for Business Value, Augmented Work for an Automated, AI-Driven World (2023).
Cello Consulting - Better workforce decisions. Better workforce capability. Better organisational performance.