toni teaches
Spending Your Learner's Budget
Way back in the 1990s, I discovered Jakob Nielsen. His teachings, along with Steve Krug's, formed the foundation of my career in web application development and still influence everything I do when designing e-learning interfaces. He recently published an article on cognitive load, and I've translated it for all of my course designers.
Your students are working with about four chunks
Your learners arrive with a mental budget of roughly four chunks, and your course spends it whether you planned to or not. Every hunt for the right link, every "wait, which worksheet was this?", every cryptic module name is an expenditure.
By lesson three, some students are overdrawn. They don't blame your course design. They quietly decide they're "just not good at this." That one makes me cranky, because it's fixable.
Load is a budget to allocate, not an enemy to eliminate
Usability pioneer Jakob Nielsen recently wrote about cognitive load, the mental effort people spend to perceive, understand, decide, and act. His reframe: the goal isn't to minimize load. It's to allocate it, and his slogan is "spend the user's mind on the user's goal."
Nielsen is writing about interfaces, and the leap to course design is mine. But swap "user" for "learner," and it fits uncomfortably well. Some effort is the learning itself, and that's the good stuff. Everything else is overhead, and your students are paying for it out of pocket.
Sort your course's load into three buckets
Nielsen draws on John Sweller's cognitive load theory, which splits load into three types. The course examples in the last column are my translation.
- Intrinsic load is the subject's built-in "costs" such as visual identity, an unreasonable schedule, and confusing navigation. Manage it with sequencing, chunking, and sensible standards.
- Extraneous load is how you present the material, like three platforms to find one handout, inconsistent file names, or a wall of text. Eliminate it without mercy: Be consistent, centralize access, and eliminate unnecessary mouse clicks.
- Germane load is the effort of building lasting understanding, like practice, worked examples, or applying an idea to a learner's own project. Protect it, because this load pays dividends.
The trap is trimming the wrong bucket. Cut the practice because "it's too much work," and you've deleted the learning. Keep the confusing navigation because "it's how the platform works," and you've kept the tax.
Four places your course quietly leaks
Nielsen audits the budget at four stages of an interaction. Here's how each shows up in a course.
- Perceive: Instructions sit far from the thing they describe, so learners flip back and forth. Put the directions right beside the task.
- Understand: Jargon, cute-but-cryptic module names, or a narrator reading the slide word for word. Nielsen notes that duplicating information makes it harder to process, so let your voice add something the slide doesn't.
- Decide: Fourteen "optional resources" and no clear next step. Offer fewer, ranked choices and a sensible default.
- Act: Learners must remember a login, a code, or what they decided two lessons ago. Show earlier work on screen instead of asking them to recall it.
One bonus from Nielsen's research roundup: scaffolding that helps beginners can slow experts down. Offer a skippable intro and a fast lane, and let veterans bypass the training wheels.
Beware load laundering: pretty is not simple
Nielsen calls it load laundering when complexity moves off the screen and into the user's head, and the result gets booked as "simplicity." His example is a minimalist screen with a few vague labels that can cost more effort than a busy screen with many clear ones.
Courses do this too. A gorgeous, spare dashboard with modules named "Explore" and "Create" looks calm, but learners now hunt for what they need. Dropping prerequisites keeps the syllabus lean while students go Googling for the missing pieces.
How to tell honest simplifying from laundering? Watch behavior, not aesthetics. If learners backtrack, reread, and email you "where do I find…?", the load didn't go away. Your inbox is a surprisingly good load meter (that last bit is my own rule of thumb, not Nielsen's).
Unfinished lessons haunt people at 11 pm
Nielsen also looks at load over time. Unfinished tasks tend to nag at the mind (the Zeigarnik effect, though he notes later replications are mixed). But research he cites suggests that making a concrete plan for the unfinished task can quiet the nagging, even before you finish it.
For courses, that translates to a few cheap habits:
- Save progress automatically and offer a clear "continue where you left off."
- End each lesson with one named next step.
- Use progress bars that can actually reach 100%.
And skip what Nielsen calls loop farming: fake incompleteness meant to lure people back, like streaks that punish a vacation.
Try a 20-minute budget audit this week
Pick your course's most important path, say from purchase to finishing lesson one. Walk it like a first-timer, and count everything a learner must hold in their head: codes, links, earlier choices, "where was I?" moments.
Then run each item through four questions. Can I cut it? Chunk it? Default it? Make it visible? Fix the biggest leak first, then repeat.
Nielsen's full article has 26 design guidelines, plus a section on how AI tools shift the load. It's written for interface designers, but it’s got a lot of juicy nuggets for course designers, the biggest ones I’ve covered here. I encourage you to read his article with your course-design hat on.
Sources: Cognitive Load Is a Budget, Not an Enemy: Design for the Brain's 4 Chunks, Jakob Nielsen, Aug 12, 2026.
