top of page

STAFFLY

Group 3.png

How might we increase employee control over work life and simplify shift management?

Overview

Staffly was a project to create an internal product that ultimately increased control over work schedules, whilst maintaining functionality for higher level management in terms of HR and approvals. The final product increased casual staff shift approvals by 40% compared to historic clock in/out methods.

Goals

  • Increase shift approvals for weekly casual shifts

  • Collate management tasks to one platform​

  • Decrease the need for secondary communication channels 

Specifics

  • Product Design (UX/UI)

  • 3 weeks

  • Internal Platform

  • Team - UX Designer, Developers, Project Manager

The problem

Approving worked shifts was a cumbersome and time consuming experience utilizing old clock in/out methods; with close to 50% of shifts not accounted for using finger print scanning products.

 

In order to increase the self sufficiency of staff clockings we needed an internal platform that provided access to shift approvals from both inside and outside of general work hours.

Researching the users

In order to create a useful product we needed a deeper understanding of what our users required.

We conducted user interviews to understand the wants and needs of our user base.

windows-kRWY72TKB0Y-unsplash.jpg

I forgot to take photos of my interviews but this is how they usually pan out

The divide

The results of our interviews showed the emergence of two different user groups and a divide in what they wanted out of the product. 

In response, we broadened our research efforts and targeted the groups individually for various rounds of discovery sessions

Senior Staff Members/

Management

Casual/Junior Staff Members

Crafting the personas

Following our research efforts and our discovery of the divide in user needs we crafted two main personas based on these different user groups

Persona 1 - The Manager.png
Persona 2 - The Casual.png

Key Design Considerations

With the breadth of information that was gathered we continued to synthesise the data

We translated our research into design considerations for our user groups

Multi-level access is required for different levels of staff authority

Clockings and shift approvals are the highest priority for our users

Access to payroll information (timesheets, payslips, leave balances)

Roster viewing and integration is required

Implement communication channel access through the product

Let's talk platform

Ultimately a mobile product was decided upon due to insights around staff usability. 

 

Considerations had to be made for integration with current desktop software for payroll, HR and record keeping.   

Going with the (user) flow 

Now that we had an idea of the product we required it was time to map out the user flow and iterate on the architecture of the product.

A note for devs:

We incorporated considerations for various screen states to ensure we designed for the full UI stack and eased back and forth during development

Staffly UI flow.png

Getting wired

Having mapped out the architecture of the site it was time to start sketching and developing wireframes. 

wires.PNG

What else?

Early tests on the mid-fi prototype yielded some interesting results for iterations

Surprisingly, a map function was a high priority for both user groups due to changing shift locations

This, including other insights were used to further refine the design. Including the restructure of the hierarchy of some pages.

Group 25 (2).png

Through to Hifi

After taking the designs through to high fidelity and producing a prototype that was loved by users we got the green light!

Display.png

Outcomes

(Projected)

40% increase in post shift clockings

Successful integration of communication channels

Intergrated work task into a single platform

bottom of page