Your Earnings
πŸ’Έ

Your Earnings

Product

"Your Earnings" flow in the Orka Works app

Timeline

1 Week

My Role

Product Designer

UX Designer

UI Designer

Toolstack

icon
Miro
icon
Typeform
icon
Notion
icon
Figma
icon
Maze

Problem Space

πŸ™β€β™‚οΈ
Problem: Workers are getting confused when looking at their pay in the app. It's not clear when they are getting paid and what work is included in that cycle. It is also confusing why their instant pay balance changes.

Step 1 - Empathy

My goal during the empathise phase is to:

  1. Learn how our workers use the pay page. What do they check? Where is the value?
  2. What are the current problems they have with the pay page?
  3. Uncover what information is needed for users to be able to understand their pay cycles better

By building these objectives, I can ensure I ask theΒ rightΒ types of questions, helping me gather accurate data that can be synthesized to form a problem statement.

User Surveys

I created a survey in Typeform and sent it to a number of different workers through Intercom

Step 2 - Define the problem

As a worker I need to be able to clearly see the next date that I am due to be paid

As a worker I need to know how much I am expected to be paid

As worker I want to know when I am getting paid for the shifts I work

As a worker I want to know how much I'm being paid for each shift that I work

As a worker I need to know how long I have to use the Instant Pay facility before my pay gets processed and my balance changes

As a worker I need to know the fees I will be charged using Instant Pay

⭐
Early Hypothesis: We can create monthly in-app payslips by grouping pay from work into the paydate the work falls on. We can display the gross pay for that paydate as well as the money available to withdraw from instant pay. This will make it clearer how much they are being paid, when they are getting paid, how much of it can they withdraw through instant pay and the cut off date.

Step 3 - Ideation

Crazy 8's

image

Customer Journey Map

To better understand what the user is trying to achieve and what they are thinking each step along the way, I created a customer journey map.

image

Step 4 - Rapid Prototyping

Step 5 - Testing

πŸ”¬
User Research

NameDateInterviewerTypeTaskStatus
πŸ™‹β€β™‚οΈ
Josh
October 9, 2020
Connor Ashton
General Feedback
Your Earnings
Completed
πŸ™‹β€β™€οΈ
Jordan
October 9, 2020
Connor Ashton
Testing Session
Your Earnings
Completed
πŸ™‹β€β™‚οΈ
Darren
October 9, 2020
Connor Ashton
Testing Session
Your Earnings
Completed
πŸ™‹β€β™€οΈ
Philippa
October 8, 2020
Connor Ashton
Testing Session
Your Earnings
Completed
πŸ™‹β€β™€οΈ
Amber
October 9, 2020
Connor Ashton
General Feedback
Your Earnings
Completed

I also sent out a Maze.design un-moderated test to get some additional feedback from our current users

Step 6 – Prototype V2

πŸ’‘
After the initial round of user testing I updated the prototype based off problems that arose through the testing sessions and general feedback. There were a few additional edge cases I designed for as well.

Outcome

πŸš€
Outcomes: We expect to see the number of pay related queries community receive decrease substantially.
β€£
How to measure this outcome?
  1. Ask community to work out the % of our user base that has sent in pay related queries in a 7 day period leading up to the paydate before the updated Pay page design was introduced
  2. Ask community to work out the % of our user base that has sent in pay related queries in a 7 day period leading up to the paydate after the updated Pay page design was introduced