Role- and Skill-Based Learning Pathways in Saudi Academies

Begin with the role, not the catalogue

Traditional pathways often begin with a list of courses and then attempt to assign them to jobs. Role- and skill-based learning pathways reverse that logic. They start with the role’s purpose and outputs, identify critical tasks, decisions and high-impact errors, and then derive the required knowledge, skills, behaviours and evidence. Content becomes a means of building capability rather than the centre of the design.

The World Economic Forum’s Future of Jobs Report 2025 estimates that 59 out of every 100 workers globally will need training by 2030, and identifies technological literacy among the skills growing fastest in importance. These are global findings, not Saudi labour-market measures. Saudi Arabia’s Human Capability Development Program also places lifelong learning and alignment with future needs at the heart of human-capability development. Neither source can define an organization’s skill requirements automatically, but together they reinforce the need for a living role map rather than a static catalogue.

The better starting question is not “Which courses do we own?” It is “What must a person in this role be able to deliver, at what level, and what evidence would make the organization confident that the person is ready?”

An eight-step design chain

1. Define the role and context

Describe the role’s purpose, customer, location, tools, authority and expected experience. Do not rely on the job title alone; the same title may carry different responsibilities across business units or sites. Clarify whether the work is office-based or frontline, individual or supervisory, and identify the risks surrounding performance.

2. Define the outputs

What does the role produce, for whom and to what standard? The output might be an analysis, project plan, service, decision, safely operated process or capable team. Write it in a form that can be inspected, then specify relevant expectations for quality, time, accuracy, compliance or user experience.

3. Analyse tasks and decisions

Select critical and recurring work, including exceptions that require professional judgement. Ask experienced performers about the mistakes with the greatest consequences and the situations that distinguish a ready employee from one who needs support. Avoid turning every procedural step into a separate skill; group tasks that depend on the same capability.

4. Derive skills, knowledge and behaviours

For each task, define what employees need to know, do and use, plus the behaviours that preserve quality. Separate knowledge and skill gaps from environmental barriers. An employee may understand the requirement but be blocked by access, an unstable tool or a conflicting process.

5. Define proficiency levels

Distinguish a beginner working with support, an independent performer handling routine cases, an advanced performer managing exceptions and an expert who shapes standards or develops others. Connect each level to conditions and evidence. Years of experience alone are not proof of capability.

6. Diagnose the baseline

Use more than one source: a short assessment, simulated situation, work sample, manager input and relevant performance data. Do not rely on self-rating alone. The purpose is not to label employees; it is to identify the gap worth addressing and the shortest credible route to close it.

7. Design the journey

Match the channel to the gap: self-paced learning for concepts, scenarios for decisions, a lab for tools, workplace practice for performance and job aids at the moment of need. Give learners an opportunity to attempt, receive feedback and improve. A pathway is not an ordered list of links; it is a sequence that moves a person from baseline to defined performance.

8. Specify readiness evidence

Before launch, agree the work sample, simulation, project or manager observation that will demonstrate capability. Define who assesses it, the standard they use, how reassessment works and how differences between assessors will be calibrated. A certificate should only close the pathway when it represents meaningful evidence.

Write skills so they can be observed

Statements such as “understands data” or “has a digital mindset” are too broad to support fair assessment or pathway design. Use a more precise structure: action, object, context and standard. For example: “Analyses the service performance dashboard, checks input quality, interprets the variance and recommends an action within delegated authority.”

Then add task conditions. Is the work completed with full or incomplete data? Alone or with a team? What is the acceptable time? Which errors are unacceptable? This definition guides channel choice. Terminology may be learned independently, a decision tested in a scenario, a tool practised safely and independence demonstrated through real work.

Avoid turning broad attributes into personality judgements. If collaboration is a skill, define visible behaviour: sharing critical information on time, documenting a decision or resolving a conflict through an agreed process. Observable definitions reduce bias and make feedback more useful.

Proficiency levels need different evidence

A beginner may explain a process and perform it with support. An independent employee completes a routine case to standard. An advanced performer manages exceptions and trade-offs. An expert shapes standards, reviews others or transfers knowledge. Not every skill requires four levels; the important point is that each distinction has operational meaning.

Evidence should change with the level. A guided simulation may suit a beginner, a work sample an independent performer, a complex case an advanced performer, and a standard review or coached transfer an expert. Employees can then see what progression means, while managers can provide the next appropriate opportunity instead of assigning the same content again.

Build a common core with intelligent branches

Corporate academies need consistency, but consistency does not mean one pathway. Use a flexible architecture:

1. A common core for policy, concepts, terminology and minimum risk requirements.

2. Role branches focused on authentic tasks, decisions and cases.

3. Short remediation for a specific diagnosed gap rather than repeating the whole pathway.

4. An advanced challenge or project for learners who pass the foundation.

5. Job aids, expert communities and support at the point of work.

6. Re-certification when a system, policy or risk changes—not simply because a year has passed.

This structure prevents experienced employees from sitting through introductory material and beginners from attempting work without the foundation. It also lowers maintenance cost because the common core is managed once while examples and practice change by role.

Critical pathways and exploratory learning

A corporate academy should not become a closed network of mandatory routes. Distinguish critical pathways tied to readiness, safety or compliance from exploratory content that helps employees grow or understand adjacent fields. A critical pathway has an audience rule, assignment logic, standard and evidence. Exploratory learning creates room for choice without implying that content consumption automatically qualifies a person for a new role.

Self-enrolment can signal interest. When an employee seeks mobility, connect that interest to a diagnostic, project or supervised opportunity. The academy keeps its openness while avoiding the false equivalence between viewing material and job readiness.

Connect the manager and workplace evidence

Before the pathway, the manager identifies a real application task and safe boundaries. During it, the manager protects time and provides a tool, data or access to an expert. Afterwards, the manager reviews a work sample or observes behaviour using a published checklist. The assessment should address evidence against a standard, not personality or general impressions.

Where no application opportunity exists, record that fact rather than labelling the employee uncommitted. A readiness dashboard must separate capability from opportunity. Someone may acquire a skill but receive no data, task or permission to use it during the measurement window.

Saudi evidence from pathway and choice data

An internal SkillUp MENA case study with Al-Ayouni Investment and Contracting Company records 68,138 self-enrolments, 119,655 total enrolments and 77.9% completion across critical pathways. The client name and figures require explicit approval before external publication.

These are access, choice and completion indicators from one Saudi case. They do not show whether every enrolment addressed a role gap or created workplace impact. Their useful lesson is that guided pathways and learner choice can coexist. The next level of evidence requires diagnostics, mastery assessment, workplace tasks and role-readiness measures.

A role-readiness dashboard

Start with measures that lead to a decision:

1. The share of the role population completing diagnostics, segmented by starting level.

2. The most frequent and consequential gaps across critical tasks.

3. Mastery in a consistent assessment or simulation, not completion alone.

4. Accepted workplace evidence and the attempts required to reach the standard.

5. Time to independence and opportunities managers provided for application.

6. Skills whose standard has changed or become obsolete, triggering pathway updates.

Start with one role and one pathway. Test the definitions, diagnostic, experience and evidence with real experts, users and managers. Once the chain from task to measurement is clear, expand to a role family and reuse the core. Success is not a larger number of pathways; it is readiness that people can understand and demonstrate.

Next step

Start a digital academy readiness assessment with SkillUp MENA experts to build role maps, skill definitions and learning pathways that prove readiness rather than simply recording content completion.