It is never about setting up a process and being done with it. Rather, the focus should always be on optimizing it for the best outcomes. Thus, we didn’t stop at setting up JSM for our recruitment process. We looked at the process from different stakeholders’ points of view and came up with some neat things to make it more delightful for everyone.
Let us dig in deeper, assuming you have already read through part 1 of this post.
JSM has a feature that lets you customize the email notification content. Obviously, this feature is accessible only to the service project admins. The default seeded content for these notifications is not targeted at your prospective employees. Now, this should present itself as an opportunity to speak to the candidates. Make the content modifications in these templates & ensure your employer branding is prominent in them.
Additionally, you can also control what events generate notifications to the candidates. Easy peasy, ain’t it!
Some tips to spruce up your emails templates:
If not for automation, human race would have missed out the chance to do all these amazing things while letting the code take care of routine stuff. So go ahead. Think about the repetitive scenarios that your recruitment process encounters. And then use Jira’s native automation to nudge relevant stakeholders in the right direction.
Here are some of the situations that really stand out as automation candidates:
Is the process becoming too mechanical already with automation? Well, don’t let that happen. Prospective employees are your future customers, offer them the best in class experience with consistent & detailed communication. Use something like Canned responses once you take help from your copywriters. This will save a lot of time for your HR team involved in the recruitment process.
Do not stop at creating only a few response templates. Otherwise, there will be a repetitive & mechanical feel to the overall conversation. You always want to build on & continue to improve the candidate experience. It is not only about improving efficiency but also about not losing the human touch in these discussions.
One big thing that your team needs to be trained on - not putting in customer-facing comments by mistake. We solve this problem with a simple rule - only our colleagues from HR communicate with the candidates via these customer-facing comments. Everyone else does participate in the process, but they only post internal comments.
Even the HR folks can commit this mistake of posting an internal comment externally, but the chances of that happening become exponentially less.
Apart from hiring the best possible candidates quickly, your recruitment process should also have another equally important goal. Which is to delight the experience of every candidate that has ever shown interest in joining you. Put another way, your recruitment team should be held accountable to the satisfaction ratings provided by your candidates. Satisfaction ratings & comments, especially from the candidates that were rejected along the way, are your guiding rails to improve the process.
To get more accurate responses, modify the satisfaction rating question. Look at the screenshot below.
Once your recruitment service project is moving steadily, need for more insights will arise. That is where Jira’s native dashboard gadgets will come into play. You will be able to look at different charts and respond to the questions like
You can even get some advanced insights such as
Here’s a very simplistic dashboard from our recruitment project:
Hope this helps HR teams to start moving to Jira & Jira service management, where rest of the teams are already working day in day out.
Anand Inamdar_AmoeboidsRising Star
Calling all collaborators and Confluence users! Our Appy Hours event on September 29th features 4 presenters demoing functionality to superpower Confluence. Don't miss learning about these apps i...