case study:

Prime Career Day Application

Creating a solution for planning Career Day at Prime.

My team worked with the staff at Prime Digital Academy to design an application for Career Day, an event put on for each group of graduating students. The event brings in potential employers and business partners and gives them the opportunity to interview the students. 


The Challenge

Career Day at Prime takes multiple weeks to plan. The current process involves numerous technologies and many of the tasks are left in the hands of only a few staff members at Prime.

My Challenge was to design an application that creates a more seamless experience for all groups involved in the Career Day event and alleviate the pain points for the Prime Staff.

The Approach

I started by attending a meeting between the Prime Staff and graduating students. I took notes to better understand the view points of both students and staff on what went into planning the event. I conducted a contextual inquiry of the current processes used to manage Career Day.

I created a Journey Map to help illustrate the current process and highlight pain points that would need to be focused on. I proposed design solutions based on the information I was able to gather and met with a developer to get an understanding on how many hours each feature would take to build. 

I conducted a Kano Analysis of the proposed features. I was able to take the results from the analysis and create annotated wireframes & task flows. Finally, I proposed those features, as well as stretch goals for future features to implement.


Contextual Inquiry

The first step in this project was to conduct a contextual inquiry of the current process used in managing the event. Through this method, I was able to discover three groups involved in Career Day.

  • Prime Staff

  • Students

  • Partners (Companies & Recruiters)

The current process involves emails, spreadsheets, and whiteboards. With all of these different technologies and touch points, it becomes hard to manage for the staff involved in putting on the event.

 

 

IMG_0017.JPG

Journey Map

 

I created a Journey Map after doing my initial research to understand how the current process is done. It displays the steps taken and the touch points between the three groups involved and different technologies used. It also highlights some of the main pain-points that the Prime Staff encounters.

One of the biggest points of concern that I wanted to focus on was creating the interview schedule on a whiteboard. The students provide a list of the top five companies they are interested in meeting with and the partners have certain considerations (4-year degree, front-end/back-end development, etc) that must be planned for. All of this information is juggled between different platforms and must be referenced when creating the interview schedule. Also, partners will drop-out and be added to the interview schedule all the way up to the morning of Career Day, causing changes and re-ordering. 

 

Proposed Features

After creating a Journey Map, I created a list of eight proposed features that would help solve some of the main pain-points I wanted to focus on.

  • Auto-Schedule Emails

  • Consideration Hashtags

  • Auto-Populate Schedule

  • Print Interview Schedule

  • Events Calendar

  • Cohort Homepages

  • Student Profile Pages

  • Partner Profile Pages

After meeting with a developer, I was able to gather information on how many hours each feature would take to build. We were allotted 400 hours for the developers to use. Many of the features would need to be modified and rearranged in priority to fit within our constraints.

1.jpg

Kano Analysis

Using three Prime Staff members, I created an analysis that would help determine the level of satisfaction each feature instills.

The staff looked at each scenario/feature and answered the questions: "How would you feel if this feature was present?" and "How would you feel if this feature was absent?"

The staff rated each question from "I like it" to "I dislike it". This way the features could easily be put into three categories:

  • Table-stake (must-have)

  • Incremental (more is better)

  • Delighter (unexpected)

2.jpg

 

Annotated Wireframes & Task Flows

Once I received the feedback from the analysis, I created annotated wireframes & task flows of the following features: 

  • Administration Login

  • Student/Partner Login

  • Partner Profile Page

  • Student Profile Page

  • Cohort Dashboard (Homepage)

  • Integrated Media Kit

  • Interview Schedule Builder

  • Click/Click Functionality

  • Interview Number Card

  • Error Prevention

  • Partner Management

  • Add to Cohort

  • View Old Cohort


These wireframes & task flows showed the interactions necessary to execute each feature I was looking to implement.

 

Stretch Goals

Some of the features that I wasn't able to implement in the original plan could be implemented at future dates. To do this, I made sure to document the next steps and goals of each feature:

  • Preference Connection

  • Considerations

  • Top 5 Hover State

These features fit into the "Delighter" category of the Kano Analysis, meaning they weren't expected or necessary but could help enhance the application. 

9.jpg

 

Conclusion

This project was a great opportunity to branch out of re-designs and start a design project from scratch. The features that were originally proposed had to be modified or changed and the limitations of the development hours made this project a challenge and taught me to be flexible and think quickly. Using the contextual inquiry and journey map created a great framework to focus the design on. The Kano Analysis was a great opportunity to get real feedback from actual users and and help decide which features would be the focus and which could be implemented as stretch goals.