Missouri S&T Web Lead UX Designer 2025

Updating the advising experience.

Academic advising at Missouri S&T was fragmented across systems that expected students to know how the institution worked. I restructured it as a continuous, guided experience: one place, one journey, one student at a time.

RoleLead UX Designer · also built the site
Surfaceadvising.mst.edu (live)
StackTerminalfour CMS
StatusShipped · usability testing planned
Competitive analysis of peer university advising sites, 1 of 3 Competitive analysis of peer university advising sites, 2 of 3 Competitive analysis of peer university advising sites, 3 of 3
Site-structure option 1 explored Site-structure option 2 explored Site-structure option 3 explored, organized by department
§01The problem

The system was the obstacle.

Students were expected to manage complex academic requirements across disconnected tools, with little guidance, leading to confusion around responsibilities, next steps, and ownership.

The core failure wasn’t usability. It was a lack of clarity and continuity across the system.

What broke down, specifically

Students struggled to find advising info. Content was scattered across multiple sites and systems. The previous advising.mst.edu only served a select group of students, but didn’t make that clear, so students often visited the wrong offices for their needs.

Information wasn’t organized in a way students understood. Content was structured around internal organization (colleges) rather than the way students actually think about themselves (their department or program).

This led to confusion and inefficiency. Students spent extra time searching, wandering, and ending up in the wrong places before finding what they needed.

§02My role

Lead UX Designer · also built the site.

Leadership and ownership

I led product design from discovery through implementation. As one of three designers at the university, I was responsible for ensuring the solution was clearly defined, executed, and delivered. I built the site myself in Terminalfour, the university CMS.

Cross-functional collaboration

I worked closely with faculty, department staff, and advisors to understand the advising process and align on a solution that balanced student needs with institutional requirements.

A research constraint, named honestly

We couldn’t conduct direct research with students; the project ran during finals week, and we deliberately chose not to involve students in the lead-up so they could focus. By the time the semester ended, the window had closed. Future iterations will involve student feedback.

§03The reframe

From “improve advising usability” to help students take the right action at the right time.

Improving advising wasn’t about adding more content. It required restructuring the experience to:

  • Centralize critical actions and information.
  • Guide students through key journeys: planning, registration, graduation.
  • Make responsibilities and deadlines explicit.
Help students take the right action at the right time without needing external support.
§04Research approach

Streamlined methods, meaningful signal.

Given the tight project timeline, I prioritized efficient, insight-driven methods instead of full-scale user testing.

Competitive analysis

I benchmarked against similar university advising sites to identify effective patterns and gaps.

  • Similarities: Most sites covered the essentials: advisor contact and appointments, degree planning, and academic support resources.
  • Differences: UMKC segmented navigation by user role (students, advisors, success coaches). UMSL included extensive resources like advisor outcomes and myConnect info. Mizzou focused more on grades and transcripts.
§05Navigating stakeholders

When information stops flowing, change the loop.

After early mockups and a competitive analysis, progress stalled. I didn’t have enough department-level detail to ensure the experience would meet each program’s needs. Many faculty members were hesitant to share details and concerned about the new site (understandable, but it left gaps).

Pivoting the approach

I consulted the VC of Student Success to surface essential advising info that applied to all students. Then I switched to a mockup-first feedback loop: I built a preliminary structure and shared it with faculty, asking them to correct inaccuracies rather than relying on proactive information gathering. That shift unblocked the project while keeping the design student-centered.

Preparing for buy-in

I prepared a slide deck outlining the proposed site structure and user experience to support alignment across departments. Although it wasn’t ultimately needed, it was ready for presentation to stakeholders if required.

§06Defining the site structure

Three options, one student-centered choice.

  • By College, a broad overview of each of the three colleges.
  • By College with Department Links, college-level info linking out to each department’s page.
  • By Department, every department listed directly, no need for students to know which college they belong to.

Heuristic evaluation

I ran each structure through a heuristic evaluation, judging it against the usability principles that matter most on a page students reach mid-task, usually stressed and after one specific answer: does the structure match how students actually think about their program, does it lean on recognition instead of forcing recall, and does it keep the path to the answer short?

Measured that way, the three separated cleanly. Both college-first structures assumed students know which of the three colleges their department sits under, and from earlier conversations with students, faculty, and staff, we knew many don’t. That turned a one-step task into a guess, and the version that only linked out to departments stacked extra clicks on top of it. Organizing by department removed the guess: students recognize their own program name on sight, so every advising page sat one clear choice from the hub.

Choosing the best student experience

So I organized the site by department. Each department got a dedicated advising page hosted on its own site, linked from the central advising hub, with advisor contact info, advising processes, and forms / important links. Centralized organization with departmental autonomy: a consistent shell, flexible content underneath.

The two moves it all came down to

Step back from the details, and the redesign rested on two structural decisions: consolidate advising into one destination, so students never had to work out which office or site owned their answer, and organize that destination around students, not the org chart. Everything else served those two.

§07Outcome

Live and in use.

The site is live at advising.mst.edu. Formal research and usability testing are planned for a future iteration to measure how students are navigating the experience and where it can keep getting better.

§08Reflection

What changed, in one sentence.

The biggest shift was moving from a system-centered structure to a student-centered journey.

Instead of expecting students to figure out the system, the experience now guides them through it.

If I continued this work

  • Personalization based on student progress.
  • Predictive guidance for upcoming requirements.
  • Better support for edge cases and non-traditional paths.
Say hi

I reply to most things.

uxmdoss@gmail.com LinkedIn →
Next case → Building an email toolkit for a university that designs its own emails. →