Utilizing workarounds may be sufficient temporarily. However, as a product matures, a thorough review of each piece becomes necessary.
Contract management at Keka was suffering from a lack of optimisation, poor management, and insufficient visibility. This resulted in improper usage and workarounds, making the overall product unsuitable for expansion.
Contract workers are employees who are typically hired to complete specific projects for a set period. This gives companies the flexibility to adjust their workforce as per their demands.
Here’s a really nice refresher by my peer on what it means when we say the term contingent/contract worker
[Complexity and Importance] Unlike managing employees, contract workers come with a define set of time period which leads to situations like extensions, completion, conversions and other crucial situations for contract workers
[Needs & Goals] → A system that fits into an HR/admins’ fast paced work style → A system which is functional and proactive → Flexible to fit different contract duration use cases
[Pain point]
→ Current system is inefficient as it uses work around policies like probation policies to manage contract workers → The lack of a dedicated touchpoint for actions such as extension and work type conversion leads to an increase in execution time.
A really important part during any project is defining the solution scope.
Asking these questions, before you start, could really help to keep all the expectations clear.