Plan the Onboarding
When To Use
Ramp-up takes months and stakeholders blame the talent. Meanwhile the new hires finished every module on the list and still hand the awkward cases to whoever sits nearest. Use this to plan the job-skill part of onboarding for one role. It answers: which real tasks must a new hire handle, in what order, with whom beside them, and how does anyone know they are ready for each one?
When Not To Use
If you are sequencing modules for several roles, run Map the Curriculum. If an established employee needs a manager's support around one course, Brief the Managers is enough. This skill is one role's first weeks.
Inputs
- The role and its real tasks, with the exceptions that trip people up (your task breakdown or expert notes, if they exist)
- The onboarding content you have today (modules, policies, system access steps), who could be a buddy, by role, and how long the path should run
If you have none of this, I start from the role and five tasks you list from memory and mark the output as a first draft.
Approach
The four Cs of onboarding from the SHRM Foundation's public guideline (compliance, clarification, culture, connection) for the frame, and practice on real problems (Merrill, 2002) for the job-skill part. The guideline covers onboarding broadly, so the tasks carry the plan and the four Cs check that nothing is missing. The failure this prevents: first weeks of policy reading and system tours, every box ticked, then a first live exception met alone, with the buddy on leave and the answer in a module from day two.
Workflow
- Ask up to three questions: which tasks a new hire must handle alone and by when, which exceptions cause the most trouble, and who does the work well today, by role.
- List the real tasks and order them from simpler to harder: the usual case, then the common exceptions, then the rare costly ones. Take them from the task breakdown if you have it. A task nobody can describe yet goes back to the expert.
- Lay out the weeks over a length you set. Each week names the tasks in focus, the practice that comes before the live task (a scenario from real cases), and which of the four Cs it covers. Compliance sits where the work needs it, not all in week one.
- Place clarification and culture in the weeks where the tasks show them: what "good" looks like in this role, said plainly, at the moment the new hire can see it.
- Plan connection: buddy sessions at a cadence you set, each tied to a task that week. Watch, then do together, then do while the buddy watches. Booked in the calendar, never "when there is time".
- Set sign-off per task: the new hire does it with a person beside them, who confirms readiness to do it alone or names what to practise next. Never a quiz, never a score, and no new hire is compared with another.
- List compliance and policy items apart. What is required, and by when: check with a qualified adviser.
Output Format
# Onboarding Path
Role: [role] | Length: [weeks you set] | Path owner: [role] | Buddy: [role]
## The real tasks, simpler to harder
| No. | Task | Usual case, common exception or rare costly one | Week it is first done live | Source |
|---|---|---|---|---|
| [1] | [task] | [type] | [week] | [task breakdown / expert / "ask the expert"] |
## Week by week
| Week | Tasks in focus | Practice before the live task | Four Cs covered | Buddy session (date, task, watch / together / observed) |
|---|---|---|---|---|
| [1] | [tasks] | [scenario from a real case] | [compliance / clarification / culture / connection] | [session] |
## Sign-off by doing the task
| Task | Done with | Date | Ready to do alone, or what to practise next |
|---|---|---|---|
| [task] | [role] | [date] | [ready / practise ...] |
## Content with no task, and compliance items
Cut or moved to reference: [module or document, and the call]
Compliance and policy items: [policy or rule, week, owner], each one marked "check with a qualified adviser"
## Decision
[Hiring manager name] and [L&D lead name] approve the task order, the buddy time and who signs off each task by [date].
Done When
- Every task sits in a week, ordered from simpler to harder, exceptions included
- Every week has practice before the live task and a booked buddy session
- Each of the four Cs appears somewhere in the path
- Every sign-off is done by doing the task with a person, and no column holds a score
Quality Bar
- Modules serve tasks; a module tied to no task is cut or moved to reference
- Lengths and cadences are yours; the path states no benchmark ramp-up time
- A new hire who is not ready yet gets "what to practise next", in words, from the person beside them
- Legal and policy items say "check with a qualified adviser"
- Sign-off is readiness for a task, agreed with a person beside the new hire; it never grades or ranks them.
Next
Run ldg-write-the-feedback-form (Write the Feedback Form) to start measuring what the programme gives people.
About the makers
This pack is made by 90n (90n.ai): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).
1---2name: ldg-plan-the-onboarding3description: Plans one role's first weeks around the real work, with a week-by-week path built on the real tasks from simpler to harder, practice before each live task, buddy sessions tied to tasks, and sign-off by doing the task with a person. Use for "run ldg-plan-the-onboarding", "onboarding training", "training plan for new employee", "new hire training plan", "30 60 90 day plan", "onboarding program", "new hires are not ready", "onboarding buddy sessions", part of The Complete Claude Guide for L&D Pack by 90n.4metadata:5 source: https://skillmd.com/skills/polar-bear-org/ldg-plan-the-onboarding6---78# Plan the Onboarding910## When To Use11Ramp-up takes months and stakeholders blame the talent. Meanwhile the new hires finished every module on the list and still hand the awkward cases to whoever sits nearest. Use this to plan the job-skill part of onboarding for one role. It answers: which real tasks must a new hire handle, in what order, with whom beside them, and how does anyone know they are ready for each one?1213## When Not To Use14If you are sequencing modules for several roles, run Map the Curriculum. If an established employee needs a manager's support around one course, Brief the Managers is enough. This skill is one role's first weeks.1516## Inputs17- The role and its real tasks, with the exceptions that trip people up (your task breakdown or expert notes, if they exist)18- The onboarding content you have today (modules, policies, system access steps), who could be a buddy, by role, and how long the path should run19If you have none of this, I start from the role and five tasks you list from memory and mark the output as a first draft.2021## Approach22The four Cs of onboarding from the SHRM Foundation's public guideline (compliance, clarification, culture, connection) for the frame, and practice on real problems (Merrill, 2002) for the job-skill part. The guideline covers onboarding broadly, so the tasks carry the plan and the four Cs check that nothing is missing. The failure this prevents: first weeks of policy reading and system tours, every box ticked, then a first live exception met alone, with the buddy on leave and the answer in a module from day two.2324## Workflow251. Ask up to three questions: which tasks a new hire must handle alone and by when, which exceptions cause the most trouble, and who does the work well today, by role.262. List the real tasks and order them from simpler to harder: the usual case, then the common exceptions, then the rare costly ones. Take them from the task breakdown if you have it. A task nobody can describe yet goes back to the expert.273. Lay out the weeks over a length you set. Each week names the tasks in focus, the practice that comes before the live task (a scenario from real cases), and which of the four Cs it covers. Compliance sits where the work needs it, not all in week one.284. Place clarification and culture in the weeks where the tasks show them: what "good" looks like in this role, said plainly, at the moment the new hire can see it.295. Plan connection: buddy sessions at a cadence you set, each tied to a task that week. Watch, then do together, then do while the buddy watches. Booked in the calendar, never "when there is time".306. Set sign-off per task: the new hire does it with a person beside them, who confirms readiness to do it alone or names what to practise next. Never a quiz, never a score, and no new hire is compared with another.317. List compliance and policy items apart. What is required, and by when: check with a qualified adviser.3233## Output Format34```markdown35# Onboarding Path36Role: [role] | Length: [weeks you set] | Path owner: [role] | Buddy: [role]37## The real tasks, simpler to harder38| No. | Task | Usual case, common exception or rare costly one | Week it is first done live | Source |39|---|---|---|---|---|40| [1] | [task] | [type] | [week] | [task breakdown / expert / "ask the expert"] |41## Week by week42| Week | Tasks in focus | Practice before the live task | Four Cs covered | Buddy session (date, task, watch / together / observed) |43|---|---|---|---|---|44| [1] | [tasks] | [scenario from a real case] | [compliance / clarification / culture / connection] | [session] |45## Sign-off by doing the task46| Task | Done with | Date | Ready to do alone, or what to practise next |47|---|---|---|---|48| [task] | [role] | [date] | [ready / practise ...] |49## Content with no task, and compliance items50Cut or moved to reference: [module or document, and the call]51Compliance and policy items: [policy or rule, week, owner], each one marked "check with a qualified adviser"52## Decision53[Hiring manager name] and [L&D lead name] approve the task order, the buddy time and who signs off each task by [date].54```5556## Done When57- Every task sits in a week, ordered from simpler to harder, exceptions included58- Every week has practice before the live task and a booked buddy session59- Each of the four Cs appears somewhere in the path60- Every sign-off is done by doing the task with a person, and no column holds a score6162## Quality Bar63- Modules serve tasks; a module tied to no task is cut or moved to reference64- Lengths and cadences are yours; the path states no benchmark ramp-up time65- A new hire who is not ready yet gets "what to practise next", in words, from the person beside them66- Legal and policy items say "check with a qualified adviser"67- Sign-off is readiness for a task, agreed with a person beside the new hire; it never grades or ranks them.6869## Next70Run ldg-write-the-feedback-form (Write the Feedback Form) to start measuring what the programme gives people.7172## About the makers7374This pack is made by 90n ([90n.ai](https://90n.ai)): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).