A lively and diverse city, historic North Charleston wanted a campaign that reflected its vibrant atmosphere and signaled that it’s a worthy destination in its own right. As a result, I developed this colorful, eclectic map illustration that highlights the unique features of the city. Our campaign presented North Charleston as a hub from which nearby downtown Charleston, Mount Pleasant, and West Ashely are accessible, but also highlighted some of the fun and exciting aspects that make the city stand out.
Fetcher is a SaaS start-up that places a strong emphasis on prioritizing clients' experiences when it comes to receiving high-quality candidates. By hand-delivering batches of candidates based on specific client criteria, Fetcher aims to make the process of finding the right person for the job fast, easy, and enjoyable.
Fetcher provides a dedicated page for every created position that includes analytics, candidate information, personalized templates, and more. However, the page's title appeared as a UI breadcrumb and included a dropdown where all the job positions sections were located, causing users to overlook the dropdown feature and remain unaware of its existence.
Based on the hypothesis that moving the job position sections from the dropdown to a more prominent location will reduce user confusion and enable them to achieve the primary minimum viable product (MVP) goals, we can explore potential design solutions that enhance the visibility and accessibility of this information. By prioritizing user needs and behavior, we can create a user-centered design that streamlines the user journey and improves the overall user experience.
Overview
In an effort to improve the visibility of categories on the interface, we have generated a range of ideas through brainstorming sessions. These ideas aim to enhance the discoverability and accessibility of categories, ensuring that users can easily find and navigate the content they are looking for.
Brainstorm sketches below:
Brainstorm
Solutions
1. Tabs
Given that our design system already includes a tab component, it seems reasonable to utilize this existing component to create a simplified design that aligns with our project's scope. By leveraging this component, we can create a cost-effective solution that meets the project's requirements while maintaining consistency with our established design system.
2. Pullout Navigation
Following competitive research, I came across examples of navigation that slide out from the interface. This approach could potentially help conserve screen real estate and optimize the use of available space.
3. Right Side Navigation
After implementing Solution 2, which involves Sliding Navigation, I noticed that the left side of the interface may have a lot of information. To help users better comprehend that this information is divided into distinct categories, I believe that introducing visual separators could be beneficial in clarifying the organization of the content.
4. Sliding Affect
This proposed solution shares similarities with Solution 2, Pullout Navigation, as it involves sliding navigation elements to display information. However, implementing this solution would require a significant investment of time and effort, and may not align with the project's scope. As a result, it may not be a viable option to pursue at this time.
5. Large CTA Buttons
Compared to the other solutions, this proposed solution stands out as it prioritizes the visibility and legibility of words. However, transitioning between categories may pose a challenge, and implementing this solution may require a dedicated interface to ensure smooth navigation. Given these considerations, it remains uncertain whether this approach is feasible within the project's scope.
Tabs was selected!
After deliberation with the team, we decided to go with this design. We made this decision based on the scope, time, and design system. We already had these components created and knew that it would be the most efficient design that would provide all the red routes with minimal effort.
Solutions Picked
Pain Points
Prioritized viewing candidates over the analytics:
In the current interface, the analytics section was given prominence as it was deemed important for recruiters to view candidate statistics. However, feedback from users indicated that they would prefer candidate profiles to be more prominently displayed. Therefore, we may need to re-evaluate the layout and prioritize candidate profiles to better align with user needs.
Filters:
Our current filter design features filters within a dropdown menu that may not be easily noticeable to users. To enhance the user experience, we aim to make the candidate filters more prominent and accessible, particularly for unvetted candidates, enabling users to easily filter and sort through candidate profiles.
Amount of candidates:
Currently, there is no visible indicator that displays the total number of candidates. However, this information is important to users as it provides an idea of the size of the candidate pool. Therefore, we may need to incorporate a clear and prominent display of the total number of candidates to better meet user expectations.
tool. We are equipped with a versatile design system that caters to both internal and external applications.
Moved Profiles to the first tab instead of Analytics:
After analyzing user behavior, we recognized that users primarily accessed candidate profiles instead of the analytics section. Therefore, we decided to prioritize the Profiles page by placing it as the first option in the navigation menu. While it is crucial for users to have access to position statistics, it is essential for them to vet the candidates to facilitate the candidate selection process and make progress in the search for suitable candidates.
Visible Tabs:
After considering our design options, we chose to replace the existing dropdown with tabs from our design system. To further improve user experience, we also incorporated icons next to the category labels to aid users in differentiating between them.
The Number of Candidates:
Initially, the number of candidates within a specific filter was not visible. To provide users with better visibility into the candidate pool, we added the total number of candidates within each filter.
Visibility of Filters:
Our previous filter design featured a dropdown menu that was either underutilized or difficult to locate for users. In order to improve user experience and facilitate easier navigation between candidate profiles, we aim to make the filters more prominent and accessible
Order of Filters:
To optimize the filters, I prioritized the most frequently used filters that users would require, resulting in a higher signal-to-noise ratio. This approach helps to save users' time and improve their overall efficiency.
To confirm that our design effectively addressed user feedback and pain points on the interface, we conducted an A/B test, comparing the current new interface with the older version.
Solutions
Testing
We requested 10 clients to complete the Minimum Viable Product Screens (MVPS) on both prototypes and posed the following questions:
If you can, please explore this prototype and share any initial feedback.
-
Can you show us where to find the people on your team that is on this specific search?
-
Can you show us where you’d find the candidates related to your search? before clicking. Could you tell me what the number in red means to you?
-
Can you show us where you’d look at notes related to this search?
-
Can you show us where you’d go to view the email touchpoints related to this search?
-
How do you feel about this experience compared to the current navigation we have on Fetcher.ai?
Results
The results revealed that every user favored the tab interface over the original interface. It was intriguing to note that a few users were unaware of certain categories such as notes or templates in the older design, and they had to adopt a workaround to access them. These users expressed their enthusiasm and satisfaction upon learning that we would be implementing these changes.
All users successfully completed every task listed with a 100% success rate on the Tab interface.