Type: Performance Review Dashboard
Team: team of 3
Role: UX Designer – research and design for employee user flow
Timeframe: one week
Background: We were given the task to design a Performance Review software for 3 users – employee, supervisor, and HR.
RESEARCH + INSIGHTS
We interviewed a dozen people who’ve had performance reviews in the past. We noticed the interviewees had many similar issues with their performance review experience. The complaint with generalized feedback and lack of follow-up on past performance reviews was a pain point most interviewees talked about. They were also frustrated with how little
“I’m never sure how I’ve progressed [in my job].”
“My reviewer didn’t come in with any concrete examples of my work.”
“I can never remember my goals from previous meetings or find work [supporting] my performance [when I need to].”
Employees, HR reps, and supervisors all stressed their frustration with the current performance review process:
- Not personalized. Employees felt their performance reviews were generic and weren’t given fair assessments based on their personal strengths and weaknesses.
- Overlooked examples not being considered in the review process
- Not enough time and lacking
- Archaic system. Employees felt performance reviews were not about personal growth
We wanted to create a performance review software that allows of continuous feedback including:
- Ability to communicate between employees and their managers
- Comment and attachment feature for easy access to work examples throughout the performance review period, not just the week leading up to a meeting
The design team had a lot of discussion about what the most important sections we needed for the dashboard. It grew a few times before being trimmed back to the original set of five to help the employee track their reviews and goals and communicate with their supervisor.
The most important takeaway from this project was the focus on an MVP and specified user. Since the project was so vast – 3 different users and multiple tasks – in such a short amount of time, we needed to focus more of our effort to create a single user flow before trying to tackle other users.