Switching costs are the hidden term
Working memory holds a handful of items at once. Every context switch flushes and reloads that set, and studies of interrupted work find it takes a substantial stretch to return to full depth. Two of the seven factors here — switching and interruptions — are the ones most often ignored in workload conversations and most often the largest contributors.
- • Batching similar work reduces reload cost more than working faster
- • Externalising open loops onto paper frees working memory
- • Frustration is a load factor, not just a feeling
Why effort masks overload
People compensate for high load by working harder, which keeps output stable while error rates and recovery cost climb invisibly. That is why the effort item matters: high performance sustained by high effort is the signature of a system running past its capacity, and it is only visible before something breaks if you measure it.
FAQ
What is cognitive load?
The amount of working memory resource a task demands. Overload occurs when demand exceeds available capacity and performance degrades.
How do I reduce it?
Reduce switching, batch similar tasks, externalise open loops, and automate or template the recurring decisions that eat capacity.
Is some load good?
Yes. Moderate load is associated with engagement and learning. It is sustained heavy load with no recovery that causes problems.
How this calculator is built
Independently maintained
Written by Sam Doshi and the RevenueLab editorial team. We don't sell the data feeds this tool is built on.
Sourced from primary data
Benchmarks come from public AdSense / Stripe / IRS disclosures and reader-submitted data — never third-party "$X per view" claims. Full methodology.
Last editorial review
Reviewed on a rolling quarterly cycle. Dated reviews are published on the methodology record for each calculator.
Editorial standards
See our editorial policy and disclaimer. Results are estimates, not advice.