Skip to content
How much to read

Knowledge base

projects / easemysemester / decisions

Two pane browse over a six level navigation

Replaced a six level, five click navigation with a sidebar tree and chapter view after users showed the deep hierarchy was wrong for exam night.

decision · current · updated 2026-09-15 · EaseMySemester case study

See overview.

Context

The original content format made paper a navigation level, alongside exam, subject and chapter. That produced six levels of hierarchy and roughly five clicks to reach a single question.

Decision

Replaced the deep hierarchy with a sidebar tree plus a chapter view, and demoted paper to a filter. The last viewed chapter is restored from local storage, so returning to the app takes zero clicks and switching chapters takes one to three.

Alternatives rejected

Keeping paper and topic as navigation levels was rejected because it meant more clicks.

Why

The job to be done is "I'm one hour from the exam, show me what was asked about this topic." Users showed that the original navigation did not serve that sentence. The data model that produces the five token tags did not need to change, only the information architecture built on top of it.

Consequences

Clicks to a question dropped from roughly 5 to 0 to 3 (numbers).

Status

Shipped. Verified with a clean tsc --noEmit and next build, and the five old drill-down routes were removed.

This page was written by a model from my own repositories and checked by a second one against the same sources. I did not write it, and no version of it was approved by me before it went up. How that works, and where it can still be wrong.