Cognitive Load at the Gaming Table: How Too Much Information Can Stall a Game

Many game masters will recognize this moment. A player stares at a character sheet, the table goes quiet, and a question that should be quick stretches into a long pause. Someone asks, "Wait, what are we doing again?" Nobody is being lazy or inattentive. Often, the table has simply asked too many minds to hold too many things at once.

Psychologists have a name for the limit those moments run into: cognitive load. This article explains the concept, why it matters for tabletop roleplaying games, and what table-craft follows from it. It is written for game masters and players of any system, and the ideas apply whether you play a rules-heavy fantasy game, a rules-light story game, or something in between.

A quick note on scope. Cognitive load theory comes from research on learning and problem solving. Tabletop play is not a classroom, and no study cited here measured RPG sessions. What follows is an application of a well-known idea to a new setting, and where the advice is about table preference rather than established fact, it says so.

What Is Cognitive Load?

Cognitive load refers to the demand a task places on working memory, the limited-capacity system you use to hold and work with information in the moment, such as keeping a phone number in your head while you walk to the phone.

The idea was developed by educational psychologist John Sweller. In his 1988 paper on cognitive load during problem solving, Sweller argued that conventional problem solving (means-ends analysis) uses so much of a person's limited processing capacity that little is left for schema acquisition, that is, for learning (Sweller, 1988). The core claim is simple: working memory is limited, and anything that does not help you with the task still competes for the same limited space.

Sweller's work is where the concept starts. Sweller and colleagues later described three types of cognitive load: intrinsic, extraneous, and germane. Two are especially useful here:

• Intrinsic load is the effort that comes from the inherent complexity of the material itself. Resolving a grapple against a spellcaster who is concentrating on a spell can involve more interacting rules than swinging a sword at a goblin.
• Extraneous load is the effort that comes from how the material is presented or organized, rather than from the material itself. A cluttered handout, an unclear map, or a rule explained out of order adds extraneous load.

This split is a useful lens, with a caveat: the exact taxonomy has been revised and debated in the literature since 1988, so treat the categories as a working vocabulary rather than settled doctrine. The practical takeaway is stable. In many cases, it may be possible to reduce the effort a table spends on things unrelated to play without making play itself any simpler or less interesting.

Why Cognitive Load Matters in Tabletop RPGs

A tabletop session asks people to do several demanding things at the same time. Consider what a single player may be juggling during one combat turn:

• Their own character's abilities, resources, and conditions.
• The current positions of allies and enemies.
• What the game master just described.
• The social and fictional situation: who knows what, who is angry at whom.
• The rules that apply to the action they want to take.
• Waiting for their turn while trying not to lose any of the above.

The game master carries more. They may be tracking monster statistics, narrating, adjudicating rules, remembering a non-player character's voice and motives, watching the clock, and reading the mood of the table.

None of this is a flaw in the hobby. Handling rich, shifting information is part of the appeal. But if extraneous load is high, there is likely less working memory left for the parts people came to enjoy: making clever choices, roleplaying, reacting to surprises, and laughing at each other's jokes.

Familiar symptoms

Because cognitive load is invisible, it usually shows up as other problems. These are common symptoms that overlap with load, though other causes are possible too:

• Long pauses at the start of a player's turn.
• Players asking the game master to repeat information that was just given.
• A newer player going quiet, or deferring to experienced players for every decision.
• Combat that feels slow even though each individual action is quick.
• Players forgetting details (a name, an objective, a condition) that seemed obvious to the game master.
• Visible fatigue late in a session.

If you see these, it is worth asking whether the table is overloaded before assuming the group is disengaged. The fix is often to reduce what people have to hold in their heads, not to ask them to try harder.

Where Load Comes From at a Table

It helps to sort the sources of load, because the remedies differ. These groupings are a practical framework for this article, not a formal classification from the literature.

Rules load

Some of a system's complexity is intrinsic: if a game models many factors, you have to engage with them. Some of it is extraneous: rules scattered across several books, unclear terminology, or exceptions that are hard to look up.

A searchable reference, where one is available, does not remove complexity, but it can lower the cost of finding an answer.

Information load

