Pacing Skill Development

Two or three processes in the active set is the cap, each one a problem sitting in the way of the next hour. It feels too slow and is how a skill actually lands. The picture in the way is skill-building as collecting tools.

Why fewer is faster

A tool can be picked up and used. A skill cannot. Each one is a problem sitting in the way of the next hour: something blocks performance, the block has a cause, a solution has to be tried, and the loop repeats. That decoding costs load. Exposure is not the cost. The expectation is a kit that grows by addition — another method, another technique, another item on the list. The work is solving one problem well enough that the next one can use what was learned.

Split the same limited capacity across many skills and none of them get enough of that work. Each skill has variables that have to be decoded before it will run. High element-interactivity already strains working memory inside one skill. Across five at once, the same hours produce confusion and frustration instead of a landing. Competence arrives in none.

The cap is two or three processes — the active set being trained, not the whole skill list. The integer is this system’s working default, the same ceiling used when stacking small improvements on the current few in Marginal Gains in Practice. No trial has shown that two or three beats four or five as a measured optimum. The instruction is the cap, not the constant.

A student who needs critical thinking, essay writing, encoding, retrieval, and time management in two months, from a basic baseline, cannot grow all five in time. The move is still to grow each as fast as possible, by running fewer at once. The others wait in the pool. The price is that wait, paid in the same breath as the speed. A deadline that truly needs five skills from a basic baseline will not grow them all. The cap does not invent time. Measuring Learning is which two or three: the rate limiters. This page is how many.

A named change inside a fortnight is the checkable sign that a process is actually active. If none of the two or three is moving, the pick is the problem, not the cap — and that test lives next door.

The real miss is a layer

Those two or three processes are not only a count. They are how a later layer stays available. What fails is a missing kind of method, not a skipped line in the notes. A system with no method that forces comparison, judgment, and relationships lets interrelational questions walk through every pass. The skipped fact is not the risk. The missing layer is.

Why the fear of details backfires

A learning system works like stacked layers, each with holes. Encoding, then retrieval, then encoding again: each pass misses something different, and a later pass can catch what an earlier one missed — if a later layer of that kind exists. The image is a Swiss-cheese model: several imperfect layers covering different misses. It is a metaphor. It is not a proof that misses get caught. The model those layers are borrowed from is a model of residual failure when holes align. When every layer is the same kind, the miss goes through.

A detail skipped now often gets picked up later, by a technique better suited to it. That consolation holds only when the later layer exists. A fact that is too detailed for the current network is overload if forced now, and a cue once the surrounding network exists. Isolated elements first, then interacting ones: the same sentence is load for a novice and easy later. Not all information is equal.

Order Control is taking information in the order the current network can hold, not the order the chapter printed it. Prestudy is the layer that decides what is too detailed to take now.

Focusing on details because of a fear of missing them makes them more likely to be forgotten. Isolated notes encode weakly. Organisation is what retention uses, and isolation has none. Tidy notes then feel like fluency — the page looks complete, the network was never built. The harvest is the slowdown. The old reassurance on this page was that skipped details come back later. They do, when a later layer of the right kind exists. The warning is the other half: the frightened harvest is itself the reason they do not come back.

The cap that keeps a layer

Two or three at a time still looks slow. It is how a later layer stays in the system — the layer that can actually catch. The frightened harvest of isolated details is the same slowness wearing a costume. Fix the missing method, not the individual detail. If none of the two or three is moving, the pick is the problem, and that test lives in Measuring Learning.

Links into the knowledge base

• Measuring Learning — rate limiters tell which two or three to pick; this page is how many
• Marginal Gains in Practice — the practice of stacking small improvements on the current few
• Order Control — take information in the order the current network can hold, not the chapter’s
• Prestudy — the layer that decides what is too detailed to take now

Open Questions

When a later layer of the missing kind cannot be added in time, what is the honest move — drop the fact, or drop the deadline’s implied scope?

Sources

• van Merriënboer, J. J. G., & Sweller, J. (2005). Cognitive load theory and complex learning. Educational Psychology Review. Few interacting elements at once; the load half of the cap.
• van Merriënboer, J. J. G., Kester, L., & Paas, F. (2006). Teaching complex rather than simple tasks. High element-interactivity overwhelms working memory when too much is live at once.
• Pollock, E., Chandler, P., & Sweller, J. (2002). Assimilating complex information. Learning and Instruction. Isolated elements first, then interacting elements — why a fact too detailed now becomes easy later.
• Kalyuga, S., Ayres, P., Chandler, P., & Sweller, J. (2003). The expertise reversal effect. The same detail is load for a novice and a cue once the schema exists.
• Craik, F. I. M., & Lockhart, R. S. (1972). Levels of processing. Isolated, shallow encoding is what the frightened harvest produces.
• Bjork, R. A., Dunlosky, J., & Kornell, N. (2013). Self-regulated learning: Beliefs, techniques, and illusions of competence. Annual Review of Psychology. Tidy notes as fluency.
• Reason, J. (1990). Human Error; Reason, J. (2000). Human error: models and management. BMJ. Swiss cheese as residual failure when holes align — the model being scoped, not a proof that later layers catch.