Prime Digital Academy

Prime Digital Academy is a bootcamp-style program that trains designers and developers for careers in the technology industry. Every cohort at Prime Digital Academy experiences a Career Day event in the final week of their program, and the Community Relations and Operations Manager (CROM) at Prime is responsible for creating the master schedule for the day.

To create this schedule, the CROM must match students and interviewing companies based on their personal knowledge of individuals' skills. The current system includes holding information in scattered places, including Google Docs, Google Spreadsheets, Gmail, on paper, and on a whiteboard.

Prime wanted to simplify the process for their CROM by digitizing and centralizing as much as possible, so they asked my cohort of UX students to design their own solutions. We conducted research as a collective, then created solutions individually.

Directed Storytelling

To begin the project, we conducted a session with the user, the CROM, where she explained her current process. This included a walkthrough of the timeline and tasks involved and showing the various artifacts and where in the process they were involved (including mentally-stored information).

Journey Map

After getting a grasp on the process directly from the primary user, I created a journey map to highlight the touch points between Prime staff, students, and hiring partners. Creating this map also highlighted some of the more egregious pain points in the process, including all the different storage and communication avenues.

Feature Cards & Kano Analysis

We came up with feature cards of wireframes that would solve some of these pain points. These were designed individually and then brought together as a group for user testing.

All the feature cards were incorporated into a Kano analysis survey, where primary and secondary users rated the features according to their necessity in the application.

Development Scoping

In order to provide constraints and a scope of work for the project, we spoke with a developer who provided timeline estimates for the various features we had come up with. We were then told that our final designs should account for only 400 hours of development time. Fortunately, Prime already had an existing administration portal and databases that we would be working with.


As a final piece of research, we conducted a contextual inquiry as the CROM made the whiteboard schedule. We observed her process from start to finish to ensure that our designs would match the mental model she already had for this step.