OVERVIEW
Legion is a workforce management platform that utilizes AI to help employers accurately forecast labor/demand needs while providing dynamic scheduling capabilities for employees.
Approximately 60% of the U.S. workforce is made up of hourly workers. The main factor that causes high employee turnover within the retail and food industry is due to workers not getting shifts that fit into their schedule, more-so than low pay or work environment issues. Legion’s solutions aim to eliminate labor inefficiency, increase job satisfaction, and bring transparency to the workplace.
BACKGROUND
CHALLENGE
Legion had landed a pilot deal with a national retailer in the spring of 2019. The pilot was set to launch in the fall across 14 locations in the Pacific Northwest.
Any business with a large number of locations have managers managing a region. These are known as District Managers. Legion provides little to no support for District Managers today. The needs of these managers are different than the needs of a single store manager.
Provide compelling capabilities for District Managers to manage a group of locations within Legion. Build a MVP feature to coincide with pilot launch within 8 weeks.
GOAL
ROLE
I worked alongside 1 product manager and 2 developers. I was responsible for the entire end-to-end process from helping define requirements, interviewing stakeholders, wire framing, and building out a prototype.
USER RESEARCH
We began talking to our point of contact at HQ who was a former District Manager. He defined exactly what a district is on an operational level and the type of access they should be granted. Afterwards we interviewed 3 District Managers to get a better sense of their main duties and any paint points they currently deal with. We determined that District Managers needed support in the following key areas:
USER INTERVIEWS
From our interviews, we consolidated our findings into a persona which we reviewed with our stakeholder over at HQ.
PERSONA
REQUIREMENTS
After a few more discussions with HQ, we scoped out the project to the main requirements:
District Managers require an aggregate view
District Managers access is only at a weekly level. DMs can view daily by accessing the Store Manager view for specific locations.
UX support was needed in the following areas:
Controls support for Districts
Dashboards for each District
District Report for Budget & Scheduling
District Report for Time & Attendance
District Report for Compliance Violations
I will only be reviewing the Dashboard view in this case study.
DESIGN
Below is the current dashboard view for store managers today and smart cards used in all of the reporting. I wanted to do a quick inventory to see which components we could utilize in the District dashboard view.
CURRENT DESIGN
I talked with our data science team first to get a grasp of best practices in data visualization. I wanted to learn when it was best to use a bar graph vs a line graph or how to effectively communicate progress in varied time ranges. I began sketching out these ideas and different dashboard layouts.
UI SKETCHES
CONCLUSION
NEXT STEPS
We saw great feedback with the pilot launch in the fall of 2019. Since then I’ve iterated on more stripped down versions of the dashboard for smaller business clients.
LESSONS LEARNED
This project became a company wide effort that taught me how to better manage the expectations of multiple stakeholders. There were a lot of exciting ideas being facilitated between our executives and our client’s HQ. However, I learned to say “perhaps” a lot more instead of promising a vision that hadn’t been thought out yet.
With our 8-week deadline, it was a rush to ship out towards the end. I realized that I have to plan ahead for validation testing way ahead of time and start those conversations before my designs are completed.
