MindOS Learning Manual: Analogical-Mapping State | Two Problems Can Look Different and Still Have the Same Skeleton

Wait, What?

Two questions can share almost no words—and still be the same problem.

A student may solve one Mathematics problem about filling tanks and fail another about downloading data, even though both contain the same underlying rate relationship.

A Science learner may understand current in a water-flow analogy and then accidentally import a property of water that electricity does not share.

Analogy is powerful because it can carry structure across different surfaces.

Analogy is dangerous for exactly the same reason.

Quick Answer

Analogical-Mapping State is the learner operation of aligning relationships across two cases: deciding what corresponds to what, which structure is genuinely shared, and where the mapping must stop.

The learner should not ask only:

What looks similar?

The stronger question is:

Which relationships play the same role, even though the objects and wording are different?

Owned Learning Operation

ANALOGICAL-MAPPING STATE = identify source structure → identify target structure → align corresponding relations → infer cautiously → test the mapping → mark where it breaks.

This is not generic comparison. Comparison State asks learners to inspect similarities and differences. Analogical mapping goes further: it asks whether a relational pattern in one case can organise understanding in another.

It is also not the same as Transfer State. Transfer asks whether learning survives a changed task. Analogical mapping is one operation that can help construct the abstraction that later makes transfer possible.

Surface Similarity Is the Easy Part

Imagine two stories.

Story A: several small streams enter a reservoir. The total inflow depends on the contribution of each stream.

Story B: several workers contribute parts to a shared production total.

The objects are different: water and workers. The important question is whether the relation is similar: several contributors combine into one total.

Now consider two stories that both contain water but use different relationships. Their surfaces may match while their structures do not.

That gives us a MindOS firewall:

Same nouns do not guarantee same structure. Different nouns do not guarantee different structure.

Three Levels of Analogy

1. Appearance Match

Two cases share visible features, vocabulary or objects.

This can attract attention but may teach very little.

2. Role Match

Different objects play corresponding functions.

For example, a battery in a simple circuit analogy may be mapped to a pump in a fluid system because both contribute to driving a system—not because a battery literally contains pressurised fluid.

3. Relational-System Match

The learner maps several connected relationships at once and can explain which inferences are licensed and which are not.

This is the strongest state because the analogy is functioning as a structural model rather than a decorative metaphor.

The MindOS Analogical-Mapping Protocol

Step 1 — Understand the Source First

An analogy cannot safely carry knowledge from a source that is itself misunderstood.

Ask the learner to explain the source case in its own terms before mapping it elsewhere.

Step 2 — Name the Target

What new case or idea are we trying to understand?

Step 3 — Map Roles, Not Just Objects

Write correspondences explicitly:

source element A ↔ target element A
source relation B ↔ target relation B
source change C ↔ target change C

Then ask why each mapping is justified.

Step 4 — State the Shared Rule Without Either Story

This is the abstraction step.

If the learner can only say “these are both about water,” the analogy has not reached the relational structure.

Step 5 — Mark the Break Point

Every useful analogy eventually fails.

Ask:

What is true in the source but not true in the target?

This protects the learner from importing false properties.

Step 6 — Use a Third Case

Give a new case and ask whether the same relationship applies. If it does, the learner may be moving from one analogy toward an abstract schema.

Worked Examples Across Subjects

Mathematics: Ratio Structure

Recipe scaling, map scale and speed problems can look completely different. The analogy is not “they all contain numbers.” The shared structure is multiplicative comparison between quantities.

Ask the learner to identify what corresponds across the three cases and then state the relationship without mentioning recipes, maps or vehicles.

Science: Models of Current

Fluid-flow analogies can make some circuit relationships easier to discuss, but they are models with boundaries. A learner who carries every property of water into electricity has not mapped selectively.

A strong analogy lesson therefore contains two columns:

what the analogy helps us see;
where the analogy stops being reliable.

English: Argument Structure

A learner can compare two completely different texts and notice that each uses the same argumentative movement: claim → evidence → interpretation → qualification.

The analogy is structural, not topical.

Analogical Mapping Can Fail in Opposite Directions

Failure A — Surface Capture

The learner notices shared objects or vocabulary and assumes the same rule applies.

Failure B — Surface Rejection

The learner sees different objects or wording and misses a shared structure.

Failure C — Over-Mapping

The analogy starts well, then the learner carries properties that were never meant to transfer.

Failure D — Under-Mapping

The learner remembers the analogy as a story but never extracts the general relationship.

Competing Explanations When Analogy Does Not Help

The source case may not be understood.
The source and target may not share the intended structure.
The learner may lack the vocabulary to describe the relation.
The analogy may impose more cognitive load than it removes.
Surface details may be more salient than relational structure.
The learner may need direct instruction before analogy becomes useful.
The analogy may itself contain a misconception.

Do not keep adding analogies when one analogy fails. First diagnose why it failed.

How Do We Know?

Research on analogical comparison has a long history across cognitive science and education.

Gentner, Loewenstein and Thompson’s influential 2003 experiments showed that comparing analogous cases could help novices abstract a shared problem-solving schema and transfer it to later situations more effectively than studying the cases separately.

A meta-analysis of K–12 research on using similarities and differences—including comparison, classification, analogies and metaphors—reported a positive average effect on academic achievement and highlighted the value of systematic instruction, supportive cues, reflection and discussion.

Research in Mathematics and Science has likewise treated analogical comparison as one promising route for helping learners notice structural relationships, but the literature also repeatedly warns that learners can focus on superficial similarity or carry invalid inferences from the source to the target.

Useful sources:

Evidence Boundary

Analogy is not a universal shortcut. Its effectiveness depends on the quality of the source, the learner’s prior knowledge, the clarity of the mapping, the complexity of the material and the support provided. Some studies come from controlled tasks rather than ordinary classrooms. Strong educational use therefore makes the mapping explicit, tests it, and states its limits.

The Independence Test

Give two analogous cases and ask for the shared relationship.
Remove the original analogy and give a third case with different surface features.
Ask the learner to map the roles independently.
Ask for one feature that should not transfer.
Ask the learner to invent a different analogy for the same structure.

If the learner only remembers the original story, the analogy has not yet become abstract knowledge.

Teaching Guide for Parents, Tutors and Teachers

Use fewer analogies, more carefully.

Choose a source the learner already understands.
Map correspondences explicitly at first.
Ask for the shared relationship in neutral language.
Ask where the analogy breaks.
Use a second or third case to test abstraction.
Gradually remove the mapping prompts.

The goal is not for the learner to say, “I remember the water-pipe story.” The goal is for the learner to see a relationship that can survive without the story.

MindOS Direction

If the learner sees similarities but cannot state the shared relation: return to Comparison State and Explanation State.

If the learner can map only when the original diagram or wording remains: inspect Cue-Dependence State.

If the learner understands the analogy but cannot express the same idea in another form: continue to Representation State.

If the learner can map the relation but fails on new tasks: test Transfer State.

MindOS rule: a good analogy does not make two things identical. It makes one important relationship portable while keeping the differences visible.