Meow! I’m Cleo, Vinu’s head of quality checks. Got 2 minutes? I’ll tell you the story of the uoZone usability study.
uoZone in 2 minutes
Audio overview · problem, research & findings
2:08

Usability Evaluation

Students can’t find their own degree on uoZone

Six everyday tasks, five first-year students, and what happened when they got lost on the University of Ottawa’s student portal.

5

Participants

6

tasks

18

trends identified

9

issues identified across 5 themes

16

recommendations to improve UX

Overview

Role

UX Researcher

Method

Remote moderated usability test

Participants

5 students

Team

5 researchers

Tool

Loop11

Tested Device

Desktop

Session

30–45 minutes

Timeline

February 2026

Context

uoZone is the University of Ottawa’s student portal: enrolment, transcripts, exam schedules, volunteer placements. Its users include undergraduate, graduate, PhD and external students.

What they need is simple: find the right information quickly and accurately, or learn that it isn’t there.

The Problem

🚨 Students struggle to efficiently find academic information such as degree requirements and exam schedules on uoZone.

🔍 Research question: where exactly does finding things break down, and why?

What getting lost looks like

One participant’s real click path while trying to request a co-curricular record (Task 6). They left uoZone for Google, found a guide, came back, reached the right page, and still couldn’t work out how to request the report.

Applications

›

What-if reports

›

Applications

›

Work study nav.

›

Applications

›

Home

›

Google search

›

Get your CCR guide

›

Applications

›

CEN

›

CCR

›

Home

›

Back

›

Back

›

Back

›

…

💬 “I feel lost. I have no idea how to request the report. Really difficult to do. I feel uncomfortable performing this task.”

How we tested it

1. Scope and task design

We turned our objectives into six task scenarios that reflect common student goals, covering both navigation and comprehension.

2. Sessions

Remote, moderated sessions with think-aloud and neutral facilitation. We used one script for every session so tasks stayed comparable, and closed with a short debrief.

3. Measurement

ISO-aligned measures: task outcome (success, success with hint, fail), time on task, and satisfaction from reactions, comments and a System Usability Scale questionnaire. We logged every error and prioritised issues by severity.


🎯 Choosing the right people

A screener questionnaire recruited current uOttawa students with low to moderate uoZone familiarity, mostly in their first year.

We deliberately excluded very familiar users and anyone with a very positive attitude toward uoZone. Experts work around design flaws, and fans forgive them. We wanted the people who would hit the problems.

All participants consented to screen and audio recording.

The six tasks

Task 1

View degree progress and remaining courses

All 5 left the expected path

Task 2

Find your unofficial transcript

5/5 succeeded, all said too many steps

Task 3

Find where to change your preferred name

4/5 found it difficult

Task 4

View this semester’s exam schedule

2/5 unsure what the page told them

Task 5

Register for volunteer work

100% abandoned

Task 6

Request your co-curricular record (CCR)

1/5 completed

What we found

Across 30 task attempts, three patterns explained most of the trouble. Overall, 18 trends identified.

0/5

noticed 'My Academic Requirements' shortcut

The thing students needed was on the page, and nobody saw it

In Task 1, none of the five participants noticed the 'My Academic Requirements' shortcut. Four went through Applications, then Enroll, because they think of degree progress as part of course enrolment. All five left the expected path at least once, and three turned to the general program website instead.

100%

abandoned volunteer registration

When browsing fails, students leave

Nobody completed volunteer registration in Task 5: four of five rated it extremely difficult and two switched to Google. In Task 6, 40% of participants went through 13 or more pages before finding the CCR page, and one reached 17.

Every participant’s first click was Applications, so students know where to look.

The page itself fails them: an overcrowded list, an “Other” bucket, and a Co-Curricular Record behind an abbreviation.

💬 “I need to look through a thousand buttons on the application again and again.”

💬 “I probably just go Google.”

5/5

said that the transcript took more steps than expected

Even success felt uncertain

