Redesigning email alert & projects flow
From the functionality that few recruiters used to one of the most adopted features in the product
This redesign significantly increased email alert usage
Context:
Textkernel is an ATS platform. As a part of bigger redesign of Search, I was assigned to examine email alert & project functionality, determine use cases and propose solution.
Process:
1
Identifying pain points in the current flow
2
Internal research
3
Propose first draft of the solution to the team
4
Evaluative research
5
Iterate the design & measure results
1
Pain points in the current flow
I examined the currrent flow, and found out that the email alert feature is hidden under “projects” functionality. So, if recruiters don’t use projects, they might not be aware that email alerts exist.
searching candidates
creating a project
setting up email alert
saved to projects
2
Internal research
UX Designer in Amsterdam
Email alert:
Off
Daily
Weekly
Monthly
Save
Cancel
We didn't have time for exploratory research, so PM and I decided to collaborate with CS to gather data we already have. We learned that recruiters who attended learning sessions use email alerts 5 times more often than the rest. This insight reinforced the idea that email alert is hidden.
3
Looking for a solution
I started to think about the possible solution. I started exploring how a recruiters could set up email alert differently. I found several solutions:
Email alert is off
Email alert is on
Create email alert
Edit email alert
Create email alert
Edit email alert
After several iterations, we decided to test toggle variant with users.
After redesigning email alert creation flow, the product team raised a question about where to store this info. We came up with the idea of creating a new dashboard. I created the first draft, but also created new UI for existing pattern, to test several ideas during the upcoming research
4
Evaluative research
Research findings
7/10 recruiters used email alerts as a part of their working routine. Also, we learned that some users indeed don’t know about this function in our product.
4/10 recruiters didn't find information about email alert and its frequency on the dashboard. Also, date was missing.
5/5 new users were confused with “projects” naming. They were guessing what it means.
5
Changes in the design
After the research I conducted a workshop about the changes we want to make, and we agreed on the action plan:
v
Go with the dasboard idea, but add date and make email alert info more noticeble
v
Rename "save project" to "save search"
v
Merge saved searches and email alerts on the dashboard
Final designs
After implementing the changes here's what the designs look like:
Monthly
Weekly
Daily
Off
Learnings:
1
Even if we don't have time for research, we can collaborate with other teams to gather info that we already have
2
Strategic, minimal UI changes can have a significant impact on UX and feature discoverability
3
This project taught me to effectively balance short-term redesign goals with long-term design vision