How to save time with employee onboarding and which role could Jira play in this area?

Forbes stays that it’s common that companies have just one or two day onboarding programs that focus on familiarizing newcomers about legal and policy-related rules. The result of these is that new employees are left unprepared for their first 90 days. They are often have to understand their jobs in-depth, uncover team relationships, and integrate themselves into their new company’s culture on their own.

From our experience, it’s much more efficient to have an onboarding plan defined for each job title, moreover, it’s much more comfortable to have it automated as Jira tickets. For example, this workflow could be useful within the onboarding case:

Pre-boarding, where linked issues for workplace preparation are created (newcomer would need a laptop, a list of accesses, documents, etc.)

Day 1, where the real onboarding starts. Here the system could create tickets for office excursion for HR, «meet and greet» for team manager, NDA and policies for the employee

Day 2, and there are more linked issues created: a manager follow-up task to make sure everything is on track, a list of tasks for mandatory trainings

Week 1 status creates a follow-up task for employee’s manager and HR to discuss how the newcomer feels about their job and if there is smth to fix.

Onboarded. At this time the employee is considered to be onboarded and the status attribute for the employee is updated to «Onboarded» and the Onboard Employee request is resolved.

Just that easy! In combination with Confluence it could be more efficient and less time-consuming, but having a plan is a good idea in any case.