Projects
Pursuited.
Pursuited is a desktop and mobile platform that aims to connect headhunters with potential job candidates. It’s a data driven platform that motivates candidates with information about the job market and their position within it.
The platform’s MVP status dictated us focusing on one key persona: an early-30’s accountant who’s tech savvy but time poor, unhappy in their current job and interested in the job market and potential opportunities.
Pursuited had a limited user base, but insights could be garnered from their analytics which showed up to a 60% bounce rate during signup, and a further 40% immediately after signup.
I guided the client on conducting a survey of onboarded and bounced users to try and garner some insightful pain points. Trends were seen in sentiments “Benefits not obvious”, “Became lost / confused”, “Lost motivation”.
I performed an audit of their current onboarding workflow, with a focus on areas with notably high bounce rates. During this audit, I documented many potential issues to address such as lack of clear reasoning for requesting private information, excessive form length and no clear next steps post-signup.
The team and I started with a rough sketching session to get as many ideas on the table as possible. Clear trends were seen with ideas incorporating the platform’s data into the onboarding as a carrot for the user, and breaking steps down into a clear progression.
I synthesised highest voted ideas into one approach for the onboarding workflow and two approaches for the post-signup dashboard. A rudimentary design system already existed, so we opted to skip wireframes and use high fidelity components. These were then presented to the client.
Once the client approved my approaches, the mockups were refined and fleshed out as Figma prototypes in preparation for testing.
Using Maze, I defined a number of key workflows for success, and the client organised a set of both existing a new potential users to test the solutions. Within each prototype there were a number of sub-workflows we tested for efficacy, such as ability to define salary values and navigate the onboarding progress bar.
We did not perform any face-to-face interviews for this project, but instead included relevant questions into our Maze tests. We wanted to confirm that users were sure of why they were giving information, could see benefits in the data they received in return, and knew what to do next post-signup.
Beyond some refinement of where and when certain data points were show during signup, our onboarding prototype was largely successful. The post-signup on the other hand still confused users as to what to do next. This was evidently due to an overload of information shown to the user, which we further refined.
When I was confident with the solutions we’d tested, I went ahead and refined the existing UI design system that was in place to be suitable for implementation by the client’s development team.
The onboarding solution was implemented over 2x two week sprints. I was present for sprint meetings and the direct contact for their development team during the sprints to ensure clarity of communication and a smooth implementation of the designs.
Pursuited were in the midst of securing a funding round during this project, and their budget did not extend to post-launch monitoring and iteration. They reported a significant improvement in their bounce rates, which assisted them in successfully securing their next funding round.
Let's Chat
.png)