Everyone found the unofficial transcript, yet all five said it took more steps than expected, and many hesitated after clicking “View Report” because the page gave little sign that anything was happening.

In Task 4, the two students with no exams saw only “An exam schedule is not available for this term” and couldn’t tell whether the page was broken or empty.

Labels added to the confusion: in Task 3, only one of five strongly agreed that menu names were clear.

Recommendations

Nine issues in five themes, ranked by severity. Each came with a mock-up of the proposed direction.

Navigation and information architecture

1.1

Critical

Degree progress is hard to locate

Add a clickable progress indicator to the uoZone homepage, showing overall and per-category progress visually, as a percentage, and as credits completed against needed.

1.2

Major

Students link degree progress only to course enrolment

Meet their mental model: show remaining and completed courses early inside the enrolment flow.

1.3

Major

The 'Applications' page is overcrowded

Show grouped applications by default and break the “Other” bucket into logical groups.

Findability and discoverability

2.1

Critical

The Co-Curricular Record is buried

Create a “Career, Experiential Learning & Volunteering” category in 'Applications' page with a clear primary path that doesn’t depend on external guides.

2.2

Critical

“Request Official CCR” button can’t be found

Move action buttons out of the left-side 'Options' menu and place them directly under the CCR tab header.

Labelling and terminology

3.1

Major

Abbreviations reduce clarity

Spell it out: “Co-curricular Record (CCR).”

3.2

Major

“Advisement Report” means little to students

Rename it in student language, such as “View My Academic Requirements Report.”

Visual hierarchy and efficiency

4

Major

Accordions increase interaction cost when reviewing degree requirements

Auto-expand incomplete sections and visually distinguish complete versus incomplete categories with colour, icons and banners.

Feedback and system status

5

Major

An empty exam page for system feedback is unclear when no exams are scheduled. It reads like an error.

Replace the message with a clear status-oriented statement: “You currently have no exams scheduled for this term.”

Project Retrospective

The core problem is not that uoZone lacks features. Students can’t find them. Information architecture, ambiguous labels, weak visual signals and non-actionable messages all push the same way, until students give up and use Google instead.

Our recommendations aim to lower cognitive load, cut task errors and raise satisfaction.

💡 What I learned

Success rates hide friction: All five participants completed the transcript task, yet all five said it took too many steps. Pairing task outcomes with perceived effort caught a problem that completion alone would have missed.

Leaving the product is a finding. Participants turned to Google in Tasks 1, 5 and 6. When people abandon the system’s own navigation, that is a clear sign the information architecture failed.

Recruiting shapes what you can see. Excluding very familiar and very positive users meant the sessions showed real friction rather than workarounds.

⚠️ Limits worth naming

  • Five participants is enough to surface recurring problems, not to produce reliable percentages, so I read the figures above as signals.

  • We tested desktop only, and with mostly first-year students by design.

➡️ Next Step:

  • The natural next step is to prototype the homepage progress indicator and the regrouped Applications page, then rerun the same six tasks and compare.

  • The expected impact (lower cognitive load, fewer task errors, higher satisfaction) is not yet measured.

Back to Home

Back to Home

so… want to chat?


Let’s make something
people trust.

End-user needs

Utilitarian Design

Business goals

That’s the bridge I love to build. I’m open to UX, product design and product roles: on-site in Ontario, hybrid or remote. Or just say hi and show me your pet.

© 2026 Vinuri Hopman. All rights reserved.

so… want to chat?


Let’s make something
people trust.

End-user needs

Utilitarian Design

Business goals

That’s the bridge I love to build. I’m open to UX, product design and product roles: on-site in Ontario, hybrid or remote. Or just say hi and show me your pet.

© 2026 Vinuri Hopman. All rights reserved.

so… want to chat?


Let’s make something
people trust.

End-user needs

Business goals

That’s the bridge I love to build. I’m open to UX, product design and product roles: on-site in Ontario, hybrid or remote. Or just say hi and show me your pet.

© 2026 Vinuri Hopman. All rights reserved.