Four Myths About Storytelling in Educational Game Design

Most educational game stories fail before anyone writes the dialogue. They begin with a wizard, a mission, or a disaster and attach a quiz afterward. The learner has a task, but no reason inside the game for that task to exist.

The more useful case for storytelling education is narrower: a story can organize facts around a problem, give a decision a human consequence, and help students see why evidence matters. That is a meaningful job. It is also a job that does not require elaborate lore, branching endings, or a cast of animated characters.

Jerome Bruner described narrative and paradigmatic thinking as different ways of making meaning. Richard Mayer’s coherence principle and research on “seductive details” point to a related caution: interesting material that does not support the learning goal can compete with it. The research base is stronger for narrative supporting comprehension and causal reasoning than for the sweeping claim that any story makes a game more motivating or memorable.

Four common myths get in the way.

Myth 1: “Students need a rich, immersive story to stay engaged”

That advice confuses attention with learning. A student can care deeply about a character, collect every virtual object, and still miss the concept the activity was meant to teach.

In educational game design, story earns its place when it performs an instructional job. It should establish a problem, identify a relevant perspective, make evidence matter, or show what changes after a decision. At its best, story is a compression tool: it gives several facts a relationship. At its worst, it is extra material competing for working memory.

Mayer’s coherence principle argues for removing words, images, and sounds that do not support the instructional message. Work by Richard Mayer and Robin Harp on seductive details reached a similar warning about interesting but irrelevant additions. Their point was not that students dislike detail. It was that detail can pull attention away from the explanation a learner needs to build.

Start with this sentence frame before writing character biographies or backstory:

A [role] must [make a decision] because [problem], using [evidence]. The decision changes [consequence].

For an eighth-grade watershed activity, “You are the chosen guardian of the river kingdom” supplies atmosphere but not much disciplinary purpose. “The town must decide whether to close a well after nitrate levels rise” gives students a problem. Runoff maps, water samples, health guidance, and uncertainty now have somewhere to go.

Use a deletion test. Remove the character names and decorative backstory from the draft. If the task, evidence, and reasoning remain exactly the same, the story was probably decoration. Rewrite the story around the decision rather than adding more detail around the setting.

This advice has a limit. Students with little prior knowledge may need more orientation, and a completely bare scenario can feel arbitrary. A short explanation of who is affected or why a decision is urgent can reduce confusion. Add detail that helps students interpret the problem; resist detail that merely proves the designer has imagined an impressive world.

Myth 2: “Narrative learning means turning the syllabus into a linear plot”

Narrative learning does not require every topic to become a hero’s journey. A narrative can be a sequence of observations, a dispute between sources, a design failure, or a chain of decisions. Its basic ingredients are time, causality, perspective, and consequence.

That distinction matters because a plot can be linear while the thinking remains active. A lab investigation might move from an anomaly to a hypothesis, then to a test and a revision. A civics inquiry might move from a resident complaint to competing priorities, a budget constraint, and a public decision. Neither needs a villain, a climactic battle, or a surprise twist.

The Cognition and Technology Group at Vanderbilt’s Jasper Woodbury series is a useful reference point. Its problems were presented through anchored situations that gave students a reason to use mathematics and science. The instructional value came from embedded information, complex relationships, and a need to decide—not from cinematic production.

Draft a three-layer brief:

• World: What conditions and facts are fixed?
• Role: What can the learner know, influence, or question?
• Decision: What must the learner choose, explain, or revise?

Write those three lines before deciding whether the game needs a branching plot. They also expose a common flaw: giving students a role with no real authority. If the learner is called an engineer but cannot inspect data, compare constraints, or defend a design, the role is costume.

Does every educational game need a plot? No. Narrative is especially useful for causal reasoning, perspective-taking, systems thinking, and ethical judgment. It may add little to a short practice round for multiplication facts or vocabulary recall. In those cases, a clear goal and immediate feedback may serve the learning better than a fictional wrapper.

There are subject-specific risks, too. A single protagonist can flatten history by making structural forces look like the work of one great individual. Personifying a cell, atom, or ecosystem can create a memorable explanation that is scientifically wrong. Story helps when it makes relationships visible; it harms when the metaphor becomes the content.

