Cognitive load management is the practice of designing interfaces so users spend the least mental effort possible getting what they came for.
It comes in three flavors: the effort the task itself demands, the effort your clunky UI adds on top, and the effort that actually helps learning stick.
Use cases
Overload your users and they don't struggle politely, they bounce, misclick, or rage-fill a form and never come back.
The wall-of-options dashboard: A user opens an analytics tool to 40 widgets at once, can't find the one number they need, and closes the tab.
The endless form: A 22-field signup asks for everything up front. People abandon at field nine, and the drop-off never shows in the happy-path demo.
The decision freeze: A pricing page offers eight nearly identical plans. Faced with too many choices, users pick nothing and leave to "think about it."
How it's used in practice
Chunk related information into small groups instead of one dense block, so eyes can scan and rest.
Reveal complexity only when needed via progressive disclosure, keeping the default view calm.
Cut or defer non-essential choices at each step so users decide one thing at a time.
Favor recognition over recall: show options and past inputs rather than making people remember them.
🪄
Pro-tip: Stop equating "fewer elements" with "less load." One dense, ambiguous control can cost more mental effort than five clearly labeled ones. The only load worth cutting is the extraneous kind your interface invented. The task's own difficulty (intrinsic load) is the job, so don't strip that away and leave users a pretty page that can't do anything.
Challenges & limitations
Over-simplification: Hide too much, and power users can't find the depth they need, so "clean" becomes "crippled."
Measurement is slippery: Load is felt, not easily counted, so it's hard to prove and easy to hand-wave in reviews.
