← BACK

OVERVIEW

PROBLEMS SOLVED

FEATURES FOR FLOW

FINAL PRODUCT

CONTEXT

CONTEXT

The Path at Penn…

The Path at Penn

Path@Penn is the university's current portal for course planning and registration.

I redesigned the user journey to make it more personalized, productive, and pain-free.

I redesigned Path@Penn the university's portal for course planning/registration to fix friction in the user flow.

Path@Penn is Penn's current portal for course planning and registration.

I redesigned the user journey to make it more personalized, productive, and pain-free.

OVERVIEW

Path or puzzle?

Currently, building a schedule that all fits, all while meeting one's degree requirements looks like this:

Currently, building a schedule that works all while meeting degree requirements looks like this.

Interviews into affinity mapping

Interviews with current users revealed the following:

Affinity mapping current user pain points and pathways.

Affinity mapping current user pain points and pathways.

Heuristics highlight friction

Little flexibility, consistency, and error prevention when adding courses.

KEY INSIGHTS

01

"It feels outdated and hard to use"

"It's outdated and hard to use"

02

"I have to get insights from external resources"

03

"I don't use Path@Penn unless I absolutely need to"

How might we make Path@Penn more personalized, productive, and pain-free?

How might we make Path@Penn more personalized, productive, and pain-free?

How might we make Path@Penn more personalized, productive, and pain-free?

PROBLEMS SOLVED

Time out on time outs!

Time out on time outs!

After some time, Path@Penn would automatically sign the user out.

Especially when all course information and resources aren't centralized, reauthentication became a major pain point.

After some time, Path@Penn would automatically sign the user out.

Having to reauthenticate was a major pain point, especially when all course information and resources aren't centralized.

I made an Idle Timeout button to prevent this friction point. But to prevent session timeouts in the first place, I included all important info in one place:

I made an Idle Timeout button to reduce friction. But to prevent session timeouts in the first place, I included all important info in one place:

Especially when all course information and resources aren't centralized, reauthentication became a major pain point.

I made an Idle Timeout button to prevent this friction point. But to prevent session timeouts in the first place, I included all important info in one place:

Deadlines up front

Deadlines up front

A dynamic landing page that brings important deadlines front and center (literally).

Course alerts

A real-time notification system for open sections (during a first-come, first-served period).

Insights

Easily get the insights into the courses you need, eliminating the need for 20 other tabs.

FEATURES FOR FLOW

Parsing with Precision

Filtering involved a small, single-select dropdown for hundreds of options.

The Problem: filtering is currently a single-select dropdown for hundreds of options.

This required manually cross-referencing lists and tabs to find courses that "double-count".

Stackable Filters

A more navigable, scalable panel to select and stack multiple attributes simultaneously.

Filtering Through

An inclusive search bar that provides all possibilities but prioritizes courses that match the most filters applied.

Status Indicator

No more manual schedule-checking; stacked against the user's student's current schedule, the course displays its availability:

I eliminated manual schedule-checking; course stacked against the user's student's current schedule would display:

No more manual schedule-checking; stacked against the user's student's current schedule, the course displays its availability:

  • Green (open and fits schedule)

  • Yellow (open, but a time conflict)

  • Red (closed or restricted)

Responsive Feedback

Know the exact changes you're making to your schedule. Easily discern and correct any action you've taken.

REFLECTION

FINAL PRODUCT

Building for what's real

Working with developers involved lots of sprints, but . Aside from, I've learned HTML and CSS to lighten the load on my teammates.

Overcoming biases

Especially as swimmers

UX extends beyond UI

Navigating problem solving involved recognizing the social aspect of swim.