Worked Example Concept Maps

Worked examples are powerful, but many learners use them badly. They read a solved problem, nod at each line, copy the same steps into a notebook, and feel fluent for 10 minutes. Then the next problem changes one condition and the method disappears. The issue is not laziness. The issue is that a finished solution hides the decisions that made it work.

A worked example concept map solves that problem. Instead of treating a solution as a sequence to imitate, you turn it into a visible network of goals, principles, conditions, constraints, choices, and checks. A worked example is a fully solved task that shows the path from problem statement to answer. A concept map is a visual knowledge structure where concepts are connected by labeled relationships, as described in the background on concept maps. A transfer cue is a feature that tells you when the same idea can be used in a new problem. Those 3 definitions matter because the goal is not to memorize the example. The goal is to recognize why it worked and when to adapt it.

This method fits math solutions, physics derivations, programming examples, accounting cases, grammar corrections, medical case rationales, design critiques, and business strategy examples. It pairs well with retrieval practice concept maps, self-explanation concept maps, problem-solving concept maps, the complete guide, reusable templates, and the free editor.

TL;DR

• Map the decisions inside the solved example, not just the steps.
• Use 15 to 25 nodes for one difficult example.
• Label links with "because," "requires," "checks," "fails when," and "transfers to."
• Hide the solution after 24 hours and rebuild the map from memory.
• Finish with 3 variation problems so the example becomes transferable knowledge.

"A worked example only becomes a study tool when the learner can name the decision points. Copying 12 lines is rehearsal; explaining 5 choices is learning."
— Hommer Zhao, Knowledge Mapping Researcher

Why Worked Examples Feel Easier Than They Are

Worked examples reduce the burden of figuring out every step from scratch. That is why they are useful for beginners and for complex procedures. Research summaries on worked-example effect and cognitive load explain the basic idea: when learners are not overloaded by search, they can notice structure. But that benefit disappears when the learner reads passively.

Most students mark the visible surface:

• formula used;
• answer obtained;
• diagram copied;
• code output matched;
• teacher's final note underlined.

Those notes are not wrong, but they leave out the deeper structure. Why was this formula chosen instead of another? Which clue ruled out a tempting method? Which condition allowed a shortcut? Which step checked the result? Which part would change if the numbers changed? Without those relationships, the learner owns a transcript, not a method.

A worked example concept map asks a better focus question:

How does this solved example work, and what would tell me to use or change the same method later?

That question changes the map. The center is not "Example 4." The center is the logic of the example.

The 6-Part Template

Use this template for one example at a time. If the example is short, keep the map to 12 to 15 nodes. If it is dense, use 20 to 25 nodes and split long branches into sub-maps.

Map part	What to add	Link labels to use	Study check	Best for
Problem goal	What the task asks you to find, prove, decide, or produce	asks for, constrains, depends on	Can you restate the goal in one sentence?	All subjects
Given conditions	Data, assumptions, definitions, constraints, units, context	provides, limits, rules out	Can you list 3 conditions without looking?	Math, science, law, cases
Principle or tool	Formula, rule, framework, model, theorem, pattern, syntax	applies because, requires, converts	Can you explain why this tool fits?	Technical subjects
Decision points	Places where the solver chose a path	chosen because, rejected because, switches to	Can you name the turning point?	Problem solving
Verification	Unit check, edge case, proof check, test case, counterexample	checks, confirms, detects	Can you catch a wrong answer?	Exams and coding
Transfer cue	What makes a new problem similar or different	transfers when, fails when, changes if	Can you create 3 variations?	Long-term learning

This template works because it separates visible steps from invisible choices. The visible step may be "subtract 8 from both sides." The invisible choice is "isolate the variable because the equation is linear and the target is x." The second statement is the one that transfers.

Step-by-Step Workflow

Step 1: Read the Example Once Without Mapping

Read the solved example from start to finish. Do not pause after every line. Your first pass is only to understand the broad story: what was asked, what method was used, and what answer was accepted.

Then write a 1-sentence summary:

This example shows how to use [method] to solve [problem type] when [condition] is present.

For a physics problem, the sentence might be: "This example shows how to use conservation of energy to find final speed when friction is ignored and height changes are known." For a programming example: "This example shows how to use a hash map to count items when repeated lookup must be fast." For a literature example: "This example shows how to connect imagery to theme when the passage repeats a concrete symbol."

