Rethinking Class Planning

Designing the mobile experience of a class planning tool for 20,000+ BYU-Idaho students

Registering for classes at BYU-Idaho confused and frustrated students, especially freshmen. I joined a small design team to build a planning tool from the ground up, and owned its full mobile experience.

Industry &
Business Model
Industry & Business Model

EdTech, B2C

Role

UX Designer

Team

UX Manager, 2 Designers, Engineers

Duration

May 2023 - Aug 2023

The schedule builder on a laptop and a phone
The problem

Students were planning their semesters on paper

The problem

Students were planning their semesters on paper

The problem

Students were planning their semesters on paper

BYU-Idaho’s registration system was outdated and hard to navigate. Freshmen often needed help just to register, and most students found it daunting to build a balanced schedule. The most proactive students wrote their planned sections on paper before registering to see how their options fit together. Stakeholders also knew some courses filled faster than expected, leaving students to rework their plans and still graduate on time.

Before the tool:
The old registration search

Hard to navigate

Students struggled to find their way through the old registration search.

A student's handwritten notes planning a semester

Planned on paper

So they took notes by hand to keep track of their options.

The old registration search
A student's handwritten notes planning a semester
Before the tool:

Hard to navigate

Students struggled to find their way through the old registration search.

Planned on paper

So they took notes by hand to keep track of their options.

Context

Joining a project already in motion

Context

Joining a project already in motion

Context

Joining a project already in motion

The tool was proposed to make planning each semester easier and less stressful. When I joined, stakeholders had set what it should do, and the design team had already interviewed students, compared how other universities handle registration, and created and tested very early prototypes.

Ownership

Filling the gap when two of three designers left

Ownership

Filling the gap when two of three designers left

Ownership

Filling the gap when two of three designers left

I joined to carry the prototype forward through iteration. Two of the three designers on the project had just left, so I worked out much of the direction myself, with quick help from my manager and the remaining designer.

I started from the stakeholder requirements and user requests below, and wrote a How Might We statement to keep us aimed at the overarching problem.

Stakeholder requirements

Ability to plan classes all in one tool

Easy experience so all students can use

Registering for classes is easier

Better indication of course demand through viewing students’ plans sooner

Notifications to let students know of relevant changes

User requests

Display of key class information for quick comparisons

Easier registration process

Less stress and scrambling on registration day

Help to plan a more balanced schedule

How might we

Make class planning and registration easier for students, so that they can build more balanced schedules for greater success?

Make class planning and registration easier for students, so that they can build more balanced schedules for greater success?

What will happen when a student’s planned class becomes full?

This question came up in my second week. Students used to build their schedule on registration day, but our tool asked them to plan far ahead, so a planned class could fill up before they registered. I realized that helping users find promising alternate solutions after they had created a plan would make or break the experience, so I brought our UX manager and the other designer together to map every warning and error and how a student could respond.

A timeline of what could go wrong from pre-registration through the add/drop deadline
When a class fills up:

Across the timeline

Across the timeline

What could go wrong at each stage, from pre-registration through the add/drop deadline.

What could go wrong at each stage, from pre-registration through the add/drop deadline.

Errors, named early

Errors, named early

Time conflicts, missing prerequisites and full or filling sections, each flagged with a notification.

Time conflicts, missing prerequisites and full or filling sections, each flagged with a notification.

A way forward

A way forward

Waitlists and plan alternatives, so a full class never left a student stuck.

Waitlists and plan alternatives, so a full class never left a student stuck.

What testing changed

Showing next steps where students already were

What testing changed

Showing next steps where students already were

What testing changed

Showing next steps where students already were

We tested from low-fidelity wireframes onward: 12 rounds of usability testing and 60+ tests. Here are three parts of the tool I worked on, and what testing changed in each.

Photos from testing on campus: Raphael's UX designer badge, a student trying the prototype on a laptop, and the student center where sessions ran

Adding courses to the schedule

The other designer and I built a visual schedule builder, because students couldn’t “see” their schedule while planning it. Here’s what students told us.

The tested course list, where students tried to drag courses onto the calendar
Tested

Tiles looked draggable

Tiles looked draggable

Students tried to drag courses onto the calendar, so we added a signifier for clicking.

Students tried to drag courses onto the calendar, so we added a signifier for clicking.

Keep needed features, ditch the rest

Keep needed features, ditch the rest

We added a button for courses outside the Grad Plan and removed the unused backup plan.

We added a button for courses outside the Grad Plan and removed the unused backup plan.

Credits got missed

Credits got missed

Students didn’t notice their planned credits, so we made the count more prominent.

Students didn’t notice their planned credits, so we made the count more prominent.

A course in the list on hover, with a pointer and arrow showing it can be clicked
Revised design

A click cue on hover

A click cue on hover

Hovering over a course in the list shows a pointer and an arrow that signal clicking.

Hovering over a course in the list shows a pointer and an arrow that signal clicking.

Add courses, no backup plan

Add courses, no backup plan

An “Add Course to List” button brings in courses outside the Grad Plan, and the backup plan is gone.

An “Add Course to List” button brings in courses outside the Grad Plan, and the backup plan is gone.

Credits in the header

Credits in the header

Planned credits now sit in the header, with a label like “Part Time Student” beside them.

Planned credits now sit in the header, with a label like “Part Time Student” beside them.

The class summary

This part took the longest. After planning, students had two next steps: resolve any warnings, like a planned section filling up, and register on their registration date. While the other designer refined the schedule builder, I explored summary page layouts to walk students through both. The feedback below comes from several of those layouts, shown on one for simplicity.

The tested class summary page with next steps students skipped
Tested

