Problem summary

Managing contract employees comes with it’s own set of requirements. Currently, it is a hassle to do that with Keka. Due to a lack of a dedicated system, organisations handle contract employees via probation policy which leads to an incomplete experience.

This project was a crucial addition to the Keka’s CoreHR module and implementing this would allow us to scale our system for a wider adoption.

Here’s a really nice refresher by my peer on what it means when we say the term contingent/contract worker

→ Read it here

Now that we have the required context on what and who we are solving for, let’s take a look on how we approached the problem.

Defining solution scope

A really important part during any project is defining the solution scope.

• How much are you going to solve?
• Is it going to address the minimum functional requirements?
• How much effort would be required to build something close to an ideal system?

Asking these questions, before you start, could really help to keep all the expectations clear.

Preparations🧑🏼‍🍳

To start with the project, a retrospect on past customer requests was done. This involved getting on customer calls, hunting down all the requests and extracting meaning out of them which gave this project a direction.

We mapped out the current user flow, cross verified it with all the requests and what other competitors are doing in the market. With this, we now had a better picture in front of us. An ideal flow was sketched out.

But you can’t really push one ideal flow in the market. The experience should be flexible enough to accomodate a variety of usecases. And another important thing to keep in mind is the market geography that you want to operate in. The things which are considered normal in some might be considered incomplete in others.

Ease of use, Flexibility and Control. The principles to rely on by default.