Cognitive load: how it shapes your learning
Have you noticed how hard it is to think clearly in a meeting where three things are happening at once: a cluttered presentation, a chat window flashing, and a discussion that jumps between topics? That is not a character flaw. It is your brain's working memory hitting its ceiling.
In 1988, the Australian researcher John Sweller gave the phenomenon a name and a theory: cognitive load. His work has since shaped how we design training, learning materials, and interfaces, and it explains why less is often more when people need to learn something.
What does the research say?
The starting point is that working memory, the part of your thinking that handles whatever you are holding in your head right now, is severely limited. It can only manage a handful of things at a time, and everything going on in a task competes for the same space. Long-term memory, by contrast, is practically unlimited; learning is about moving patterns there, so that they eventually run on autopilot.
Sweller's decisive discovery concerned problem solving. He showed that when people struggle with a problem in a certain trial-and-error way, constantly comparing where they are with the goal and hunting for the next step, the searching itself consumes almost all of working memory. The result is paradoxical: you can solve the problem and still learn very little from it, because no capacity was left to notice and store the pattern.
The conclusion is that load that does not belong to what is being learned, sometimes called extraneous load, directly impairs learning. Cluttered graphics, parallel information streams, unclear instructions, and stress all take space away from the skill itself. If you want someone to learn, strip away everything that is not the thing itself.
What does this mean for you as a project manager?
Design your meetings for working memory. One question at a time, one slide with one message, decisions written out where everyone can see them. When you ask the team to weigh in on three things at once, you get worse thinking on all three. What looks efficient on the agenda is often inefficient inside the participants' heads.
Protect your own thinking in difficult conversations. A charged conversation already loads working memory with emotions and relationship monitoring. So prepare the essentials in advance: your core message in one sentence, your opening question. What you have prepared costs no working memory in the moment, and that capacity can go to actually listening to what the other person is really saying instead of searching for your own words.
Introduce new things step by step. When a new team member or a new way of working arrives, dose it. Teaching everything at once feels thorough but works worst. A few things at a time, with time to consolidate, builds real competence faster. What has been automated stops loading working memory, and only then is there room for the next layer.
How to practice this
The same research dictates what a good training environment should look like: when you practice a difficult conversation, the screen should be calm and stripped down, so that all of your working memory can go to the conversation, with numbers and analysis waiting until the debrief afterwards. That is how Project-simulator is deliberately built, in line with Sweller's findings. If you want to practice conversations in an environment that does not steal your thinking, you can try it free for a week.
In Project-simulator you practice these conversations against an AI counterpart and get feedback grounded in research like this.
Try free for 7 days