This research and design project stemmed from a new technological capability that our development team had been working on for a few months. Previously, our products containing a high quantity of data analytics could send that data to only one source at a time, which was time-consuming and inefficient. Now, we were able to send the data one time, and have it surface in multiple places at once. This process was called "bulk extract". I was tasked with finding the best uses of this capability within our product suite, which was centered around increasing persistence and graduation rates for higher education students.
My role: UX Researcher/UX Designer
Goal: Discover ways to integrate new capabilities of bulk extract into existing desktop-based product suite, primarily with data from the Illume Courses product.
Users: College and university academic advisors, success coaches, administrators, and students
I consulted with several in-house subject matter experts to better understand the Illume Courses product, which was rich with user data, and learn how its insights could enhance our other products, both technically and conceptually. Our target audience for this application was college academic advisors and students who might use the data-informed course success indicators to assist in planning their degrees and course selections.
To do this I worked with colleagues across several departments, including software engineers, product managers, the VP of Product & Strategy, the Director of Strategic Planning and two product consultants who had direct client contact, and another UX Designer on my team.
The primary way the data in this product was surfaced was with a "course signal". These were graphical indicators of the student success data. These signals were "Yellow Flag", "Qualifier", "Challenge", and "Late Hurdle". They were based on a combination of grades and persistence rates of the average student taking a particular course. I determined through my research that these visual cues would be the most efficient way to communicate the data to our users.
Some of the questions I sought to answer:
After many conversations about how Courses worked, who it served, and what types of information it contained, I evaluated the other products we sold, and identified ways in which the data could enhance their usage.
As part of the design process, I sketched out a few concepts of how the data from Courses could be surfaced in our other products. (Click to enlarge)
As I gained a more thorough understanding of what type of data Courses contained, and how it impacted student success, I was able to develop a concept (shown below) of a flow of data-driven course signals throughout our product suite. (Click to enlarge)
Two of our product consultants had been college academic advisors prior to their roles at Civitas, so they had first-hand knowledge of the impact this information could have and how it could be implemented. I showed them the initial sketches I’d produced to illustrate my concept, and we discussed where improvements could be made and if my concepts were feasible in practice. Some notes from our conversation were as follows:
This is an example of how the data from Courses could be surfaced in Degree Map (the degree planning product). My main deliverable for this project was a full-color prototype featuring this concept as well as one from the administrative side of planning the degree requirements; however, it is not available for use outside the company. I presented the prototype to the VP of Product & Strategy, first for initial feedback and then again when I had refined the work. With her approval, I presented the prototype and a slide deck to the project manager for the Degree Map product for final review. (Click to enlarge)