Schema

Part of Deep Processing.

A schema is a network of concepts and routes: each piece connects to others and can be reached from more than one entry. Facts sitting outside that network stay isolated. Facts inside it can be reached, reasoned through, and used on a new case.

What a schema is

The structure knowledge sits in decides what can be done with it. A fact by itself answers only the question that named it. A fact wired to its neighbours can be reached from a different question, used to explain a third idea, and applied to a case the source never showed. That is the difference Knowledge Mastery: From Recognition to Usable Knowledge is drawing: recognized is not the same as usable.

When the network is strong, a question that touches any node lights the surrounding structure. The path does not have to start at the official entrance. It can start from a symptom, a counter-example, an exception, or a neighbouring topic, and still arrive. When the network is thin, the same few doorways work and the others do not. A question asked from the wrong doorway looks like forgotten material. It is often material that was never connected.

A transport network is the picture that makes this recognitional. Each concept is a station. Each relationship is a route. A dense network reaches almost any destination from almost anywhere. A thin network keeps offering the same few stations, and fails when those are not the ones the question used. The failure is not always a blank. Sometimes the material is there, and there is no route to it from the question that was asked.

Two qualities of that network can be told apart. Retention is how much of it stays accessible over time — whether last week’s stations are still on the map. Mastery is how well-connected, accurate, and usable the map is — whether a new question can ride the existing routes. A network can score high on one and low on the other. A well-rehearsed list of terms lasts a week and still cannot answer a sideways question. A richly connected map that was never retrieved fades, and the routes go with it.

Both qualities rise by the same process: building the network on purpose. Neither is reliably improved by going back over the same pages, by repeating items that were never joined, or by sitting through material without placing it. The pages feel familiar. Familiarity is retention of the surface, not mastery of the routes. Faced with a complex problem, a well-built schema is what lets the problem come apart into the concepts it is made of, with a place to start. That is one clause, not a feat.

The conversion bottleneck

The slow step is not intake. Pages turn quickly. Lectures run at speaking speed. What takes the time is converting what just arrived into a network that can be entered later. Reading is cheap. Joining each new piece to the pieces already held is the work that actually costs.

A piece that arrives with nowhere to sit is processed at full cognitive cost every time. It is stored poorly. It is gone in hours or days. A piece that arrives into a network already waiting is placed, joined to what it belongs with, and lasts. The extra effort is spent deciding whether the piece matters, and where, before any of the meaning is processed. That full-cost feeling is what Cognitive Load & What Mental Effort Is Trying to Cue is trying to cue.

A thin network produces a recognizable cycle. Retention is poor, so the material fades in hours or days. Relearning is required. The same process runs again: more pages, more highlights, the same isolated pieces. The same thin network comes back out. Repeating that process harder produces the same network faster. Changing the volume does not address the cause. Changing the process — forming the network rather than adding to the pile — does. The hours spent on the second and third pass through the same chapter feel like progress because more of the chapter has been seen. Seen is not connected. The trap is that the feeling and the structure move in opposite directions.

Why this page exists

Volume is not the repair. The conversion step is. Going back over notes and running unstructured repetition do not raise retention or mastery, however many times they run. They activate what is already connected. They do not build the connections that were never made.

A well-organised pile is still a pile. A tidy outline that cannot be entered from a new question is not a schema. The lookalike is the thing the page has to survive: notes that look complete, headings that look like structure, a map that can be recognized and cannot be used. The outline can be recited. A question asked from the side still dies.

That is why this page sits next to retrieval practice rather than being replaced by it. Retrieval tests a network. It cannot invent the routes that were never built.

Formation, not review

This system forms a schema in three passes. Skipping any one leaves the network incomplete or inaccessible. The three are a procedure, not a published research triad. The how-to in full lives on Schema Construction, Assimilation, and Reorganization. What follows is the pointer, not that page.

Construction builds a draft before the source is engaged in depth. Accuracy is not the point of that draft. Existence is. Three moves get one. Headings, objectives, lecture slides, and diagrams come off every source onto a single keyword list, so attention is not split hunting the same words across books, slides, and videos. What is already known becomes the first scaffold — even a wrong scaffold is a place for the next piece to argue with. Relations are guessed before they are fully understood. A wrong draft that can be corrected is more useful than no draft. The output is a rough map: imprecise, incomplete, revisable. That is what it should be. Waiting for a correct map before starting is how the conversion step never starts.

Adding and connecting is the second pass. Each new piece is integrated into the existing structure, not accumulated beside it. The field word assimilation is often used for this step. The move here includes changing the structure when a piece will not fit, so “add and connect” is the honest name. For each new piece three questions do the work: how does this connect? What does it flow from and to? Which existing group does it expand, correct, or subdivide? Importance-Based Chunking is how those nodes get grouped once the relations have been judged.

A piece that cannot be placed yet is flagged and moved past, and returned to after the surrounding structure has developed. Trying to finish every piece before moving on stalls the pass. The work proceeds in layers: approachable concepts first, then secondary ones, then detail. A fact that will not sit is often a frame problem, not a memory problem — the same rule as layered learning, applied here to a single session.

