Choreography: onboarding that scales
The onboarding you rebuild from scratch with every hire becomes a role-personalized track that almost fires itself. But the human bond of the first day never gets automated.
Every time a cycle closes, you build the same report again: pull the numbers, write the summary, format it, send it. The structure never changes, only the period's content changes. And even so you rebuild the whole material, from scratch, every time, as if it were the first.
Every month-end close you build the same variance report: pull the budgeted, the actual, write the summary for the board. The structure is always the same, only the month's numbers change. Even so you redo the whole table by hand, month after month, spending the same expensive hour on an assembly that should already be ready.
Every new service-provider contract you build from scratch: review clause by clause, adjust the term, adjust the value. The contract's anatomy is always the same, only the client and the scope change. And you rebuild the whole document again, every time, when you could have started from a ready-made base.
Every new campaign you build the same brief: audience, message, channels, posting calendar. The brief's structure never changes, only the product and the season change. Even so you write the whole document again for every campaign, spending hours rewriting what you'd already solved in the previous one.
Every new hire is the same scramble. You open a blank document and build onboarding from scratch: write the first week's schedule, gather training materials scattered across three different folders, schedule the introductions with each area, write the welcome message. Two hires in the same month means doing this work twice, from the start. And the worst part is the structure never changes: day 1 is always system access and welcome, week 1 is always team and culture context, week 2 is always the first small deliverable so the person feels progress. Only the role and area change the content inside those boxes. Think about it: if onboarding always has the same anatomy by role, why do you rebuild the whole material every time someone new joins? The answer is that nobody showed you the ladder that turns this into a system, while keeping one thing safe: the human bond of the first day, the manager welcoming them live, the coffee, the sincere question of "how are you feeling", that piece never climbs up into any automation.
Every sprint closes and you build the same product report: activation, retention, roadmap status. The structure is always the same, only the sprint's data changes. Even so you rebuild everything by hand, sprint after sprint, when the format has been solved for a long time.
Every week you build the same forecast: pull the CRM, count the deals by stage, project the close. The format never changes, only the week's deals change. Even so you redo the whole spreadsheet, week after week, spending the same hour on a structure that should already run on its own.
Every month you build the same operational report: SLA, volume, cost per delivery. The structure never changes, only the period's numbers change. Even so you rebuild the whole dashboard, month after month, as if each cycle required reinventing the format.
Every quarter you build the same controls report for the risk committee: audit status, exceptions, incidents. The format is always the same, only the period's findings change. Even so you rebuild the whole report, quarter after quarter, when the anatomy has been set for years.
Every sprint you build the same engineering report: deploys, incidents, test coverage. The structure repeats every time, only the cycle's numbers change. Even so you rebuild everything by hand, as if the previous report didn't exist to copy the shape from.
Every month you build the same UX report: completion rates, research findings, accessibility score. The format never changes, only the period's data changes. Even so you rebuild the whole structure, month after month, spending expensive time on an assembly that's always the same.
Every quarter you build the same deck for the board: performance by unit, OKR status, competitive scan. The deck's anatomy never changes, only the numbers and market moves change. Even so you rebuild the whole deck from scratch, every time, as if you still didn't know the recipe.
Think about something that hurts: every time someone new joins the team, you sit down and build onboarding almost from scratch. Write the schedule again, dig up the training material from the usual folders, schedule the introductions, write the welcome message with care, again. Hired three people this month? You did that work three times, from the start, as if each one were the company's very first hire. And the strange part is onboarding's structure never changes: the first day is always access and welcome, the first week is always team context, the second week is always the first small deliverable so the person feels like they're already contributing. Only the role changes the content inside those boxes.
The core idea of this lesson. All recurring onboarding is, in fact, a system disguised as a task. You climb a ladder: from by hand, to a fixed template by role, to a workflow that assembles the track on its own, up to onboarding that almost fires itself as soon as the ATS marks "hired". But there's one rung you never automate: the first day's human bond. AI assembles the content and the schedule; the welcome stays yours, always.
01Why you're still rebuilding everything from scratch
Let's call it what it is. Onboarding has three parts, and they don't have the same value.
- The structure. The same sequence, in the same order, for any role: day 1 is access and welcome, week 1 is team context, week 2 is the first small deliverable. This doesn't change from hire to hire.
- The content. The specific training material, the names of the team's people, that role's tools. This changes by area and by opening, but follows a pattern within each role.
- The human bond. The manager welcoming them live, the first day's coffee, the sincere question about how the person is feeling in the first week. This is yours, and it's the part that makes the new person feel like they joined a team, not a system.
When you rebuild everything by hand, your expensive time goes to the structure, which is the part that repeats the most and needs the least of your attention. The ladder that follows pushes the structure and the content to the machine, and frees you up for the human bond, which is irreplaceable.
What shifts in your time:
02The ladder: four rungs from by hand to one click
Think of a four-rung ladder, and you climb one at a time, at your own pace. Rung one is where you are today: building everything by hand, hire after hire. The next three rungs are what comes in the next two sections.
The important thing is to see the whole picture: the assembly effort drops with every rung you climb, but the human bond always stays at the top, untouched. Automation grows below it; the welcome never comes down into it.
03Rungs two and three: the template by role and the workflow
Rung two is the template by role. Here you stop writing the schedule from scratch for every hire. You write, just once, a fixed template for each common role at the company: the 30, 60, and 90-day schedule for the salesperson, for the analyst, for the developer. Each template holds, in writing, the sequence of milestones, the right training materials, the introductions that need to happen and in what order. It's like having a house blueprint ready: you adjust the finishes for the resident, the blueprint stays the same. This jump alone already cuts a good chunk of the hours you used to spend rebuilding the whole structure every time.
Rung three is the workflow. Now you climb one more rung. Instead of you opening the template and filling it in by hand, AI reads the new hire's role and area, from the ATS or the openings spreadsheet, and assembles the personalized track on its own: automatically scheduling the right introductions, gathering that team's training material, drafting the welcome message with the right name and role. You go from being the assembler to being the reviewer: the track arrives ready in front of you, and your job becomes checking that everything's right and adjusting whatever's specific to that person.
04Rung four: almost one click, never one click, and what never gets automated
Rung four is the top of the ladder. Here the workflow no longer waits for you to trigger it: as soon as the ATS marks the opening as "hired", the track already fires on its own, with the schedule assembled, the material gathered, and the introductions scheduled, waiting only for your review before it goes out.
Notice the name: almost one click. Not one click. Because there's a part of onboarding that no automation touches, nor should it.
The rule is clear: you automate the content and the schedule, never the human bond. The manager welcoming the person live, the first coffee, the sincere conversation about how the person's feeling that week, that's irreplaceable. An onboarding with a flawless track but no such contact turns cold, and the new person feels exactly that: they feel like they joined a system, not a team. In HR, this distinction isn't a detail, it's what decides whether the person stays excited or already starts second-guessing the choice they made.
05The math that justifies the ladder
Now the frame that makes this obvious. Take your onboarding and calculate how much time it costs you per hire: building the schedule, digging up material, scheduling introductions, writing the message. If it's three hours per hire and you hire twenty people a year, that's sixty hours, almost two weeks of work, spent rebuilding the same structure over and over.
Turning this into a system doesn't give you back everything, because you still review the track and, most importantly, you still do the human bond live. But it gives you back the whole assembly, which was the bulk of the time. What's left for you is exactly the part that makes a difference to whoever just arrived: being genuinely present on the first day. Notice the pattern, because it's bigger than this onboarding: every task you repeat by role is a system waiting to be built, as long as you protect the piece only a person can do.
Do it now
Take the role you hire for most at the company, your real task or another one (salesperson, analyst, support agent). Describe in writing the fixed structure of this onboarding, as if you were explaining it for someone else to build in your place: what happens on day 1, what happens in week 1, what happens in week 2, which materials and introductions always come in. This is your rung two, the template by role.
Now mark the red line: the exact moment the human bond needs to happen with zero AI intermediation, the manager welcoming them live, the coffee, the first week's conversation. Write this line prominently at the top of your template, so you never forget it doesn't climb up into any automation.
Practice
1. What's the correct sequence of the ladder for turning onboarding into a system?
2. At the highest rung, when the track already fires as soon as the hire is confirmed, what do you never automate?
3. Why is recurring onboarding a good candidate for turning into a system?
</content>
For the board
On the reworkthree hires in a month is three onboardings from scratch, as if each one were the first.
On the laddera template per role, then the workflow, and the check stays at the top.
On the limityou automate the content and the schedule. Never the welcome.
Thanks for the feedback. It helps sharpen the next lesson.