Scroll to top

Simplifying Recruiting


My role:
Product Designer

Randall Reilly


Group of three screens from stratas including track, analyze and strategize modules

Project Summary

Stratas is a multi-module intelligence platform designed for the transportation industry that brings together competitive intelligence, talent supply and demand, and granular campaign performance.

With shortages in professional drivers, diesel mechanics and technicians, warehouse workers, and more, Stratas simplifies the process to attract and engage operators with qualified experience in specific locations.

Project Challenge

A common factor companies with long lifespans have is the ability to evolve. By taking on many identities over the last 85+ years, Randall Reilly has done just that. When I first started at Randall Reilly in 2016, it was on the verge of its next transition to what it is today; the leading growth platform for vital industries. 

While Randall Reilly offered many valuable services and resources to its clients, it needed to become an integral part of the way its clients did business. For the transportation recruiting division, this meant solving challenges in recruiters’ workflow while meeting business goals.


  • Simplify a complicated recruiting technology stack

  • Give more visibility into recruiting pipelines

  • Help clients grow their businesses

  • Create a seamless, efficient recruiting process

  • Turn our users into workplace heroes

  • Give the client more power over their Randall Reilly products and services

  • Make existing Randall Reilly products and services available in a client-facing UI


Stratas is a multi-module subscription-based platform that provides visibility into talent pipelines, enabling fast, strategic decisions. From tracking applications to automated nurturing, Stratas empowers growth. Stratas modules can be used independently or in sync with one another.

Group of icons showing the modules of stratas. These modules are track, analyze, strategize, reach, and connect.

How do the modules work together?

Bob’s Trucking needs to hire more drivers.

Infographic flow chart showing how the modules work together. The flow chart starts with a manager researching for a campaign in strategize. They then create a job posting in reach and creates an automated call campaign in connect. Reach then posts the job on job boards. Drivers then submit applications. A driver profile is created in track while connect calls the driver and forwards them to a recruiter. A recruiter answers the phone and opens the drivers profile in Track. The driver is then progressed through the hiring process. During this entire process the manager can use analyze to monitor campaign performance and use track to monitor recruiter performance.

Module #1



See the pipeline of leads responding to job postings.

Track Discovery

Track (ATS – applicant tracking system) was the first Stratas module to be developed. It originated from an acquired product that needed to be rebranded and have new features added. This case study will primarily focus on Track since being the first, and at the time largest module, required the most research and design. All the other modules would follow in Track’s design patterns, style, and functionality. It was important to get it right.


Track Preliminary Research

Not having many research resources, I had to collect information from stakeholders, product managers, and in-house user experts. Since Track was an existing product, I was able to access HotJar heatmaps, session recordings, and research competing products.

Findings included:

  • Recruiters need easy access to driver information. Many times they are working in their ATS, receive a phone call from an applicant, and have to switch tasks quickly.

  • Most activity happens on a few screens which the recruiter has to go between.

  • When recruiters access applicant tables, the tabs default view is set to the least used tab.

  • Driver data has much of the same hierarchy making it difficult to find key information.

  • Competing products do not follow best design practices or have the most intuitive user flow.

Hypotheses from findings:

  • Making driver information easier to access would help recruiters be more efficient on the phone.

  • Reorganizing the main screens recruiters work most on would minimize clicks and allow the recruiter to work faster.

  • Switching the default tab view of the applicants table will reduce clicks and will remove friction for the recruiter.

  • Adding more hierarchy to the driver data will allow the recruiter to better find what they are looking for.

  • Following best design practices and providing a good user flow would put Track ahead of the competition in design.

Track Design

The biggest portion of the Track re-design was to create a new user flow and information architecture that minimized clicks and made the recruiter’s work process more efficient. The original design had the majority of features used by recruiters spread out onto multiple screens. Most of these screens were minimal in what features and sections they contained. It made sense to combine related screens so the recruiter could do all their needed work in one place.

Old Track sitemap showing a top level navigation of dashboard, applicants, hired drivers, tasks, DOT app links, reports, and SMS campaigns. Off of applicants, there is a second level page of applications. Off hired drivers, there is a second level page of driver profiles. Both applications and driver profiles link to a third level page of leads.
Old Track sitemap
arrow pointing down
New Track sitemap showing a top level navigation of dashboard, workflow, DOT app links, reports, and SMS capains. There is then a second level navigation of leads, worklist, hired, and tasks off of workflow. Finally driver profile can be acccessed from all the second level pages.
New Track sitemap

Once the new site map was complete, I began sketching layouts for Track on paper. I then moved to on-screen wireframes. Initially, the driver profile was still on a separate screen from the driver tables. After presenting version 1 wireframes and talking with in-house user experts, the driver profile was combined with the driver tables into a dual-pane format. This allows a recruiter to do a majority of their work on one screen creating a seamless, efficient workflow. 

Version 1: No dual-panel. Recruiter workflow tables and driver profile were on separate screens.
Version 2: Dual-panel design. Recruiter workflow tables and driver profile are combined onto one screen.
High Fidelity Mock-Up: Workflow

Track Design Summary

  • A dual-panel layout makes for easy searching and editing of driver profiles and allows the recruiter to switch tasks quickly.

  • The default tab is now the leads tab. In the original version, users landed on a lesser-used tab and immediately had to click the leads tab. Other tabs are ordered sequentially based on application statuses.

  • Important data like basic driver contact, status, and assignee were moved to a prominent place at the top of the driver profile.

Feature Highlight: Flexible Workspace

One of my favorite feature contributions to the Track UI is the expandable and collapsible panels. The dual-panel layout may keep the user on one screen, but with the amount of information present, it could become a difficult space to work within. Giving users the ability to make one side of the screen larger as they work alleviated this. Certain sections and features become easier to access and use. For example, if the user needs to add columns to the driver table, expanding that panel will help them do that.