This is the amount of fictional and factual content players must keep track of. Names, places, factions, quest details, inventory, and the state of the battlefield all count. A game master who introduces six named characters in one scene is spending players' working memory fast.

Presentation load

This is about how information is delivered. A long spoken description can be hard to hold in memory, while a short description plus a visible prop or sketch may be easier; how much description a group wants is a matter of table preference. The Alexandrian's tips on evocative descriptions suggest a few sensory, concrete details. For minor scenes, he suggests describing three things with a single detail each, since items past the third in a sequence add little (Alexander, 2017).

Decision load

Every choice costs effort. A player facing a dozen possible actions, spells, and items may freeze. A player with a clear shortlist may act quickly. This is part of why some tables find that structured prompts, such as "you can attack, help, or retreat," speed up less experienced players without removing their freedom to try something else.

Social and emotional load

Playing with strangers, performing in character, or worrying about disappointing the group all consume attention. This is a different kind of load from rules or information, but it plausibly competes for the same limited attention. Setting clear expectations in a session 0 helps keep players from walking away disappointed (Haeck, 2024), and it may also ease some of this social pressure.

Principles for Lowering Extraneous Load

The aim is not to strip a game of depth. It is to make sure the effort people spend goes toward play. These principles follow from the concept, and each is framed as a choice you can adapt rather than a rule you must follow.

1. Externalize what people have to remember

Working memory is small, but tables are large and paper is cheap. Moving information out of heads and onto the table is a practical way to reduce load.

Examples of externalizing:

• A visible initiative tracker, so nobody has to remember the turn order.
• A shared map or sketch, so spatial information is seen rather than recalled.
• Index cards or a notepad of names and one-line descriptions of important characters.
• Condition markers or tokens placed on a character, so players do not have to remember who is poisoned.

The principle is general: if something matters repeatedly during play, give it a physical or digital home.

2. Chunk information

Grouped information is often easier to follow than a long string of unrelated items. Instead of reading out a list of nine details about a room, group them: what the characters see first, what they notice if they look closer, and what is hidden. Giving a few vivid, organized facts is easier to hold than an undifferentiated paragraph.

In 'The Art of the Key,' The Alexandrian criticizes 'wall of text' location keys and argues that a key should make information easy to parse and reference during actual play (Alexander, 2014). Structuring your notes into short, scannable chunks reduces your own load as well as the table's.

3. Introduce complexity gradually

Intrinsic load is easier to manage when it is introduced in steps. A new player does not need every subsystem in the first session. Teaching the core loop first (describe what you do, roll if there is uncertainty, hear the result) and layering exceptions later gives people time to build familiarity.

What feels automatic to an experienced player once felt effortful. As familiarity grows, a task takes less working memory, which is part of why experienced players can handle more at once. The practical consequence is patience: expect new players to need more time, and do not read that as a lack of interest.

4. Reduce competing demands during key moments

If you want players to absorb a crucial piece of information, avoid delivering it while they are doing something else demanding. A plot-relevant detail announced in the middle of a tense combat round may well be lost. Giving it between scenes, or repeating it when attention is free, helps.

Similarly, avoid asking players to recall something from three sessions ago in the middle of a difficult decision. A short recap at the start of the session, or a written summary, helps the information return to working memory before it is needed. How formal that recap is depends on your group.

5. Make lookups cheap

If a rule matters often, make it quick to find. Some game masters keep a one-page cheat sheet of the rules that come up most at their table. Others prefer to make a ruling quickly and verify later. Both are legitimate. The load-reducing idea is to avoid the long mid-turn rules hunt that stalls everyone.

Michael E. Shea's work on pacing makes a related point: good pacing means keeping up forward momentum while knowing when to pull back (Shea, 2022). A fast, good-enough ruling often costs the table less than a slow, perfect one, though the right balance is a table preference.

6. Keep the number of simultaneous threads small

Tracking many subplots, factions, and open questions raises information load. Some groups thrive on this complexity, and some long campaigns lean on it. For other groups, narrowing the active threads to a few per session leaves more attention for each. When in doubt, ask your players how much they want to keep track of.

What This Means for Game Masters

Game masters often carry a heavy load, so reducing it for yourself is part of reducing it for the table.

Prepare in a way that lowers your own table-time load