Myth 3: “Every meaningful choice needs its own branch and ending”

Branching is often mistaken for agency. It is possible to give students four apparent choices while leading every path to the same predetermined answer. It is also possible to create so many branches that nobody can check whether the content, feedback, and accessibility work on every route.

With four decision points and three options at each point, a fully branching structure produces 3 × 3 × 3 × 3 = 81 paths. Add one more decision and the number becomes 243. That is before accounting for alternate feedback, reading levels, misconceptions, translation, or factual review.

A more manageable structure is convergent, sometimes called foldback branching. Students make different choices, encounter different evidence or constraints, and then return to a shared situation where they must make the next judgment. The story can still acknowledge consequences without requiring 81 separate endings.

For each decision, check four things:

• What concept or judgment distinguishes the options?
• What evidence could support a defensible choice?
• What changes immediately after the choice?
• How can the learner revise or explain the decision?

The consequence does not have to be points, a locked door, or a triumphant animation. It might be a new stakeholder response, a depleted resource, a conflicting data set, or a need to revisit an assumption. Those consequences make the reasoning visible.

This is where choice design becomes assessment design. If students receive the same information no matter what they choose, the choice is cosmetic. If one option produces the only positive outcome, students may learn to hunt for the designer’s preferred answer rather than weigh evidence. Ask for a brief explanation before revealing the result, and treat the explanation as part of the learning record.

A shared ending can sometimes be more honest than multiple endings. Real decisions often lead to incomplete information, trade-offs, and another decision rather than a neat victory screen. Full branching is worthwhile when genuinely different outcomes are the subject—such as a systems simulation or a sustained policy exercise. If that is not the learning goal, spend the saved design time on better evidence and better feedback.

Myth 4: “Students will remember the story, so the content will stick”

Story memory and concept mastery are different things. A student may accurately retell why a character chose one bridge material and still be unable to explain load, stress, or trade-offs in a new problem.

A story provides retrieval cues, but a cue is not the knowledge itself. Retrieval-practice research, including Roediger and Karpicke’s 2006 work, offers a useful corrective: durable learning depends on pulling an idea back out, not merely recognizing it while the original narrative is present.

Use a short debrief that gradually removes the fictional wrapper. First ask students to identify the decision, the evidence, and the consequence. Then ask them to express the same reasoning without the character names, setting, or game terms. Finally, give them a new case with one changed condition.

For example, after a resource-allocation game, an exit task might ask students to:

1. State the principle that guided their decision.
2. Cite the evidence they used and name one limitation.
3. Apply the principle to a new allocation problem.
4. Explain what would change if one important condition changed.

A claim-evidence-reasoning paragraph, annotated diagram, or short oral defense will tell you more than a polished retelling of the plot. If students can only answer while the story’s proper nouns are in place, the narrative has done too much of the thinking for them.

This fails when the debrief is treated as optional. Ten minutes spent translating the story into disciplinary language may feel like it breaks the spell, but without that step the activity can become a pleasant memory with weak transfer. If the timetable cannot protect the debrief, shorten the story before shortening the thinking task.

A one-week story audit for an existing activity

Take one game or interactive lesson you already use. Do not redesign the whole thing. Spend about 30 minutes on this audit:

1. Write the learning target as an observable action. “Understand ecosystems” is too broad. “Use two pieces of evidence to explain how removing one species changes the food web” is usable.
2. Write the one-sentence story spine: role, problem, decision, evidence, consequence.
3. Label each scene or piece of dialogue with its job: orient, provide evidence, require a decision, reveal a consequence, or support reflection. Cut or shorten material with no job.
4. Circle every student choice. Beside each one, write the concept that separates the options and the information that changes afterward.
5. Create a story-free exit task using the same principle in a new context.

Then ask a colleague to read only the opening and first decision. Can they tell what the learner is deciding and what evidence matters? If not, more atmosphere will not solve the problem. Clarify the problem.

The success signal is not that students enjoyed the plot, though enjoyment can help. It is that they can name the problem, justify a decision, and use the underlying idea after the characters and setting have disappeared. Before the next class, rewrite one existing activity’s opening problem and first decision with that test in mind.