Why It's Needed: the gap between knowing and doing

The cost of doing nothing

Three constraints fall on one bill.
Fix one, the other two keep charging you.

$0B

Relevance

Spent on workforce learning globally each year, most not built for the role it's aimed at.

Bersin / Deloitte

<0%

Accessibility

Less than 30% of that spend shows up as measurable change in how people work.

Bersin research; Kirkpatrick Level 3

0 min

Reinforcement

A week is all most employees have left to learn. Gone by Friday.

Bersin research

Every system's throughput is limited by its weakest constraint. Remove one without removing the others, and you haven't lifted throughput. You've just moved the bottleneck.
Goldratt, Theory of Constraints, 1984

How it gets fought today

Six systems. Five vendors. One spreadsheet.A quarter of your year.

That's what building one academy costs most capability teams today. Alignment in slides that are out of date by the second meeting. Frameworks hand-built in spreadsheets. Content sourced across five tools with no through-line. A launch email, a nudge programme nobody runs, and a dashboard that shows completions but can't answer the question the CEO actually asked.

The ritual isn't a failure of effort. It's a failure of distance.

Everything the team needs exists somewhere in the business. It just never reaches the people doing the work, in their language, at the moment it matters. That distance is the whole problem, and it is closable.

Fixing the mechanism isn't the same as fixing the rollout

The system worked.
The rollout didn't.

Get relevance, accessibility and reinforcement right and you've built something that works. Whether it gets used depends on three separate things going right, none of which the system itself can do for you.

Someone has to go first

If leadership treats it as another rollout, so does everyone else. Adoption starts the moment one visible pilot shows a real result, not the moment the licence is signed.

It has to stop belonging to one team

The most common failure isn't resistance, it's indifference. If only the project team can explain why it matters, only the project team will still be using it in six months.

It has to survive you looking away

Every launch works while someone's pushing it. The real test is week twelve, once the attention has moved on and nobody's checking whether it's still happening.

This is the difference between a system that works and one that's still being used a year later.

Client spotlight

Building capability at scale
with PKF Australia

PKF Australia asked for outcomes, not optics. Branded as Luca Learning, their instance pulls content from multiple sources into personalised journeys, builds the right skills across offices and role levels, and gives every person a digital Companion for daily guidance. Around 800 people today, expanding regionally in phases, with engagement and sentiment tracked live in the Builder console.

Lana WeldonNational COO

Alex McAskillNat. Head of Marketing Technology

Chantel DippleNat. Director Quality Management

Kelly ViljoenNat. Digital Marketing Specialist

Erin ViljoenNat. Marketing Specialist

From cost centre to capability engine

Firm standards captured once, reused across every journey. Leaders see progress, sentiment and skill lift across divisions, not completion rates. Every activity logged, audit-ready.

What changed at PKF, in their language

Trust is earned, then documented.

Built for business use, with safeguards for access, customer data and secure handling across the platform. Our diligence standards cover how we protect information, manage risk and support enterprise requirements.

See our standards