Prep that you cannot read quickly at the table does not help you. Shea's work on high-value prep asks where limited prep time is best spent and focuses on the activities that matter most for running a great game (Shea, 2024). That is a statement about efficient prep, but it has a load angle: a short, scannable set of notes is easier to use mid-session than a dense document.

Some practical formats that reduce lookup effort:

• One-line descriptions for non-player characters with a distinguishing trait and a motivation.
• Bold keywords in notes so your eye finds them quickly.
• A short list of likely scenes rather than a script.
• Monster information reduced to what you will need on the turn: attacks, defenses, and one or two special behaviors.

Tactics resources such as The Monsters Know What They're Doing can help you decide quickly how a creature behaves, reducing the effort of improvising tactics on the spot (Ammann, 2019).

Use pacing as a load management tool

Pacing is not only about excitement. A change of pace may give people a mental breather. A fast action scene followed by a slower conversational scene lets people recover. Alexander's writing on the art of pacing treats pacing as something a game master can deliberately shape (Alexander, 2013), and his advice aimed at beginners is a good starting point for building the habit (Alexander, 2023).

If you notice the table flagging, a short break, a change of scene, or a simplification can help more than pushing on.

Watch your own description habits

Long stretches of narration may be hard for listeners to hold onto, especially if the details are not tied to anything players will act on. The Angry GM's 'When to Stop Narrating' describes 'tab stop narration': skipping ahead past stretches where nothing needs deciding until the next point that calls for player input (The Angry GM, 2025). You do not have to adopt any one author's view, but the ideas are worth testing: skip ahead when nothing needs deciding, and favor shorter descriptions that invite action, which can be easier to hold and more useful.

Calibrate to the least experienced person

It can help to plan a table's load around the person with the least familiarity. A game that is comfortable for four veterans may overwhelm a newcomer. You can often support the newcomer without slowing everyone down: a simple character with fewer options, a brief reference card, or a pairing with a friendly experienced player.

What This Means for Players

Players can lower their own load and help others do the same.

• Know your character's core moves. A short list of your three or four most common actions on an index card can reduce hesitation.
• Plan during other turns. Use waiting time to think about what you might do, so your turn is faster. Staying attentive also keeps you from losing the thread of the scene.
• Take notes. Writing down names, goals, and clues turns memory into reference. Some players find a few words per scene enough.
• Ask for a recap. Asking "Can someone remind me what we were after?" is a sign of engagement, not a failing, and it brings everyone back to the same page.
• Say when you are overloaded. A quick "I need a moment" is useful information for the game master.

Cognitive Load and Safety Tools

Social and emotional load deserves its own mention. Safety tools exist so players can address discomfort without a lengthy explanation, which reduces the effort of managing it in the moment. Resources such as the X-Card, which Stavropoulos developed as a simple, quick way to signal a problem, aim to make that signal low-effort (Stavropoulos, n.d.). The TTRPG Safety Toolkit collects a range of such tools (Shaw & Bryant-Monk, n.d.). Whether and which tools suit your table is a conversation to have with your group, and a pre-game discussion is a natural place for it (Haeck, 2024).

Limits of the Idea

It is worth being honest about what cognitive load theory does and does not say.

• It is a model of learning and problem solving that originated in educational research (Sweller, 1988). Its application to tabletop play is an extension, not a tested finding about RPG sessions.
• Lowering load is not always the goal. A mystery or a tactical puzzle may be fun precisely because it taxes you. Some players enjoy a dense, demanding game. Aim to remove the load that does not serve the fun.
• People differ. What overloads one player may be effortless for another, and familiarity changes the picture over time.
• Simplifying can go too far. A game stripped of meaningful choices or consequences may lose the engagement that makes people care.

Treat the concept as a diagnostic lens rather than a prescription. If a session is dragging, asking "What is the table having to hold in its head right now?" is often a productive first question.

Example: The Lantern Road Company

This is an illustrative scenario, not a report of an actual game. It shows how the ideas above might look in practice for a fictional group.

The Lantern Road Company is a four-player party escorting a merchant caravan through a mountain pass. The game master wants a lively opening scene at a crowded waystation. Here are two ways the same scene could go.

