The first thing I wanted to do was to identify the pain points that execs face during the hiring process. Are there any behavioural patterns that are shared between the execs that might induce specific pain points? This step is crucial in providing insights and context during the creation of Hireflow.

I initially interviewed 6 club execs, all within UBC Launch Pad and who are mostly university students. I asked questions mostly about their prior experience in recruiting new club members and was provided with the past Google Form question and responses to better understand the behavioural and technical pattern of the hiring process. Here are the results:
     • Creating and sorting through multiple spreadsheets is very “time-consuming” and “resource-intensive”
     • Scheduling an interview time that works for both parties is hard to manage
     • Manually sending decision email to applicants is ineffective
     • Google Forms and Sheets create a lot of duplication, is resource intensive and very prone to human error.
     • Scheduling an interview through a single Calendly account and migrating the appointments onto a spreadsheet is time-consuming and intensive

After compiling the data I have found from the research, I utilized Whimsical and began creating flowcharts to better visualize the end-to-end recruitment process for a clearer understanding of the pain points. I also created multiple case flows for the edge cases and also to identify which flow and/or feature works best for our project. Converting my research findings into a flowchart is very important as it allows me to tackle the problem more critically and systematically; visualisation is a very powerful method of processing mass data.

Afterwards, I began creating the end-to-end product flow using charts to make sure that I didn’t miss anything and that every feature integrates cohesively with each other. It’s very time-consuming to make a whole product flow alone, but it’s completely worth the time and effort as it’s going to tremendously help me in creating the lo-fi wireframe later on down the line.

Using Figma, we began creating the lo-fi wireframes to visualise what we had in mind. This step is necessary as it provides us with a rough estimate of what the outcome is going to look like. Moreover, since lo-fi wireframes are generally easier to create and fix, the developers can begin to visualise the development early.

With the lo-fi wireframes ready, we did a thorough user testing with the president of UBC Launch Pad, Rob, to hear his insights and feedback. Based on his crucial input, I then began modifying the wireframes to better accommodate UBC Launch Pad’s specific needs. More specifically, he wanted the pipeline shortened to be more effective and to have separate pages for the sorted and unsorted applicants.

With everything laid out and ready to go, I moved on to the (arguably) most fun phase of the whole design process: designing the Hi-Fi prototypes. Still utilizing Figma, I began bringing our wireframes to life with wonderful design entities such as: colors, illustrations, content writing, etc.