Matific · Teacher & admin navigation

More subjects. Different roles. One framework

I designed a framework—converting top navigation to a scalable side navigation—connecting school roles, classes, and subjects as Matific expanded beyond Maths. It launched alongside the first new subject.

  • Sole designer
  • Navigation & IA
  • Wireframes
  • Visual Design
  • Prototyping
With
Product Managers
When
Released Jan 2026
For
Teachers and school admins
Teacher side navigation design

Teacher Navigation

Combined subject and class selector design

Subject/Class Switcher

Admin side navigation design

Admin Navigation

01 · The UX problem

A second subject changed more than the menu

Who it’s for

Teachers

Work in Class mode; a class can have Maths, Financial Literacy or both.

Need

Switch class and subject without landing on a combination that doesn't exist.

Admins who also teach

Move between running the school and teaching their own classes.

Need

A clear switch between Admin and Class modes.

School admins and leaders

Work school-wide, across many classes and teachers.

Need

School-wide pages in one place, and quick switching between classes.

The majority of our users are teachers, primarily accessing the platform via 1366 × 768 resolution laptops.

Legacy navigation

Legacy top navigation with two navigation bars

Top Navigation Bar 113

  • Logo
  • 5 Primary menus5
  • 5 Secondary menus

Top Navigation Bar 23

  • Page title
  • Class selector2
  • Page-specific menus

Admin Menus4

  • Extra sub menus under Primary and Secondary menus
  • Option to select Whole School in Class Selector

What wasn’t working

Inflexible architecture

Adding new subjects like Financial Literacy required a selector, but the rigid top navigation couldn't support it without compromising vertical space.

Poor visibility for primary controls

The class selector lacked visual prominence, and the dense layout prevented us from increasing its footprint.

Poor viewport optimisation

The double navigation bars consumed critical vertical height on standard laptops (1366×768), while horizontal space on larger desktop monitors was wasted.

Tangled permissions

Teaching and administrative tasks were merged into one cluttered menu, creating cognitive overload for admins who also teach.

Unclear settings location

Having both a class landing page and a separate class detail page created navigational confusion, leaving users unsure of where to manage their class settings.

Design Goal

Streamline class and subject selection, decouple teaching workflows from administrative tasks, and optimise vertical screen real estate while building a scalable foundation for future subjects.

Why it mattered: The immediate trigger was the need to integrate Financial Literacy into the platform. However, the broader challenge was ensuring the navigation could scale for future subjects without introducing friction for Matific’s 200K+ active teachers.

2.1 · Subject + class

Streamline class and subject selection

The most critical architectural decision was defining how teachers switch between subjects and classes. To drive an informed decision, I developed interactive prototypes of both competing models—allowing us to test and evaluate the exact workflow, friction, and cognitive load of each approach.

Option 1

Separate Subject and Class Selectors

Two independent dropdowns (one for subject, one for class).

Prototype option 1: separate subject and class selectors
Try Prototype ↗

Pros

High familiarity; follows standard UI patterns.

Cons

High risk of dependency errors and restrictive UI states. Changing a class could trigger an error, silently switch the subject in the background, or disable invalid options—forcing users into a clunky guessing game of toggling back and forth to find valid pairs. Furthermore, scaling this model for future subjects would introduce UI clutter and require extra clicks.

Option 2

Chosen Direction

Unified Selector

A single dropdown where classes are nested under subject accordions.

Prototype option 2: unified selector
Try Prototype ↗

Pros

Inherently prevents mismatched selections (only valid pairs exist). Highly scalable, as new subjects simply slot in as new accordion groups. A global search allows teachers to find any class instantly.

Cons

Classes repeat under each subject, lengthening the list. However, we mitigated this friction through collapsible accordions and robust search functionality.

2.3 · Space & scale

Optimise vertical space while building a scalable foundation

Shifting to a side navigation model reclaimed critical vertical real estate on standard laptops. The menu collapses into a streamlined icon view to maximize screen space, while clear active-states keep users oriented. Crucially, new subjects now integrate seamlessly into the side selector rather than stacking vertically and crushing the layout.

Why now

While product leadership and I had long advocated for a side navigation model, it previously lacked the business weight to overcome board-level reservations. The introduction of Financial Literacy provided the definitive use case—creating an immediate need for scalable navigation and securing the necessary buy-in to proceed.

Descoped

To manage development scope, we cut a proposed "draggable menu width" enhancement. Because the core design already included a collapse-to-icon toggle, this reduction in scope had minimal impact on our primary goal of saving vertical screen space.

Before & After: Shifting to side navigation

Reclaimed vertical space and a scalable home for new subjects.

Legacy dashboard with top navigation
BeforeDashboard with legacy top navigation
Dashboard with side navigation
AfterDashboard optimized with side navigation

Maximising horizontal real estate

As users become familiar with the platform's architecture, they can collapse the side navigation to maximize horizontal screen space. This hides the detailed submenu text, significantly reducing visual clutter and cognitive load while keeping core tools accessible—ideal for data-heavy reporting.

Expanded navigation on dense table
ExpandedFull navigational context with clear active-state wayfinding.
Collapsed navigation on dense table
CollapsedSpace reclaimed for denser data tables, reducing visual noise for experienced users.

Reflections & Next Steps

What launch taught us, and what I'd do next.

72% were satisfied and about 1 in 5 were not. Here's what that, and the weeks after launch, taught us.

Learned after launch

Never deprecate without a true replacement

We trialed removing legacy menu items to steer users toward a more detailed page. We quickly restored them after realizing the new page didn't support their specific, quick-action needs. Sunsetting features requires building a superior alternative first, not just a different one.

Don't bury high-value tools

We initially relegated the "Explore as Student" preview into the Help menu. Post-launch feedback proved it was a critical workflow tool, prompting us to elevate it back into the primary navigation tier just below Class Management.

What I'd do next

Investigate the dissatisfied 21%

Conduct targeted user research to separate genuine usability flaws from a natural resistance to change. Understanding whether users are struggling with a broken workflow or simply battling legacy muscle memory will dictate exactly how we iterate next.

Revisit the "Current Focus" widget

Setting a curriculum focus is a high-value action for teachers, but surfacing this directly in the navigation was cut early to manage scope. With the architecture now stable, testing and integrating this widget would be a top priority.

Closing the gap between design and build

I established Matific’s first design system on IBM Carbon, made build quality a shared goal through front-end KPIs, and added an AI-assisted QA agent so developers can check builds against the design before my review.

Next: Design & build quality →
Production Class Management interface

Fit

100% is the original image size. Drag to pan, scroll or pinch to zoom, or use the arrow keys and + / −.