If you cannot write that sentence, the example is still too blurry. Read it once more before drawing.

Step 2: Put the Goal and Conditions at the Top

Start your map in the editor with the problem goal. Add the given conditions as separate nodes. Do not combine them into one vague node called "information." Each condition should be testable:

• "mass = 2 kg";
• "friction ignored";
• "array may contain duplicates";
• "speaker uses first-person narration";
• "patient has fever for 3 days";
• "budget is capped at $8,000."

The map should show what each condition enables or prevents. For example: "friction ignored" enables "mechanical energy conserved." "Array may contain duplicates" requires "count frequency, not just membership." "Budget capped at $8,000" rules out "enterprise plan."

"The fastest way to improve a worked-example map is to split conditions. One node called 'given information' hides 6 constraints; 6 condition nodes expose the method."
— Hommer Zhao, Knowledge Mapping Researcher

Step 3: Convert Steps Into Propositions

Do not write "Step 1," "Step 2," and "Step 3" as bare labels. Turn each step into a proposition: two concepts connected by a meaningful phrase.

Weak:

• "formula";
• "substitution";
• "answer."

Better:

• "known height difference determines change in potential energy";
• "conservation law connects initial state to final state";
• "unit check detects impossible speed."

In programming, weak mapping says "loop through array." Better mapping says "loop visits each item so frequency table can update count in O(n) time." In writing, weak mapping says "quote supports point." Better mapping says "image of closed doors supports theme of social exclusion."

This is the core of concept mapping. You are not decorating notes. You are writing relationships you can later test.

Step 4: Mark Decision Points and Rejected Paths

Good worked examples often hide alternatives. The solver chose one method, but another method may have been possible, slower, or wrong under the conditions. Add those alternatives.

Ask:

• What made this method appropriate?
• What tempting method would fail?
• Which condition ruled out the wrong method?
• Where did the example change representation: words to diagram, diagram to equation, equation to graph, graph to conclusion?
• Which step would change first if the numbers or context changed?

For example, in a probability problem, the map may show that "events are independent" allows multiplication, while "events without replacement" would require conditional probability. In a grammar correction, "action completed before another past action" supports past perfect, while "simple chronology" may use simple past. In a business case, "fixed deadline" makes scope trade-offs more realistic than team expansion.

Decision points are where learning happens. They turn imitation into judgment.

Practical Example: Algebra

Imagine a solved algebra example:

Solve 3(x - 2) + 5 = 20.
3x - 6 + 5 = 20
3x - 1 = 20
3x = 21
x = 7

A copied note says, "Distribute, combine, solve." A worked example concept map says more:

• goal: find the value of x;
• condition: x appears inside parentheses;
• operation: distribution removes parentheses because multiplication applies to each term;
• simplification: like terms combine because they share no variable difference;
• inverse operation: adding 1 isolates the term 3x;
• division by 3 isolates x;
• verification: substitute x = 7 into original equation and check that both sides equal 20.

The transfer cue is not "use this exact sequence." It is: "When a linear equation has parentheses, remove grouping first, simplify, then isolate the variable with inverse operations." The failure cue is also important: "If x appears on both sides, collect variable terms before final division." That extra branch prepares the learner for the next variation.

Practical Example: Programming

Suppose a learner studies a solved JavaScript example that counts word frequency:

for each word:
  if word exists in map, add 1
  else set count to 1

A weak note says "use object." A stronger concept map connects:

• repeated words require counting, not storing unique values only;
• hash map supports fast key lookup;
• normalization changes "Map" and "map" into same token;
• loop visits every token once;
• missing key creates first count;
• existing key increments count;
• output can be sorted if the goal is "top terms."

Now the learner can transfer the example. If the goal changes to "first repeated word," the map changes: counting all words is unnecessary; the check should stop at the first repeated token. If the input includes punctuation, normalization becomes a required branch. If order matters, a plain frequency table may not be enough.

Practical Example: Medical Case Review

A nursing or medical student may read a solved case rationale and copy the diagnosis. That is risky because case questions often test cue weighting, not vocabulary recall. A worked example concept map should separate:

• presenting symptoms;
• high-risk cues;
• excluded cues;
• mechanism;
• priority action;
• safety check;
• follow-up assessment.

For example, if a rationale chooses dehydration risk, the map should show which symptoms support fluid volume concern, which symptoms are less urgent, and which action must happen within the first assessment cycle. The student then creates 3 variations: one with the same symptoms but different age, one with a competing diagnosis, and one with a missing vital sign. That practice builds cue recognition rather than answer memory.

