Problem Statement

It is really difficult to manage a large number of applicants who registered through multiple hiring drives organized by our company, ProGrad. It becomes very tedious to individually track applicants through every step of the process.

Highlights

Problem Statement

It is really difficult to manage a large number of applicants who registered through multiple hiring drives organized by our company, ProGrad. It becomes very tedious to individually track applicants through every step of the process.

Overview

About Organization

ProGrad is a tech school that aims to bridge the skill gap in the Indian IT space, enabling tech organizations to reach their talent objectives with a range of tailored talent hiring and training solutions.

Project Description

The ProGrad Hiring Platform is an application designed to help the internal team and our clients keep proper track of all the applicants who registered in any of the drives organized by my company. The ProGrad Hiring platform is a very powerful tool to track and modify an applicant's status based on their assessments. There are two access levels to this platform.

My Role

Researcher and Product Designer

Duration

July 2022 – October 2022

Tools Used

Figma, Whimsical, Trello, Google Docs

Project Timeline

How does ProGrad function?

The project started with initial insights from the stakeholders about what exactly they were looking for this product to achieve. We had multiple meetings in the span of almost 2 weeks to lay the foundation. The next step was looking for competitors, but we soon realized that the features we were trying to incorporate were case-specific. Still, we kept looking for some inspiration. Moving forward, we brainstormed the solutions and gave them shape by creating the information architecture and, simultaneously, the User Flows. After that, we started to work on designing Low-Fidelity wireframes. Once we had a basic structure, we again started taking feedback from the stakeholders so that we could be on the same page. After making certain rectifications, we eventually moved to High-Fidelity designing. Once the designing part was over, we focused on thoroughly testing our product with multiple users.

Discover

Stake Holder's Inputs

The project started with a meeting with the stakeholders where I received initial insights about what all features are primarily required and how are they planning to incorporate them to make a completely new platform. Below are some inputs that were given to me.

Pain point analysis

Right after getting an initial insight from stakeholders, we decided to gather the pain points that our internal team members had to go through without having a dedicated platform application tracking.

Define

User Journey Map

For the next step, I prepared a rough User Journey Map of both before the proposed platform and after the use of the platform. This will help me visually represent the experiences, emotions, and interactions of a user with a product we intend to create, providing insights into their pain points and opportunities for improvement, leading to better design and user satisfaction.

Ideate

White Boarding

After analyzing all the insights as well as pain points from the clients and internal team respectively, I decided to divide the platform into several sections depending on their functionality. To practically do this I created rough sketches of individual functionality keeping in mind, what all things are necessary for the functionality. Below are some snippets of some rough sketches for the same.

Information Architecture

It was really important for the platform to have seamless navigation, which will eventually save time for both the internal team and the client. Keeping that in mind and based on the rough structures that I made while whiteboarding, I created an Information architecture that segments all the functionality with clarity.

Design

Low Fidelity Wireframes

We had several meetings to finalize the structure of the website. Taking care of the accessibility, I created low-fidelity wireframes which gave us a sense of how the functionalities would be visually structured.

Feedbacks and Rectifications

After the completion of low-fidelity wireframes, I organized feedback sessions with my manager and the stakeholders and noted down the problems that they faced while navigating through the low-fidelity test prototype. We curated all the problems and rectified the ones that will reduce the pain points and improve the flow of the platform.

Style Guide

High Fidelity

Once, both the low fidelity as well as the style guide was ready, it was time to start with High Fidelity designs of the platform. While designing my primary aim was to reduce the unnecessary steps involved and to keep things as simple as I could so that the process would be seamless for the internal team as well as our clients who will be using it to track the applications of individual candidates.

Insights

Key Learnings

Future Plans

OverviewDiscoverDefineIdeateDesignInsights