Engaging new employees with a human approach
For 2017, I was the designer on the Onboarding team, responsible for understanding the needs of new employees and delivering the experience for new hires.
DISCOVERY & CONCEPT
I worked with the product manager, developers, and a UX researcher to generate insights and create concepts to address customer needs.
DESIGN EXECUTION & ITERATION
I worked closely with my scrum teams to deliver wireframes, flows, and prototypes to execute features, as well as with a UX researcher to test, iterate, and refine the design before going to engineering.
Starting a new job is a significant change. We want to make it easier. Nothing stalls productivity like showing up for the first day of work and not actually being able to do anything because the logistics aren't set up or there's tons of onboarding paperwork to do.
How might we make the onboarding process more efficient and insightful?
To get a better picture of new employees, I went onsite to one of our clients to observe their onboarding process, and extrapolated out a generalized user journey. We also did exploratory research sessions on both employees and practitioners, which yielded the following insights:
one in two HR practitioners felt their onboarding process was “somewhat structured” to “not-at-all” structured.
New Hires are anxious their first day of work and want to feel like everythings okay.
Practitioners and managers want to share their company culture and way of doing things with their new hires.
Spark a Connection
Both new hires and managers want to build a relationship with each other and the company.
Managers and practitioners need to ensure that the new hires complete the required paperwork.
Time Sensitive Paperwork
Some paperwork, such as Form I-9, must be completed in a set time frame or else new hires are not able to work.
Our product team would say things like:
We used UX KPIs to align on feature objectives and to measure how a specific feature achieves its strategic and functional goals over time. The three qualitative KPIs we chose were:
Does this help you make a decision?
How helpful the information provided to the user is in making decisions.
Was it clear, fast, and easy?
How much time, effort and training is required to successfully complete a task.
Was it useful? Will you use it again?
How many users have opted to use a feature within a given time period.
Now we changed the conversation to a common objective:
Reduced average time on task by ~5 min (33%)
Simplified number of states in flow from 40 to 25
Reduced average number of clicks to completion by 30%