When to Fade the Example

Worked examples should not remain fully visible forever. After the learner understands the example, reduce support in stages. This is often called example fading: remove some steps, ask the learner to fill gaps, then move to full problems.

Use this 4-pass schedule:

1. Pass 1, same day: map the full example with the solution visible.
2. Pass 2, after 24 hours: hide the solution and rebuild 8 to 12 key nodes from memory.
3. Pass 3, after 48 to 72 hours: solve a near-transfer problem with one condition changed.
4. Pass 4, after 1 week: solve a far-transfer problem and explain which branch changed.

The schedule matters because a beautiful map can create false confidence. Retrieval exposes whether the learner can reproduce the reasoning without visual support. Transfer exposes whether the learner can adapt the reasoning when the surface changes.

"Do not retire a worked example after one correct re-solve. I want one same-structure problem, one changed-condition problem, and one explanation of why the old shortcut still works or fails."
— Hommer Zhao, Knowledge Mapping Researcher

Common Mistakes

The first mistake is mapping too much. A map with 60 nodes for one example becomes a wall. Keep only the decision structure. If a detail does not affect method choice, verification, or transfer, leave it in the source notes.

The second mistake is using vague link labels. "Related to" is usually a warning sign. Replace it with "causes," "requires," "rules out," "checks," "converts," "contrasts with," or "fails when."

The third mistake is skipping verification. Every worked example map should include at least one check. In math, substitute the answer. In coding, run a test case. In writing, ask whether the evidence actually proves the claim. In cases, check safety priorities. Verification makes the map practical instead of decorative.

The fourth mistake is never creating variations. A worked example without variation practice teaches recognition of one page. Variation practice teaches the underlying method.

Mini Templates You Can Copy

Solved Math Problem Template

Goal -> asks for -> unknown
Given condition -> enables/rules out -> method
Method -> requires -> formula or property
Step -> transforms -> expression
Check -> confirms -> answer
Variation -> changes -> first affected branch

Programming Example Template

Input shape -> requires -> data structure
Constraint -> favors -> algorithm
Loop/recursion -> processes -> each unit
State -> stores -> needed memory
Test case -> detects -> edge case
Variation -> changes -> complexity or output

Reading or Case Template

Question -> asks for -> decision
Evidence -> supports -> claim
Counter-evidence -> limits -> claim
Rule/framework -> explains -> decision
Priority -> determines -> first action
Variation -> changes -> interpretation

Start with one of these in the templates area, then open the editor and build from a real solved example. For classroom or team use, choose 1 shared example, have each person map decision points independently for 15 minutes, and compare only the link labels. That keeps the review focused on reasoning instead of page design.

FAQ

What is a worked example concept map?

A worked example concept map is a 15 to 25 node map that explains how a solved problem works. It connects the goal, conditions, principles, decisions, checks, and transfer cues rather than copying every line of the solution.

How long should it take to map one worked example?

Plan 20 to 35 minutes for a difficult example. Use 5 minutes to read, 15 to 20 minutes to map, and 5 to 10 minutes to create 3 variation questions.

Is this better than simply re-solving the example?

It answers a different need. Re-solving checks whether you can reproduce steps. Mapping checks whether you can explain at least 5 relationships and identify why the method applies. For exam preparation, use both.

How many worked examples should I map before practicing alone?

For a new problem type, map 2 to 4 worked examples, then move to faded examples with missing steps. After that, solve 3 to 6 independent problems with different surface details.

Can this work for humanities subjects?

Yes. Use the solved example as a model of interpretation. Map the question, claim, evidence, assumption, counterargument, and conclusion. A 12 to 18 node map is usually enough for one paragraph or short passage.

What should I do if my map becomes too large?

Stop at 25 nodes for one example. Create a parent map with goal, conditions, method, decisions, checks, and transfer, then move formulas, code details, or evidence lists into separate sub-maps.

What is the fastest way to test whether the method worked?

After 24 hours, hide the example and rebuild the decision branch from memory. Then solve 1 near-transfer problem in 10 to 15 minutes. If you cannot explain which condition changed, the map needs revision.

Use the free concept map editor to map one solved example today. If you are building study material for a class, tutoring program, or knowledge team, contact us and we can help shape a worked-example mapping workflow.