SkillBridger logo SkillBridger
Foundations

How the capability journey works

The six-stage cycle (Assess, Identify, Develop, Apply, Verify, Grow) that turns training into verified, measurable workforce capability.

4 min read For everyone Updated

Most organizations already spend money on training. What they rarely have is proof that the training changed what people can do at work. SkillBridger is built around one continuous capability-development cycle so that every course, project and manager review ties back to a specific skill and a specific job role.

Why a cycle instead of a course list

A course catalogue answers "what training exists?". A capability cycle answers the questions leaders actually ask:

  • Which skills does each role need, and at what level?
  • Where are our people today, based on evidence rather than opinion?
  • Which development activity will close which gap?
  • Did the person apply the skill at work, and who confirmed it?
  • How has our capability changed over the last year?

Because each stage feeds the next, gaps are never identified and then forgotten, and training is never completed without a check that it was applied.

Stage 1: Assess

Employees record their skills, proficiency levels and supporting evidence such as certificates or work samples, and complete a self-assessment. Every new rating starts as Self-declared. A manager or HR then reviews and validates it.

Stage 2: Identify

The system compares each employee's verified proficiency with the requirements of their job role. Each gap is classified as high, medium or low priority, so HR and L&D teams can see where development is most urgent across a team, a department or the whole organization.

Stage 3: Develop

The employee builds a development plan with a career objective, target skills, learning activities and target dates. They can browse training mapped to their gap skills and submit a training request. Managers and HR approve, reject or request a modification.

Stage 4: Apply

Completing a course is not the finish line. The employee demonstrates the skill through a practical project, assignment or work sample linked to the skill being developed.

Stage 5: Verify

A manager, assessment or approved verifier validates the demonstrated capability. Verification records who confirmed it and when.

Stage 6: Grow

The Employee Skill Growth Ledger records the change: the date, the previous and new level, the evidence and the verifier. Earlier entries are never overwritten, so the organization keeps a full, auditable history. The next priority skills are then identified and the cycle starts again.

Capability stages and evidence levels

Each skill moves through recognisable stages:

  • Entry: the skill is recorded.
  • Acquired: learning has been completed.
  • Applied: the skill has been used in real work.
  • Verified: a manager or assessment has confirmed it.
  • Advanced: the person has progressed to a higher level.

Evidence strengthens in the same direction: Claimed → Learned → Applied → Verified.

Where capability programmes usually break

In practice the cycle rarely fails at Assess or Develop. It fails in the handovers:

  • Identify → Develop. Gap reports get produced and then sit unused because no one owns turning a gap into a dated plan. Fix: no gap above medium priority without a plan owner and a target date within the same review cycle.
  • Develop → Apply. The forgetting curve is brutal: without practice, much of what is learned on a course fades within days. If the employee has no real task to use the skill on within two to four weeks, most of the training budget leaks away. Plan the application task before approving the course.
  • Apply → Verify. Managers are busy, so verification queues grow. Set a service level (for example, ten working days) and treat each manager's verification backlog as a leadership metric.

The 70-20-10 lens, used carefully

The widely quoted 70-20-10 heuristic (roughly 70% of development from on-the-job experience, 20% from other people, 10% from formal courses) is not a law, and the research behind it is thin. It is still a useful corrective: if every development plan in your organization says "attend a course", you are ignoring the main sources of growth. The Apply stage is where that 70% gets captured as evidence.

What "good" looks like after a year

  • Most employees have their core role skills verified, not just self-declared.
  • High-priority gaps trend downward, department by department.
  • Each approved training request can be traced to a gap, an application task and a verification decision.
  • Managers discuss the Growth Ledger in performance conversations instead of relying on memory.

Frequently asked questions

What is a capability development cycle?

It is a repeatable process that links skills assessment, gap analysis, learning, on-the-job application and verification, so that development is measured by changed capability rather than by course attendance alone.

How is this different from a learning management system?

A learning management system mainly delivers and tracks courses. SkillBridger focuses on the whole journey around learning: role requirements, verified skill levels, gap analysis, training requests, applied evidence and a permanent record of growth.

Who takes part in the cycle?

Employees, managers and HR or L&D teams within an organization, training providers who publish skill-mapped courses, and a platform administrator who oversees quality and access.

How often should the cycle run?

Continuously. Many organizations align a full review with their performance or planning calendar, but employees can add evidence and request verification at any time.

Try it with your own team

Set role requirements, verify skills and track growth in SkillBridger.

Get started