We cut our onboarding checklist from 41 items to 12
New hires kept asking the same five questions. The checklist was answering everything except those.
A checklist is a promise.
Illustrative example. This story and its author were written by the hr.cafe editors to demonstrate the Field Note format. It does not describe a real person or event. Real, contributor-approved stories will replace it.
Key takeaways
- We sorted every item by who owned it and whether a new hire would notice if it was skipped.
- Twelve items survived; the rest became background tasks with named owners outside the checklist.
- Repeat questions in the first two weeks dropped noticeably, though we did not measure this formally before the change.
- Role
- People Operations Lead
- Organization
- B2B software, ~80 people
- Region
- India
- Timeframe
- One quarter
Situation. Our onboarding checklist had grown to 41 items across HR, IT, finance and the hiring team. Everyone had added something after a bad week. Yet in their first fortnight, new hires still messaged me the same five questions: who approves leave, how expenses work, where the team’s real priorities were written down, who to ask about tooling, and when they would get feedback.
Action. I printed the checklist and sat with two recent hires and one hiring manager for forty minutes. For each item we asked two questions: who actually owns this? and would a new hire notice if it was skipped? Items owned by a system (account creation, payroll setup) moved to an internal task list with named owners. Items nobody could explain were deleted. The five recurring questions were added, answered rather than linked.
Observation. Twelve items survived. The checklist now fits on one screen and every item has a human owner. In the next four cohorts, I received far fewer repeat questions. I want to be careful here: I did not count messages before the change, so this is my honest impression plus two new hires telling me the first week felt “less like a scavenger hunt.”
Every item you add to a checklist is something you are promising to check. We had made 41 promises and kept about 20.
Lesson. A long checklist can hide the absence of ownership. Shortening it forced conversations about who was responsible for what. The IT handoff in particular had been unowned for months. The limit: our company is small and co-located twice a week. I do not know how well this translates to a large, fully remote organization.
Question for peers. If you have done something similar at scale, how did you stop the list from growing back?
Questions for peers
Priya Raman would like to hear how this plays out in your context.
- What is on your onboarding checklist that no new hire would miss?
- How do you find out which questions new hires are too polite to ask twice?
Respond to Priya
Responses are read by a moderator before anything is shown publicly, and only with your permission. There are no public responses on this story yet.