Words and pictures

Dual Coding

Combine words and visuals — your memory uses both.

What the Research Says

Your brain stores words and images in two separate memory systems, and information is much better remembered when BOTH are used. Dual coding is not the same as “being a visual learner” — learning-styles theory has been debunked. Everyone benefits from combining words with visuals, regardless of any self-reported style preference.

Evidence Base

Study	Finding	Impact
Paivio (1971)	Original dual-coding theory: verbal and visual memory traces are separate and additive.	Two routes to recall is better than one.
Mayer (2001, 2014)	Multimedia learning research across 300+ studies: well-designed words+visuals combinations produce ~40% better transfer than words alone.	Well-placed visuals turn passive reading into active learning.
Dunlosky et al. (2013)	Dual coding is one of the few techniques rated “effective in most contexts” by the Association for Psychological Science.	Evidence-backed across age groups and subjects.
Castro-Alonso et al. (2019)	Student-generated visuals (drawing) produced bigger gains than pre-made visuals.	Draw it yourself, don’t just look at a diagram.

Step-by-Step Method

1
Pick a topic with relationships — processes, layers, hierarchies, comparisons. Dual coding shines when there’s structure to capture.
2
Choose the right visual format — flowchart for the FDE cycle or algorithms, layered stack diagram for OSI, truth table + gate diagram for Boolean logic, comparison table for storage types.
3
Draw it yourself — by hand or in a simple tool. Don’t just photocopy one from a textbook. The act of creating the visual forces your brain to organise the information.
4
Keep text minimal — labels, not sentences. The text and the visual should say different things. Duplicate labels distract (“redundancy effect”).
5
Revisit blank versions — print or redraw your visual with the labels removed. Fill them in from memory. This combines dual coding with retrieval practice.
6
Compare versions over time — a week later, redraw from memory. Spot the bits you missed.

Example 1

Draw a truth table for A AND NOT B with all four input combinations, then sketch the logic gate circuit alongside it — an AND gate with a NOT gate on the B input. Having both representations on the same page means you can see that when A=1 and B=0 the output is 1, and also see exactly which gates produce that result. Redraw both from memory a week later — most students find the gate diagram harder to recall than the table, which tells you where to focus.

Example 2

Create a 7-row stack diagram for the OSI model: each layer labelled with its name, one-word function (e.g. Physical → Transmission, Transport → Reliability), and one protocol or hardware example. Draw arrows showing data flowing down on the sender side and up on the receiver side. This single visual encodes more than a page of bullet points. Remove the labels and redraw the whole stack from memory — the visual structure helps you rebuild the order even when individual names slip.

Common Pitfalls

Decorative visuals. A picture that looks nice but doesn’t convey information adds cognitive load without the benefit.
Copying someone else’s. The learning happens while you make it. A textbook diagram is useful for reference, not for dual coding.
Too much text. If your “mind map” is paragraphs joined by lines, it’s still just text. Keep labels to 2–4 words.
Only making it once. One-off diagrams are useful. Ones you redraw from memory over weeks are powerful.

When to Use This

Mid-revision cycle — after you’ve learnt the basic facts and are starting to see connections. Before the exam, try a “one-page summary” for each unit combining a key diagram with 5–10 labelled points. Carry these in your bag. Use the night before.