top of page

Simplifying The Multi-Worker Shift Scheduling User Flow

Apple MacBook Air 13_ Space Grey.png

Overview

Company Background & Overview of the Project
Company Background & Overview of the Project

GigWorx is an on-demand staffing company operating in Bozeman, Salt Lake City, and South Bend-Elkhart. Client administrators, and GigWorx administrators acting on their behalf, schedule shifts on the platform by dragging and dropping a shift template card onto a calendar. Each template card represents one worker, so a five-worker shift takes five separate drag-and-drops and produces five shift cards, cluttering their screen.

My redesign reduces the steps needed to schedule multiple workers for the same shift and groups those shift placements into a single shift card that expands to show each one.

The Results (Pending)

The redesigned multi-worker shift scheduling user flow has not been released yet. This section will be updated once it goes live.

My Role And The Constraints

My Role: I ran requirements sessions with stakeholders and redesigned the multi-worker shift flow.

Constraints: I couldn't interview client administrators beforehand, so I built my understanding of their needs from GigWorx administrators who use the same flow and from client relations specialists who support clients through it.

Understanding Users' Problems With The Current Multi-Worker Shift Scheduling User Flow

Client Administrators Phoning GigWorx to Schedule High Numbers of Workers Instead of Using the Platform

GigWorx administrators and client relations specialists told me that client administrators were phoning them to get large batches of shifts scheduled rather than doing it in the platform themselves. Staff attributed this to the platform being slower for bulk scheduling.

Bulk Scheduling Generates One Shift Card Per Worker, Cluttering the Screen at Volume

Another issue is that a shift card is created for every person scheduled, so a business hiring 100 people for one shift generates 100 cards, cluttering the screen. GigWorx administrators and client relations specialists said this is overwhelming for them and the client administrators they schedule shifts for.

Exploring Design Solutions That Simplify The Multi-Worker Shift Scheduling Process

Setting Worker Count on a Shift Template

GigWorx lets client administrators, and GigWorx administrators acting on their behalf, create shift templates for roles they hire for regularly. Every template represents a single person, with no option to set how many are needed. Staffing a shift for 100 people means dragging the same template onto the calendar 100 times. This needs to change.​

How Best to Show the Number of Workers on a Shift Card

Once an administrator schedules a shift, a shift card is created, and it has to show how many workers were requested. There are two ways to do this:

Type=Type5.png

A black badge with a person icon and the number of workers requested.

Shift Template Details.png

No badge. The number of workers requested shown next to a label reading 'No. of Staff Members Required'.

Final Design: Fewer Clicks, Fewer Cards

Scheduling Many Workers From a Single Shift Template

A new 'No. of Staff Members Required' drop-down on the shift-template form lets administrators specify how many workers a shift needs.

Calendar.png
Multi-Worker Shifts Now Collapse into a Single Shift Card

Multi-worker shifts now produce a single card. Administrators still need per-shift access to edit or cancel one worker's shift without touching the rest, so the individual cards remain behind a 'See All 30 Shifts' button.

Shift Template Details.png

Of the two design options I set out earlier, I went with the labelled field rather than the badge. The card can already show up to three badges from other shift-template settings, and a fourth would compete with them, so the worker count appears next to a label reading 'No. of Staff Members Required'.

High-Fidelity Prototype
What Did I Learn From This Project?

The redesigned multi-worker shift scheduling user flow has not been released yet. This section will be updated once it goes live.

bottom of page