Justworks Time Tracking Mobile App

Driving innovation in the affiliate commerce content space by fostering intent-driven shopping behavior.

As the first designer on the team, I led the efforts on a more efficient time-tracking experience for our worksite employees, in support of our vertical expansion initiative.

Context & goal

A few years ago, Justworks acquired a mobile time-tracking solution to start reaching customers beyond white-collar businesses.
As winning customers in new verticals became a strategic priority again, our team worked on streamlining the UX of the mobile app, which hourly employees rely on for recording time to get compensated.

Having acquired the time-tracking app, Justworks also started building a mobile app focusing on HRIS tasks (think benefits and payroll). Managing two apps quickly became a pain point for admins and employees, so we also had a goal of introducing the look and feel of Justworks so as to prepare for consolidation into a single app.

Solution

Smart defaults and autofills

The app now leverages geolocation to autofill employee's location when they're in range, so that they can quickly get started at their actual job.  Hover to see an illustration of the before/after flows:

Before

After

Improved hierarchy and way-finding

The new design helps employees understand where they are in the system with differentiation between shift states. I also brought in some updated brand elements to freshen the UI.

Before

After

Modern patterns and flattened navigation

We consolidated forms and introduced bottom sheets for contextual editing to prevent the fatigue of having to navigate back and forth to complete form edits.

Before

After

Business Impact

Besides time saved for our customers' workforce, aligning with the mobile team early on on sharing components set ourselves up for success when it came to app consolidation.

Key Design Contribution

Drive alignment across functions and teams

I conducted a workflow audit and presented my findings and recommendations to the team. I then collaborated with my partners to sequence the opportunities we aligned on. From here, our engineers were able to start planning a concurrent back-end refactor.

Visualize the technicals

One opportunity I identified through my audit was autofilling selections leveraging mobile native capabilities, such as filling in user's location with geolocation (vs them going through a long list) . I mapped out the possible scenarios and worked closely with my engineers on refining the logic.

Drive data-informed decisions

I used a mix of qualitative and quantitative research methods (survey, concept testing, usability studies, product analytics) to help improve our confidence level in the design directions.

Balance consistency, feasibility and brand expressions

As is the case for most projects, getting to the final designs involved a lot of negotiations. I had regular touch points with both the Mobile Platform team and our brand department, which kept me close to new development on our component library and its constraints, and gave me insights into the evolution of our visual identity.
Another big consideration was thoughtful change management. From a design perspective, I was constantly balancing the old vs new look and feel so that we don't shock our users each time we introduce a change; I also collaborated with my product manager to sequence the releases so that our product marketing manager could plan for customer communications accordingly.
Here are some samples of how the designs evolved.