The overloaded version. The game master narrates for several minutes, naming the innkeeper, her husband, three rival caravan masters, a tax collector, and two travelers, while describing the layout of the common room, the weather outside, and a rumor about bandits. Then the game master asks, "What do you do?" The newest player, who is playing a cautious scout, goes quiet. Another player asks who the tax collector was. The scene stalls while the game master repeats names.

The lightened version. The game master prepares a short note card: three characters, each with one memorable trait and one want. The innkeeper is warm and hurried and wants help with a broken cart. A rival caravan master is smug and wants to leave first. A tax collector is nervous and wants an escort. The game master sketches the common room as a rough rectangle with the hearth, the door, and the stable yard marked. Before play, a one-line recap reminds everyone of the party's goal: reach the next town before the pass closes.

During the scene, the game master presents the three characters one at a time, in short bursts, and the player with the scout notes the names on a card. The sketch stays on the table, so no one has to remember where the door is. When the party reaches a choice, the game master offers a loose shortlist: they could help the innkeeper, question the tax collector, or watch the rival master. Players remain free to do something else.

Nothing about the fiction became simpler. The same characters exist, and the same tension is in the room. What changed is how much the table had to carry in working memory. That left attention for the part they came for: deciding whether to trust the nervous tax collector.

A Short Checklist for Lowering Load

Use this as a quick pre-session or mid-session check. Adapt freely.

1. Is the key information visible (map, tracker, names) rather than only spoken?
2. Have I grouped details into a few clear chunks?
3. Does every new rule or character earn its place this session?
4. Is the pace giving people moments to rest between demanding scenes?
5. Can the least experienced player take a meaningful action without help?
6. If something is likely to come up repeatedly, is it easy to look up?
7. Have I asked the table how much complexity they actually want?

Where Tools Fit In

Tools can help with externalizing, and some people find that tracking aids reduce their load at the table. The Dungeon Trainer is one option for groups who want to play together and improve their craft. Whether you use paper, a spreadsheet, a virtual tabletop, or a dedicated tool is a matter of preference. The aim is the same: free up attention for the game.

Key Takeaways

• Cognitive load is the demand a task places on limited working memory, a concept developed by Sweller (1988).
• At a table, load comes from rules, information, presentation, decisions, and social pressure.
• Extraneous load, the part that does not serve play, is the best place to cut.
• Externalize, chunk, introduce complexity gradually, and keep lookups cheap.
• Some tables want high complexity. Match the load to what your group enjoys.
• Treat the idea as a diagnostic lens, and ask what the table is holding in its head when play stalls.

Sources and Further Reading

• Alexander, J. (2013). The Art of Pacing. The Alexandrian. https://thealexandrian.net/wordpress/31509/roleplaying-games/the-art-of-pacing
• Alexander, J. (2014, May 19). The Art of the Key. The Alexandrian. https://thealexandrian.net/wordpress/35180/roleplaying-games/the-art-of-the-key
• Alexander, J. (2017, September 4). Random GM Tip: Evocative Descriptions. The Alexandrian. https://thealexandrian.net/wordpress/39227/roleplaying-games/random-gm-tips-evocative-descriptions
• Alexander, J. (2023, May 30). Pacing for the Beginning GM. The Alexandrian. https://thealexandrian.net/wordpress/49547/roleplaying-games/pacing-for-the-beginning-gm
• Ammann, K. (2019). The Monsters Know What They're Doing: Combat Tactics for Dungeon Masters. Saga Press.
• Haeck, J. (2024, March 11). How to run a Session 0 for your D&D game. D&D Beyond. Original work published January 8, 2021.
• Shaw, K., & Bryant-Monk, L. (n.d.). TTRPG Safety Toolkit. https://ttrpgsafetytoolkit.com/
• Shea, M. E. (2022). Improving Pacing. Sly Flourish. https://slyflourish.com/pacing.html
• Shea, M. E. (2024, June 3). High Value Prep. Sly Flourish.
• Stavropoulos, J. (n.d.). X-Card.
• Sweller, J. (1988). Cognitive load during problem solving: Effects on learning. Cognitive Science, 12(2), 257-285.
• The Angry GM. (2025, July 31). When to stop narrating. The Angry GM.