Reorganization takes no new information. It simplifies, corrects misplacements, groups more accurately, and removes noise. The questions: can groupings be simpler? Are the arrows real relations or merely plausible? Is there irrelevant or premature detail? Does the backbone stand out? This is done often — roughly every ten to fifteen minutes during active building, a working heuristic, not a finding. It feels slower because no new content is covered. That felt slowness is the step that converts accumulation into a durable schema. Skipping it to “cover more” is how the pile grows and the network does not.

Schema review is not schema formation. Reviewing revisits an existing network to recognize what is there. It activates what is already connected. Formation builds the connections. The two sessions can look identical from the outside — the same map, the same desk, the same hour — and they do opposite work. One confirms that the stations are still labelled. The other discovers which routes were never laid.

Reviewing an intact schema tests familiarity, not usability. Retrieving from memory without the schema in view — then comparing to find what is missing or wrong — is formation under retrieval conditions. The same distinction as going back over notes versus testing recall. Gaps that surprise during a closed reconstruction were never connected, however many times the map was looked at. That is why the split matters for Spaced Interleaved Retrieval: a reconstruction test is formation. A look back at the finished map is not. A session that never closes the artifact has not formed anything, however long it ran.

In the study system

Schema formation is the central outcome of the encoding loop. BHS is that loop. A short survey before the main event drafts the network — construction. Questions then sharpen the draft: what has to be true, what relates to what. Working the source adds and connects. The last pass takes no new input and reorganizes. Retrieval practice tests reconstruction. Prestudy, Aim, Shoot, and Skin are those jobs under their house names; this page does not re-teach them.

The external form of the schema is a mindmap. GRINDE is the standard for schema quality in final form; that standard is owned there, not here. Best-attempt Encoding is the same formation decision at the level of one concept: build slightly wider than the minimum so the structure is usable under unseen conditions. The margin itself is that page’s.

A tidy outline that cannot be entered from a new question is not a schema. A “review” session that never closes the artifact is not formation. A question that hits any node should reach the surrounding structure; if it cannot, the network is thin in that region. Those are the checkable tests. Readers looking for the three-pass how-to belong on the sibling page, not here.

Skill and procedural schemas exist and look different. A coder or a language learner still needs a network. It may be a set of productions rather than a concept map — if-this-then-that, a motor pattern, a sentence frame. The method does not become a pile either way. The nodes and routes just take a different shape.

The network review will not build

Usable knowledge is a network that can be entered from many points. Reviewing a finished network is not how that network got built.

Related

• Deep Processing — the parent dimension this concept sits inside
• Bear Hunter System — the encoding loop whose outcome is a schema
• Mindmaps — the external form of the schema
• Best-attempt Encoding — the width decision at the level of one concept
• Deep Processing for Research — research-shaped schemas
• Importance-Based Chunking — how nodes get grouped once relations have been judged
• Spaced Interleaved Retrieval — the reconstruction test; why formation is not review
• Knowledge Mastery: From Recognition to Usable Knowledge — usable versus recognized
• Cognitive Load & What Mental Effort Is Trying to Cue — full-cost processing when nothing lands
• Chunking as a Technique — the grouping skill
• Schema Construction, Assimilation, and Reorganization — the how-to of the three passes

Open questions

• Do skill schemas look different enough to change the method, or is a network of productions still built by the same three passes?
• When is a schema detailed enough to generate applications the source never showed?

Sources

• Bartlett, F. C. (1932). Remembering: A Study in Experimental and Social Psychology. Remembering is reconstruction from an organized mass, not a trace replay.
• Piaget, J. Assimilation and accommodation. Field backdrop for adding new material into a structure, and for the structure changing — not this page’s three-pass procedure.
• Sweller, J. (1988). Cognitive load during problem solving. Cognitive Science, 12(2). Learning as schema construction and automation; working memory is relieved as schemas form.
• Sweller, J., van Merriënboer, J. J. G., & Paas, F. (2019). Cognitive architecture and instructional design: 20 years later. Educational Psychology Review.
• Chi, M. T. H., Feltovich, P. J., & Glaser, R. (1981). Categorization and representation of physics problems by experts and novices. Cognitive Science, 5(2). Expert/novice differences are schema differences — principle versus surface.
• Chandler, P., & Sweller, J. (1991). Cognitive load theory and the format of instruction. Cognition and Instruction. Split-attention: one keyword list first.
• Dunlosky, J., Rawson, K. A., Marsh, E. J., Nathan, M. J., & Willingham, D. T. (2013). Improving students’ learning with effective learning techniques. Psychological Science in the Public Interest. Rereading is low utility.
• Roediger, H. L., & Karpicke, J. D. (2006). Test-enhanced learning. Psychological Science. Retrieving without the artifact in view is formation, not review.
• Watch This To Force Your Brain To Study FASTER (2024-11-01). Public video. Transport-network picture; retention versus mastery. The speaker’s paid program is not a source.