Saath

Better Reviews, Happier Employees
Tools
Time Period
Skills

2 weeks

Sketch | Miro | Principle

UX Research | Business Analysis | Data Analysis | User Flow | Wireframing | UI Design | Prototyping

Saath - Homepage

Project Overview
Performance Reviews are an important part of the HR process in any organization. It helps employees showcase their achievements and the management to understand what is going well and what could be better.

The goal of this project is to address the issues with performance reviews in professional organizations and understand how it can be made more effective.
UX Research

In order to identify the pain-points of users with respect to performance reviews, interviews and online surveys were conducted. The below displayed lean survey canvas gives us an idea of what information we are looking for from the research and the best way to approach users.

Lean Survey Canvas
Current Scenario

Data from UX Research

  • Currently, most companies follow manual review process with emails and excel sheets to track their goals, progress and feedback
  • Managers are expected to keep track of what their team is working on and report to their supervisors
  • ~40% of employees are unhappy with the current performance review process
  • Reviews happen only once a year. Hence managers are unable to keep track of year-round goals and achievements of their teams
  • The roles and responsibilities are not defined very clearly and there might be sudden change in plans and employees will have to cope with the same
  • Employees are unhappy with irregular promotions and benefits. Employee retention is an issue in most companies, specially startups
  • The system is subjective to individual managers and the employees do not feel heard or valued
  • The HR teams are mainly business-centric and do not have a relationship with individual employees after hiring process
  • As size of an organization increases, the HR processes become more complex and require better management systems

Data Analysis

The data collected from research is written on post-its and categorised for effective analysis into an affinity diagram, shown below.

User Personas

John - Primary

John is our primary user persona for whom the application is designed. He is a developer at a technical startup. His needs are

  • Efficient organization of his goals and tasks
  • Higher visibility of his achievements with his team and manager
  • Better engagement with his company and overall employee experience

Lena - Secondary

To further analyse the needs of the user, a user journey map was created. This map follows the primary persona, John throughout his performance review cycle and we can analyse the frustrations he would have (Touch-points) and consequently, the design opportunities for us to create a better product.

  • Tracking the progress of her team, their goals and achievements.
  • Maintaining effective communication with her team and the higher management
  • Increasing employee retention in the company

User Journey Map

To further analyse the needs of the user, a user journey map was created. This map follows the primary persona, John throughout his performance review cycle and we can analyse the frustrations he would have (Touch-points) and consequently, the design opportunities for us to create a better product.

Problem Statement
John needs an interactive performance review platform where he may track his goals and submit timely reviews so that he may experience an inclusive and effective engagement with the company management.
Hypotheses
We believe that having timely access to goals, tasks and status will result in effective project and team management.We will know this has been a success
  • For John when the reviews are performed quarterly instead of yearly
  • For John when the ratings he has given to himself and the ones given by his manager to him match in 50% of all the reviews in a year
  • For Managers when the team’s performance increases by 20% over three quarters
  • For HR teams when employee escalations against management decrease by 50%

We will know this has been a failure if the stakeholders have to invest more than 20% of their day to keep the tool updated.

The Solution
The analysis part of design illustrates all the possible solutions that can be developed as part of the product design.
MOSCOW Analysis | Work Flow | Mindmap | Sitemap
For the 1st iteration of the MVP (Minimum Viable Product), we will be going ahead with the following options.
  • Organization of goals and tasks -progress bar and reminders
  • Creation of goals and reviews
  • Approval of a goal
  • Adding approved goals to a review
  • Self-Rating and submitting a review for appraisal
  • Review timeline
  • Comment options to encourage communication between teams
  • 360 degree Feedback

Paper Prototype

Low-Fidelity prototypes provide an efficient way to sketch the ideas obtained from data analysis. The below prototype displays the structure of the interface.

Mid Fidelity Prototype

The below screens represent the initial structure of the platform. It has been worked on and has evolved into the high fidelity prototype displayed in the following section.

Prototype

The video displays a high fidelity prototype, complete with colours, type and functionality of the 1st iteration of the MVP.

Going Ahead...

The design doesn’t end here. Usability tests will be conducted and based on the results, further iterations shall follow.
Below are the steps to be implemented in the upcoming iterations of the design.

  • Develop feedback options on the platform - 360 degree and anonymous feedback
  • An HR interface
  • Performance and skill analysis
  • Team and settings page

---------

nextprevious

Let's connect

Reach me at sindhoo.kv@gmail.com