Digital adoption fails when organisations assume people will “figure it out” — or bolt training on at the end. Capability needs to be designed alongside the tool: role impacts, decision rights, new failure modes, and support in the flow of work. WHY THIS MATTERS Digital tools create new ways to fail if capability isn’t designed alongside them. The result is low adoption, inconsistent usage, and lost value—despite good technology. WHAT THIS MEANS FOR YOU Treat digital rollout

Competency models often die in binders because they’re built for consistency and governance — not usability. The organisations that win make competencies actionable: role clarity, proficiency levels people recognise, and pathways tied to real work, not abstract behaviours. WHY THIS MATTERS When competency frameworks aren’t usable, they become shelfware—wasting time and budget while leaving role clarity, progression, and deployment decisions inconsistent. WHAT THIS MEANS FOR Y

Training can raise knowledge, but performance changes when leaders coach in the flow of work: noticing drift, correcting weak signals, reinforcing standards, and building judgment over time. In many organisations, coaching is seen as optional — and that’s why capability doesn’t stick. WHY THIS MATTERS Without coaching, training decays fast. Capability doesn’t embed, standards drift, and performance varies by team and leader — even when everyone attended the same course. WHAT

Most organisations still treat workforce strategy as a numbers game – FTEs, org charts, vacancy lists. But the real constraint is skills, not people. Leading research shows that skills-based organisations are better at retention, agility and responding to disruption, and that “skills-first” workforce models are fast becoming a strategic imperative, not an HR trend. What this means for you   Workforce strategy has to start with a skills map , not a structure chart.  Competency