Planning isn’t registering

Planning isn’t registering

Many students skipped the next-step message and thought they’d already registered.

Many students skipped the next-step message and thought they’d already registered.

Too much on screen

Too much on screen

Students ignored the tabs and hesitated at cluttered tiles, so we merged pages and simplified.

Students ignored the tabs and hesitated at cluttered tiles, so we merged pages and simplified.

Full classes stalled students

Full classes stalled students

When a planned class filled up, the vague “Review” left students unsure what to do.

When a planned class filled up, the vague “Review” left students unsure what to do.

Three students working through the prototype on laptops in the student center

Abandoning the summary page

Students didn’t need a separate page for next steps. They needed them on the schedule builder they were already using. Each round of testing showed me why an earlier layout fell short, which led to the final design below. With next steps on the schedule builder, students could see there was more to do after planning, and the confusion about registering seemed to fade.

Final design

Registration status up top

“Registered Credits” sits beside planned credits, next to a “My Registration” button.

One page, no tabs

The summary tabs are gone, and waitlist warnings show right on the schedule builder.

A clear next step

A full section offers “Join Waitlist”, with other open sections listed below it.

Getting started

The last piece to figure out was getting students started. They could plan their schedule themselves or begin with one auto-generated from their courses.

The tested intro screen students skipped past
Tested

The intro went unread

The intro went unread

Students went straight to the buttons, so the calendar itself became the introduction.

Students went straight to the buttons, so the calendar itself became the introduction.

“Manually” scared people off

“Manually” scared people off

Students wanted to plan themselves but most picked auto-generate, so planning yourself became the default.

Students wanted to plan themselves but most picked auto-generate, so planning yourself became the default.

One page, not two

One page, not two

Without a schedule to see yet, this screen confused students, so we merged it into planning.

Without a schedule to see yet, this screen confused students, so we merged it into planning.

Revised design

The calendar comes first

Students land straight on the weekly calendar, with their course list beside it.

Planning yourself by default

“Auto-Schedule” is now an optional button that opens a short preferences dialog.

One page, no welcome

The welcome screen is gone, and the course list and calendar share one page.

Mobile

Building mobile planning around the calendar

Mobile

Building mobile planning around the calendar

Mobile

Building mobile planning around the calendar

Once the flow was solid, I took on the full mobile prototype. The features were the same, but the smaller screen meant rethinking much of the interface.

I studied Outlook, Google Calendar and iPhone’s Calendar to see how mobile calendars differ from desktop. In all three, the calendar is the primary page, and a secondary overlay is used to add items to the calendar, with a hamburger menu for navigation. I followed the same model: on mobile, the weekly calendar is the main planning view, and students add courses from an overlay.

The mobile schedule: the weekly calendar fills the screen, with sections in an overlay
Mobile planning:

The week at a glance

The weekly calendar fills the screen, with planned and registered credits up top and Register easy to access.

Sections in an overlay

The + button opens a sheet to compare sections, check open seats and register, with the calendar still behind it.

Everything else in the menu

Week, day and map views, My Registration and the Grad Plan sit behind the hamburger menu.

Dashboard

Giving students a high-level view of every semester

I also designed the dashboard students land on before they plan. I wanted it to be a quick, high-level read, so the next upcoming semester carries the main call to action, with past and later semesters still in view. Their declared plan from Grad Planner and their track sit at the top, so even newer students know which semesters to plan for. Feedback before handoff led to a few refinements, and it shipped with the beta as designed.

From start to finish:

1. Start on the dashboard

Students see every semester and begin planning the next one.

2. Choose sections

Students compare a course’s sections beside their weekly calendar.

3. Leave with a full schedule

A complete week, with each class ready to register.

Foundations

Adding mobile calendar rules to the design system

Foundations

Adding mobile calendar rules to the design system

Foundations

Adding mobile calendar rules to the design system

Our team was revamping BYU-Idaho’s design system during this project. Organizing and standardizing it was one of my major contributions, and buttons and other components got major overhauls along the way. The mobile calendar rules I set for this project became part of the system.

Delivery

Documenting the mobile flows for an outside dev team

Delivery

Documenting the mobile flows for an outside dev team

Delivery

Documenting the mobile flows for an outside dev team

After four months, we handed the tool to an outside development company we’d met with throughout the project for input on our concepts and design decisions. We documented the designs with user stories, and I documented the mobile flows. The tool launched in beta to 6,000 incoming freshmen before its campus-wide rollout.

The result

Launching to 6,000 freshmen in beta

The result

Launching to 6,000 freshmen in beta

The result

Launching to 6,000 freshmen in beta

The launch

20,000+

Campus students the tool was built for

6,000

Freshmen in the beta launch

↳ How we tested it

12

Rounds of usability testing

60+

Usability tests across the project

The schedule builder on a laptop and phone on a blue blanket
Reflection

Holding my designs loosely

Reflection

Holding my designs loosely

Reflection

Holding my designs loosely

The biggest lesson here came from the work I let go of. The summary page took longer than anything else I designed, and testing kept showing me it wasn’t working. Moving next steps onto the schedule builder was the turning point, and it taught me to trust how users work over what I’ve already built.

The tool launched to 6,000 freshmen and then across campus, and it made registering for classes easier for real students. That’s the kind of impact I want my work to keep having.

Looking for a stellar designer? Let’s chat!

Looking for a stellar designer? Let’s chat!

Looking for a stellar designer? Let’s chat!

Raphael Monaghan

Raphael Monaghan

Product Designer

© 2026 All rights reserved

Raphael Monaghan

Raphael Monaghan

Product Designer

© 2026 All rights reserved