This feature combined with the all-in-one work screen gives Track a better user flow and function than its competitors.

Animation showing the expandable panels in track. The table on the left expands to show more rows when the edge is dragged to the right. While the table is expanding, the driver profile on the right is getting smaller and stacking.

Modules #2-4



Compile all data from recruiting efforts in one platform.



Empower recruiting with competitive insights, driver market insights, and campaign trends and benchmarks.



Automate driver text messages and phone calls.

Analyze, Strategize, and Connect Discovery

Unlike Track, the remaining modules were built to give client-facing UIs to existing, proven Randall Reilly products and services. These UI’s would put more power in the hands of the client and allow them to access things like their Randall Reilly campaigns and Randall Reilly’s vast industry data.

The discovery phases for these modules were much simpler than Track’s. These were completely new UI’s which means there were no heat maps or user data to help make design decisions.


Preliminary Research

Product managers for these modules were experts with the associated product or service and its users. Each product manager provided me with a basic outline of what needed to be in the UIs to give the client full access. I also learned what I could about the products or how the services were performed to make educated decisions. This not only gave me insight into the needs of the user, but also what these UI’s would connect to or trigger on the back end.

Findings included:

  • Not all of Stratas users can interpret data well.

  • Some services provided through these modules still require edits to be performed manually by Randall Reilly employees through a ticketing system. This takes power away from the user.

Hypotheses from findings:

  • Presenting data clearly and simply will make it easier to understand and help users get the most out of the platform.

  • Integrating the UI with the ticketing system and allowing the user to visually edit will give them the illusion of more power versus filling out a ticket form.

Analyze, Strategize, and Connect Design

After mapping all the needed features and coming up with what I thought was the best organization and user flow, I began doing sketches on paper. Being the only UI designer, most screens for these modules went directly from paper sketches to high-fidelity mockups. There simply was not enough time to lay everything out and get the mock-ups to development on schedule. No testing was being done before development and stakeholders had already approved my site maps and information architecture. This meant wireframes were really just for me to explore iterations. I had to rely on my design background and what I knew about best practices for these modules.

With Track past the design phase and company branding guidelines in place, I was able to pull the design and feature styling from those. This not only made designing easier but is a good practice to give continuity to the modules. For example, all tables and charts will look the same throughout all of Stratas. If there were like screens across modules, I arranged the pages as similarly as possible.

High Fidelity Mock-Up: Analyze
High Fidelity Mock-Up: Strategize

Analyze and Strategize Design Summary

  • Charts follow a card layout to designate which charts can be exported together and to group them by category.

  • Continuity between modules was very important. Filters, side navigation, and dashboard actions all work the same across both of these modules.

Feature Highlight: Narrative Data

Both Analyze and Strategize are data-heavy modules. From my research, I knew some users may have a hard time drawing conclusions from data. Large summary metrics were added however, to take this a step further, I proposed adding data in a narrative format. This helps users understand what the dashboard is showing them qualitatively and gives a deeper understanding of the data to a larger audience. 

Narrative data example from Analyze showing a budget metric with a text description below explaining how this months budget influenced leads and hires.
High Fidelity Mock-Up: Connect

Connect Design Summary

  • Connect follows Track in its dual-panel layout for continuity.

  • When updates to a campaign are saved, a ticket is triggered on the back-end. To the user, it appears they made campaign changes, but really they created a ticket. This gives the illusion of more power to the user.

  • To further add to the power illusion, specific language was chosen for certain UI elements. One example was using the word “processing” instead of “in review” for the campaign status of an edited campaign.

Feature Highlight: Predictive Metrics

When setting up a campaign in Connect, the user selects an end date and lead goal for their campaign. However, sometimes the lead goal is not met before the campaign end date. Most of the reporting from Connect campaigns is found in the Analyze module, however, I thought having a predictive metric of lead goal vs. campaign end date in Connect would be beneficial to both the user and Randall Reilly. Showing the user a predicted goal completion date would allow them to compare it to their set campaign end date. If this goal completion date was further out than their campaign end date, they could make an informed decision on either extending their campaign end date or increasing their budget to meet their goal.

One of the goals of Stratas is to make the user a workplace hero. This feature gives them the insight to make informed campaign decisions for a successful campaign and to help their company reach its desired outcome.

Predictive metric example of estimated goal completion date.

Unifying the Modules

With the development of new modules, a header that allowed users to switch between them, access individual module screens, and get to global features was needed. With some modules being more complex than others, it was important this design was expandable. Different subscription types had to be considered as well. Some users may subscribe to all the modules, while others subscribe to one. The header needed to look consistent no matter what modules the users subscribed to.

Iteration A - This version had all the module icons across the top with drop-downs to their screens. This version did not allow for the expansion we needed.
Iteration B - This header option was the one we eventually went with. Here, all the module icons are within a waffle menu. This way of navigating is familiar to users since it is used in popular applications. Having the icons in a waffle menu also cleared the header and gave more space for additional features in more complex modules. This iteration also looked good no matter what the user's subscription was and fit better with branding goals.
Stratas High Fidelity Header Mock-Up

Challenges and Lessons Learned

Stratas was my first product and my first time working with developers and product managers.

My biggest challenges were: 

  • figuring out where to insert myself into the design process
  • learning how to work with developers after mockup handoff
  • I was the only designer and spread thin between multiple projects
  • limited resources meant there was no testing before development

Things I learned in this process:

  • an understanding of good design practices is important when resources are limited
  • a better understanding of the product design process
  • where I fit in the product design process
  • better ways of working with product teams

Simplifying Recruiting