A completed onboarding checklist shows what a new hire was exposed to, not what they can do. Competency-based onboarding starts from the other end. You list what the role must do, decide what evidence shows someone can do it, and build the first weeks around getting there. This guide is for heads of L&D, instructional designers and training managers. It covers five design decisions: map tasks and risk, diagnose prerequisites, build task practice, assess supervised readiness and support transfer. It promises no fixed ramp time, because readiness depends on the role, the person and the work. The case and rubric are illustrations: ask the manager of the role to review them before anyone is scored.
Quick facts
| Question | Short answer |
|---|---|
| What is it? | Onboarding organised around the tasks a role performs, not around a list of topics. |
| What comes first? | A task list for the role, with the risk of each task done alone. |
| How do you practise it? | Realistic cases and supervised practice, sequenced by task dependencies. |
| How do you assess it? | Evidence from representative tasks, not a completed checklist. |
| How do you check transfer? | Manager follow-up after real work exposure, then revise the journey. |
| What can it not fix? | An unclear role, missing tools and managers with no time to coach. |
1. Map role tasks and risk
List the tasks the role performs in its first months, in the words of the people who do them. Then, for each task, ask what happens if a new hire does it alone too early. A wrong filing label is a small risk. A wrong customer commitment, a safety step skipped or a data error that spreads is a bigger one.
That risk sets the supervision level. Agree with the manager what a new hire may do independently, what they may do with a check, and what they should only observe. Write it down. Without it, "ready" means whatever the busiest person at the time says it means.
2. Diagnose prerequisite knowledge
Not every hire needs the same content. A short diagnostic on the knowledge each task depends on, such as terms, rules and system steps, shows who needs what. A recall check confirms prerequisites and nothing more, so do not report it as competence. Target preparation to the observed gaps, and let people skip what they already know. Our learning gap diagnostic for L&D teams helps separate knowledge gaps from the context problems training cannot fix.
3. Build task practice
Sequence practice by how tasks depend on each other: a hire cannot practise a refund before they can find the order. Use realistic cases or supervised practice with feedback. Applying a rule to a fresh case and judging between two reasonable options are higher-order demands than recalling the rule, and the practice should match them. Our guide to matching learning activities to Bloom's taxonomy shows how to read the demand of a task.
Feedback should name the choice. "You answered before checking the account type" teaches more than "Be more careful". Live coaching adds most where two responses are both defensible. Asynchronous review is enough for checks against an agreed answer.
4. Assess supervised readiness
Define readiness through evidence from representative tasks. A completed onboarding checklist shows exposure, not competence. Pick the two or three tasks that carry the most risk or volume, ask the hire to perform them with an observer, and score against criteria the manager agreed beforehand.
Our guide to assessing judgement and problem solving in training covers anchors and how to check that two assessors score the same answer alike.
5. Support transfer after onboarding
Readiness on day 30 does not guarantee performance on day 60. Plan manager support after real work exposure: a short review of recent tasks, a place to ask questions and a trigger for extra practice when the same problem recurs. Revise the journey when recurring task problems appear. If three hires stumble on the same step, the fix is in the journey, not the hires.
A worked case with feedback and a retry
Illustrative. The instructional designer or training manager should validate the case and the answer criteria before use.
The case. You design onboarding for customer support agents. A new hire has completed the checklist but cannot resolve a routine billing query alone.
The task. Map the role's tasks to preparation, practice and supervised readiness. Explain your choices, cite the evidence you used and say what you still need to know.
A first attempt. "Add a billing module to the course and a quiz at the end." The reviewer asks which billing tasks matter most, what risk a wrong answer carries, how the hire will practise a real query and who will observe the first ones. The learner has no answer to any of them.
Feedback and retry. The reviewer points out that a module and a quiz would test recall again, which the hire already passed. The learner is asked for a new design.
A stronger attempt. The learner lists the five most common billing tasks and marks refunds as high risk. They add a short diagnostic on billing terms, then two realistic cases per task with feedback, sequenced from lookup to refund. Supervised readiness is two observed live queries per task, scored against agreed criteria, with refunds done only with a check until passed. A manager review follows in week six. They say what they still need: the real volume of each query type, who may approve refunds, and whether the billing tool is the cause of errors.
Why each response is defensible or incomplete. Judge against the approved criteria, not the reviewer's taste. The first attempt repeats a recall check and leaves independence undefined, so it counts as a critical error. The second ties practice, evidence and supervision to tasks and risk.
Score the design
Score each criterion from 0 to 2. Adapt it with the role's manager: this rubric is a proposed starting point, not a validated readiness standard.
| Criterion | 0: absent or unsupported | 1: partial, with omissions | 2: complete and justified |
|---|---|---|---|
| Task execution | Lists topics, not tasks. | Maps tasks but not risk or supervision. | Maps tasks, risk, practice and readiness evidence. |
| Reasoning | Gives no reason for the sequence. | States the sequence without alternatives. | Explains the choices, constraints and what is uncertain. |
| Boundaries | Lets hires work alone with no defined check. | Defines supervision for some tasks. | Defines supervised and independent work and escalation. |
Define critical errors separately, for example treating a completed checklist as proof of readiness. An overall score must never hide a critical failure.
To check that the design works, compare a baseline with an unseen follow-up task, and define the population, denominator and timing before you start. Measure task performance, the quality of the evidence collected and how suitable the resulting learning design proves. Look for concurrent changes, such as a new tool or a hiring surge, before you credit the onboarding. A better practice score is evidence about reasoning in practice, not a promise about ramp time.
Where interactive delivery helps
Interactive formats help where people should commit before they see what others chose. In a live session, a facilitator can describe the billing case, ask each new hire to type their next step, then show the spread before discussion. Self-paced delivery suits the diagnostic and the unseen follow-up. AhaSlides, an all-in-one engagement platform for teams and classrooms, supports interactive learning and both live and self-paced delivery. Check how you would move this case between the two against your own workflow before you rely on it.
What onboarding design will not fix
- An unclear role. If managers disagree on the tasks, no map will settle it.
- Missing tools or access. Practice cannot make up for a system a hire cannot use.
- Manager time. Supervised readiness needs an observer.
- Evidence limits. One design working once does not prove it works everywhere. Measure your own population.
Frequently asked questions
What is competency-based onboarding?
Onboarding built around the tasks a role performs, where readiness is shown by performing them, not by finishing a checklist.
How long should onboarding take?
It depends on the role and the person. Set readiness by evidence on representative tasks, not by a fixed number of days.
How do you assess a new hire's readiness?
Observe representative tasks, scored against criteria agreed beforehand, with critical errors defined separately.
Is a checklist enough?
A checklist shows what a hire was exposed to. It does not show what they can do.
Who should review the task map and rubric?
The manager of the role, and an experienced colleague who does the work, before anyone is scored.
Where to start
Pick one role, list its ten most common tasks, mark the three with the highest risk and write one case for the first. Agree the supervised-readiness evidence with the manager, run it with the next hire and revise after the first review.
To see how a case like this could run live or self-paced, explore AhaSlides.
