Catherine Hicks
User Experience and Product Design Professional

TriNet

TriNet is a professional employer organization headquartered in San Leandro, California. It provides HR outsourcing services, including payroll, health benefits, and human capital management for small business owners

Role & Project Summary

  •  Multiple Rates of Pay

  • The problem that needed to be addressed in the platform was the ability to pay different pay rates on different roles and/or different locations. For example, I am a server during the week and I am a hostess on the weekends.
  • This touched multiple points of the interface and needed to be thoughtfully and consistently built across all those touchpoints, which crossed many teams and product owners within the company.

Project Constraints

  • A streamlined process that addresses all the places that has all touchpoints across the platform
  • User is able to define multiple rates of pay for a single user who may have one or more job titles
  • The need of having multiple rates of pay came from a very high profile client. Since we handled payroll with single rates of pay already, the idea of adding others were already somewhat spelled out in concept, but not in detail. We did an audit of our platform to see where this would hit and put together a plan of how to implement the idea
  • Multiple rates of pay has many touch-points in the product and should all be easily accessible and usable based on current product functionality
  • We believe there is a use case where a single employee could have multiple rates of pays based on different roles they do for the organization and that because of this need we need to address this in the UI

Multiple Rates of Pay

Wireframes

Example

At the beginning of my design process I created wireframes for testing purposes.

Guiding Questions

  • Why was it useful to do this?
  • What kind of wireframes did you make?
  • Low fidelity or high fidelity?
  • What tool did you use for this?
  • Did you use them for testing?
  • How many iterations did you have?

Multiple Rates of Pay

Wireframes

Example

At the beginning of my design process I created wireframes for testing purposes.

Guiding Questions

  • Why was it useful to do this?
  • What kind of wireframes did you make?
  • Low fidelity or high fidelity?
  • What tool did you use for this?
  • Did you use them for testing?
  • How many iterations did you have?

Multiple Rates of Pay

Wireframes

Example

At the beginning of my design process I created wireframes for testing purposes.

Guiding Questions

  • Why was it useful to do this?
  • What kind of wireframes did you make?
  • Low fidelity or high fidelity?
  • What tool did you use for this?
  • Did you use them for testing?
  • How many iterations did you have?

Summary

  • What parts of the product does multiple rates of pay touch that we need to address
  • Job costing, user detail page, payroll, printed payroll checks
  • That an administrator can add multiple rates of a pay to a user in whatever way they would like and that it will follow them through the entire process from entry to payroll
  • Multiple rates of pay was a direct request from one of our largest customers. We made the assumption - and moved forward with it- because we believed that this could be beneficial to other customers as well
  • This project was moving forward without further validation due to the large scale of the customer requesting this, so unfortunately no further validation with users was asked for or allowed due to time constraints from those higher up than myself
  • Making sure we addressed all the places where multiple rates of pay would affect the product UI

  • Working alongside the main product owner on this feature, we did a page by page audit, determining all the places in the current version of the UI where changes would need to be made
  • Working with that many cooks in the kitchen was challenging, as each part of the product this feature touched had their own sets of needs and their own ways of working on their part of the product.
  • I would get the teams together and try to get them into alignment before the project kicked off instead of halfway through it - I believe it would have been less stressful if I had done that