A People team can standardize the structure of onboarding. It can't write the role context for every function, and shouldn't try. Split onboarding into three layers: company, team and role. The People team owns the company layer. The other two already exist in each function's tools, so they get assembled from there and approved by the hiring manager.
Who owns role-specific onboarding?
On paper, the People team. In practice, nobody.
The People team owns the program: the checklist, the schedule, the 30-60-90 template, the welcome session. All of that is real work and most companies do it well.
The role-specific part is different. Why the sales team stopped discounting last quarter. Which service an engineer shouldn't touch without asking. What was promised to the customer a new CSM is about to inherit. A People team of four can't know that for sales, engineering, product, support and finance. The people who do know are the managers.
So the template has a section called "role context", and the section has a note that says the manager will fill it in. The template has been waiting patiently ever since.
Only 12% of employees strongly agree their organization does a great job of onboarding new employees (Gallup). That isn't a verdict on the People team's effort. It's what happens when the program is finished and the context isn't.
What should standardizing mean, and what shouldn't it?
Standardize the container. Don't try to standardize the contents.
Things that should be the same for every new hire:
- The structure: what they receive, in what order, and when.
- The checklist: accounts, equipment, policies, sign-offs.
- The standard: every new hire gets written context before day one, and a manager has approved it.
Things that can't be the same:
- What a new engineer needs to know about the codebase.
- What a new AE needs to know about the territory.
- What a new product manager needs to know about the last three roadmap arguments.
The usual response to "onboarding is inconsistent across functions" is a better template. A template standardizes the questions. It has never once supplied the answers. Firstweek vs. an onboarding checklist makes the same point about checklists: keep it, and add what it can't hold.
What are the three layers: company, team and role?
- Company. What the company sells and to whom, how it's organized, how decisions get made, what changed recently. This is the same for everyone, and the People team can own it outright.
- Team. Who is on the team, who owns what, how the team works, and the decisions that explain why. This differs by function and changes every quarter.
- Role. The accounts, systems, projects or customers this one person is inheriting, with the history behind each. This differs for every hire.
Most onboarding programs are strong on layer one and thin on the other two. That matches who writes what. The People team writes the company layer once and keeps it current. Layers two and three would have to be rewritten for each team and each hire, by managers, during the same weeks they're covering an open seat.
29% of new hires say they feel fully prepared and supported to excel in their role after their onboarding experience (Gallup, 2021). "In their role" is the part to notice. That's layers two and three.
Where does each layer already live?
The useful news is that none of the three needs to be written from scratch.
- Company layer: the handbook, the all-hands decks, the Confluence or Google Drive pages the People team already maintains.
- Team layer: the team's Slack channels, its Jira board, its Confluence space, the CRM. Who answers what, who owns what, and the threads where things were decided.
- Role layer: the records this person inherits. Accounts and opportunities in the CRM, tickets and repositories for an engineer, the project threads for a product manager.
It's all written down. It was written by the people doing the work, at the time, for each other. What's missing is anyone reading it in order and writing it up for one new hire. That's a research project per hire, which is why it lands on nobody.
Meanwhile each new hire is on payroll from day one, asking for it one question at a time. The onboarding cost calculator shows what that costs with your own numbers.
What does the People team keep, and what does a manager approve?
A division of labor that works at 150 to 500 people:
- The People team keeps the program, the checklist, the company layer and the standard. They also keep the one rule that makes it consistent: nothing reaches a new hire unapproved.
- The hiring manager approves the team and role layers. Approves, not writes. Reading a draft and correcting two things is a job a manager will do. Writing six pages from a blank template is a job they've been not doing for years.
- Something has to draft it. By hand, that's the People team chasing managers. The free onboarding document template is a reasonable place to start if you go that way.
Firstweek does the drafting. It reads the tools each function already uses through read-only connections: Slack, Confluence, Jira, Google Drive, GitHub, HubSpot or Salesforce. It writes one cited onboarding artifact for each new hire, covering all three layers, for any function including engineering and product. Every claim links to its source. The hiring manager approves it before day one.
The People team gets what it wanted from the template: every function, same standard, without writing any function's context itself. A sample artifact shows the three layers in one document.
FAQ
How can a People team create role-specific onboarding without writing context for every function?
By owning the structure and the company layer, and having the team and role layers assembled from each function's own tools. The hiring manager approves the result instead of writing it.
How do growing companies standardize onboarding across different roles?
They standardize the container: the same structure, checklist and approval step for every hire. The role context inside it is different for each function and each person.
Why don't managers fill in the role-specific section?
Writing it takes hours they don't have, usually while they're covering the open seat. Approving a draft is a much smaller ask.
Does this work for engineering and product hires?
Yes. The three layers are the same for every function. Only the sources change.
Sources: Gallup for the 12% figure; Gallup, 8 Practical Tips for Leaders for a Better Onboarding Process (2021), for the 29% figure. Both are on the onboarding statistics page.
Run it on your next hire. 30 days. Then we talk. Start a pilot or see a sample artifact. How it works for scaling teams.