Study
Case Study 07
Client
McGraw Hill Education
Discipline
Edtech
Discipline
IA

McGraw Hill Ed­u­ca­tion

Teachers couldn't find content that was already in the platform.

McGraw Hill's Open Learning Platform held K-12 instructional content for teachers and students, but its structure made it hard to navigate. Teachers drilled through layer after layer to find a single resource, in the middle of class, when speed mattered most.

Focus
  • Navigation
  • Information architecture
Scope
  • Teachers
  • Administrators
  • Reviewers
Context
  • Edtech
  • State-level adoptions
McGraw Hill Education on MacBook, course table of contents open to Chapter 1 McGraw Hill Education on MacBook, teacher lesson view with planning information
McGraw Hill's Open Learning Platform, showing the nested course structure that made content hard to find.

The hierarchy made simple tasks feel harder than they should have.

The platform's content model was deeply nested, with multiple layers that could each hold content or simply act as containers. In practice, teachers often had to click through several levels before reaching anything usable.

That slowed teachers down and broke their flow. For administrators reviewing the platform at a state level, it also made it harder to see what was actually in the curriculum.

Teachers and reviewers needed different things from the same structure.

The problem wasn't the same for every user. Teachers often knew exactly what they were trying to find and needed to get there fast. Reviewers were looking for the opposite: a high-level view that made the breadth and structure of the curriculum easier to understand.

The redesign had to work for both at once.

The existing navigation asked for too much effort up front.

To reach the course structure, teachers first had to open a separate Browse This Course view, then decide whether to enter a container or expand it, then continue drilling down until something actionable appeared.

That was slow, especially during a live lesson. The deeper the structure went, the more work it took just to find where the useful content lived.

Too many clicks were spent uncovering structure instead of accessing content.

The hierarchy was complex, and it was also hidden. Teachers had to open it up one level at a time before they could decide where to go next.

That made even well-organized content feel harder to use than it actually was.

The original flow, step one: the course page before any structure is visible.
Step one. Teachers first had to click Browse This Course just to expose the content structure.
The original flow, step two: choosing between entering a container or expanding it.
Step two. Each container offered a link into it or an arrow to peek inside, one level at a time.
The original flow, step three: the contents of a single parent folder.
Step three. Only inside the parent folder could a teacher finally see what it held.

The redesign made the course structure visible.

The redesign kept the course hierarchy in view the whole time. Teachers stopped going in and out of containers and moved through the course directly.

A navigation panel on the left stayed open, so teachers could reach any content without losing their place. A full-page table of contents showed the whole course at once.

The redesigned view with a persistent navigation panel beside lesson content.
Content discovery. Lesson subject matter stays in view without jumping in and out of containers.
The full-page table of contents showing the entire curriculum in context.
The whole curriculum on one screen. State-level administrators can see all of it in context.

The redesign kept the complexity and made it navigable.

The content still needed to support a wide range of educational structures, products, and roles. The work left that system intact and made it easier for people to see where they were and what was available.

The platform got easier to use in a real classroom, and easier to read for people evaluating it from outside.

Teachers reached lesson content without drilling through containers.

With the updated navigation in place, teachers no longer had to drill through intermediate containers to reach instructional materials. Teachers could see the content hierarchy at a glance, and the table of contents was reachable from every content page.

The full-screen table of contents also gave administrators and reviewers the whole curriculum in context, so they understood its structure and scope faster. That mattered in state evaluations, where how easily reviewers found things affected whether the curriculum got adopted.

Better navigation helped most during live instruction.

The persistent panel and full-screen table of contents cut out the clicking it used to take to reach a lesson.

Teachers kept their flow, even when they switched to new content mid-lesson.

Fewer clicks to a lesson

Teachers reached lesson materials without drilling through containers.

Navigation stays in view

The panel stays open beside the lesson, so teachers move between topics without losing their place.

Built for live instruction

Teachers could switch to new content mid-lesson with very little interruption.

The table of contents on every page

Wherever a teacher was in the course, Browse This Course opened the table of contents.

The redesigned persistent navigation panel in use during a lesson.
The redesigned full-page table of contents.

The friction here came from a structure people couldn't see.

The content didn't change. Teachers could finally see where it was, and reviewers could see all of it at once.

Next project

Bullhorn's redesigned candidate record and token documentation

01 / 07B2B SaaS • Systems

Bullhorn

A new look for Bullhorn's platform, built from the smallest pieces up.

Bullhorn brought me in for three months to update how its applicant tracking system looked, across the whole platform. The candidate record and the candidate list came first, because recruiters use them most. Once I saw how many components sat under those screens, I proposed a token system, got engineering behind it, and spent the rest of the contract building it.

Focus
  • Design tokens
  • Component library
Scope
  • Full platform
  • 500+ components
Context
  • Three-month contract
  • Via Mondo
View case study: Bullhorn