Consolidating Resumes

The Problem

CareerBuilder’s Recruitment Software Solution offers users four “lists” of candidates: applicants via jobs, intake matches, job matches, and a custom sourcing list. These lists are stored independently of one another, meaning that the organization of candidates is not consistent. The solution to this is to allow users to store and link these lists together through “projects”.

Timeline: 8 x 1 week sprints Role: UX / UI / UXR / IA

Intake: After the open req conversation between the hiring manager and the recruiter has occurred and the recruiter has gained all the needed information, a list of matched candidates are shown based on the information. This custom list can be moved into a custom project.

Projects: Lists will be renamed to projects so that it is clear that multiple lists can be included in one project.

Talent Network: When users search through a project or through the recruiter database an indicator releasing where the candidate lives within the product will be provided to the user.

Create New Project: Users can create new projects from Intake, Jobs, and Recruiter Database (CBSearch).

View Candidates/ Applicants: Sourced candidates and matched candidates will show here. If a user ties a job to a project or creates a project from a job, those candidates will be listed as well.

Information Architecture

Research Plan

The goal is to validate the early concept flow above and test the potential designs below with clients who utilize “lists” most often.

The Research Hypotheses

Hypothesis 1 - Users are accustomed to lists, and do not understand trello-boards. Instead users will prefer spotlight tabs such that LinkedIn Recruiter has. INVALIDATED

Hypothesis 2 - We assume users want the capability to remove or reject candidates. VALIDATED

Hypothesis 3 - Users want to upload other resumes into projects (importing from other devices). VALIDATED

Hypothesis 4 – Users would like to have one home page for all of their lists. VALIDATED

Hypothesis 5 – Users want the option to either tie a requisition to a project, or not tie a requisition to a project. VALIDATED

Hypothesis 6 – Users want the ability to tie multiple requisitions to one project. VALIDATED

Hypothesis 7 – Projects will show value to all users. VALIDATED

Hypothesis 8 – Users are creating lists in CareerBuilder. VALIDATED

Tools: Sketch, Invision, Usertesting.com Platform: Desktop Deliverables: 2 user testing debriefs, hi-fi prototypes

First Iteration

After taking into consideration what the previous research had shown, multiple iterations of the design were taken into consideration.

Actions/Bulk Actions [Green]: Uses appreciate having the option to bulk message, and want to know if this feature is coming. However, with this design they do not like the constant clicking in order to do one action, it seems slightly confusing with multiple ellipsis coming out of everywhere.

Workflow/Status Steps [Red]: Users want ability to change workflow names and status’, and for the numbers to be clickable in order to filter the table by those specific status’.

Search Filter [Blue]: Users prefer the filtering to be done by clicking on the number in the 5 boxes, which means there would have to be an option for “all” candidates as well. Searching within table should be broader than just name, should also include company, job title, freshness (date active) and YOE. (Remove the side bar Filter Table.)

Messaging [Yellow]: Users want the ability to send Campaigns not only to MyCandidates, but to everyone in CB. Individual messaging is a “nice-to-have” but would have to work for ALL candidates.

Update Status [Red]: Users really like the idea of a mini ATS within the CB products. Therefore, they would love to be able to do pre-ATS activities by adding additional fixed or non-fixed status’ to their workflow.