Why Most Skills Strategies Stall Before They Start Working

Ask any HR or workforce planning leader whether their organisation intends to become skills-first, and the answer is almost always yes. Ask when the architecture will be live, and the answer becomes considerably less precise.

That gap is structural, not cultural. Traditional engagements conclude at the point where the hardest work begins: designing a taxonomy that reflects the actual work being done, calibrating it against real workforce data, and keeping it current as roles change. Handing that back to an already-stretched internal team is what turns an eight-figure ambition into a shelved document.

The organisations that succeed treat skills as infrastructure rather than as a programme. Infrastructure has an owner, a data source, a refresh cycle, and a set of decisions it is expected to inform — hiring, internal mobility, reskilling investment, and workforce planning. A strategy document has none of those things.

The practical test is simple: six months after the engagement ends, can a talent acquisition lead open a system and see which internal candidates are two adjacent skills away from an open role? If not, what was delivered was a plan, not a capability.