Onboarding checklist
Onboarding is a service the team owns, not homework for the new joiner. The goal is not paperwork completion — it is a first useful contribution shipped with support, and a clear picture of who to ask about what.
Recommended default
Section titled “Recommended default”Run onboarding against a written checklist with named owners and a two-week horizon. By end of week two the new joiner should have shipped one small, real change to production and named the people they’d ask for help on code, process, and product.
- Assigned buddy from day one. One named peer, not “the team”. Their job is to answer stupid questions and unblock small friction — not to run the onboarding.
- Access before day one. Laptop, accounts, repo access, and calendar invites land the working day before the start date. Chasing access on day one is a failure of the team, not the joiner.
- Env set up together. Book a session where the buddy and joiner get the stack running on the joiner’s machine. A setup wiki is a fallback, not a plan.
- First commit in week one. A typo fix, a doc tweak, a test rename — anything that exercises the full change pipeline end to end.
- First real change in week two. Something in the joiner’s stated remit, reviewed and merged like any other change.
- Written and driven. The checklist lives in the repo or team wiki, and one named person walks the joiner through it. An unattended checklist is verbal onboarding with extra steps.
Why this is the default
Section titled “Why this is the default”The first two weeks decide whether a joiner will ask questions or hide them. Named owners remove the “who do I bother?” tax. A shipped change in week one proves the toolchain works on their machine and surfaces broken setup before it compounds. A shipped change in week two proves the team’s review and release path is walkable by someone who wasn’t there when it was built.
Written checklists survive turnover. The person who onboarded the last hire is often the wrong person to onboard the next one.
Common mistakes or tradeoffs
Section titled “Common mistakes or tradeoffs”- No named buddy. “Ask anyone” means asking no one. Pick a person.
- Access requests on day one. The joiner spends a week watching tickets crawl through IT. Pre-provision.
- Setup by wiki. A README is a backstop, not an onboarding activity. Half a day of paired setup beats three days of solo troubleshooting.
- Reading week. A week of docs with no commit teaches nothing durable. Pair reading with a small change.
- Onboarding by osmosis. Sitting in on meetings is not a plan. If it’s not on the checklist, it doesn’t count.
- Overloading week one. Twelve intro calls and no keyboard time. Cap intros at two or three a day.
Step by step
Section titled “Step by step”- Week -1 — buddy assigned, access requested, laptop shipped, first-week calendar drafted.
- Day one — welcome, public intro in the team channel, buddy intro, paired env setup, repo clone, dev server running by end of day.
- Week one — pair on one small change; ship it. Intro calls with adjacent teams, capped.
- Week two — pick up a real ticket from the backlog. Buddy reviews first, team reviews second.
- End of week two — 30-minute retro with the buddy and manager. What was missing from the checklist? Update it before the next hire.
Remote joiners
Section titled “Remote joiners”The felt gap for a remote joiner is belonging, not tooling. No overheard chatter, no face attached to the name in the git log, no ambient sense of what the team cares about. Design for visibility.
- Introduce publicly, twice. Team channel on day one; adjacent teams by end of week one. A joiner nobody has been told about is a joiner nobody feels responsible for.
- Cameras on for the first week’s syncs. Faces buy trust faster than Slack does. Drop the norm back to team default from week two.
- Daily 15-minute buddy check-in for weeks one and two. A standing slot removes the “am I bothering them?” tax that quietly kills questions.
Joining two teams at once
Section titled “Joining two teams at once”A joiner splitting the week across two teams is not one hire onboarded twice as fast. It is two half-speed onboardings that will collide unless planned apart.
- Per-team first-ship goals agreed before day one. Two backlogs surfacing urgent tickets in the same week is the failure mode. Each team commits to one small change, scoped to the joiner’s days on that team.
- One buddy per team. A shared buddy across both teams is zero effective owners. Halve the joiner, not the buddies.
- Name the split out loud. “Half-present on purpose” is a legitimate onboarding state. Say so in both team channels — the guilt of appearing absent is what suppresses questions.