Why map the onboarding process
Employee onboarding is one of the most impactful processes to map. It touches HR, IT, management, and the new hire. It runs frequently (every new hire). And when it breaks, the cost is high: slow time-to-productivity, poor first impressions, and early turnover.
Most organizations have an informal onboarding process that lives in someone's head. When that person is on vacation, things get missed. Mapping it makes it consistent, complete, and improvable.
What a good onboarding map includes
Pre-day-one (offer accepted to first day)
Welcome email, contract signing, IT equipment setup, account provisioning, workspace preparation, buddy assignment. These can run in parallel - use parallel gateways.
Day one (first day experience)
Office tour, team introductions, system access verification, security briefing, first tasks. The sequence matters - you cannot start working without system access.
First 30-60-90 days (ramp-up)
Training milestones, check-in meetings, feedback sessions, probation review. Use timer intermediate events for scheduled check-ins.
Common onboarding problems process mapping reveals
- -IT setup bottleneck - everything waits on IT provisioning. Solution: trigger IT setup the moment the offer is accepted, not on day one.
- -Missing handoffs - HR hands to IT but nobody tells the manager. Solution: parallel notification flows.
- -No error handling - what if the background check fails? What if the new hire does not sign the contract? Add exclusive gateways for these decisions.
- -Inconsistency - each manager onboards differently. A documented process ensures every new hire gets the same experience.
BPMN elements you will use
- -Lanes - HR, IT, Manager, New Hire. Shows who does what.
- -Parallel gateways - IT setup, buddy assignment, and workspace prep can happen simultaneously.
- -Timer events - scheduled check-ins at 30, 60, 90 days.
- -Exclusive gateways - background check passed? Contract signed? Probation passed?
Related guides
Keep learning
Frequently asked questions
How long should it take to map an onboarding process?▼
A first draft takes 2-3 hours with HR and IT in the room. Validation with all stakeholders takes another 1-2 sessions. Total: about a day of effort for a process that runs hundreds of times per year.
Should we automate onboarding?▼
Parts of it, yes. IT provisioning, welcome emails, and document generation are excellent automation candidates. The human elements (buddy meetings, team introductions) should stay manual but be scheduled automatically.
What is the ROI of mapping onboarding?▼
Organizations that map and optimize onboarding see 30-50% faster time-to-productivity and 20% lower first-year turnover. For a company hiring 50 people per year, that translates to significant savings.