The Science of Learning: 5 Principles You Can Actually Use

The science of learning comes down to five principles you can use on any course. Build the structure before the details. Break the material into units small enough to master. Produce the knowledge yourself instead of reading it again. Judge mastery by what you can do, not by how familiar the page feels. Then come back to it over days and weeks so it lasts. Each principle rests on named research, and each one can start tonight.

This is a guide to five principles from the science of learning (structure, small units, action, evidence and review), with the research behind each and one thing to try tonight.

The hours are rarely what's missing. A student on r/GetStudying described the evening exactly: "You read the chapter, watched the lecture, felt fine, then a practice question exposed you completely" (thread). Nothing about that evening was lazy. It was missing the moves that turn time into knowledge you can use, which makes it a method problem, not an ability problem.

Ritsu is an AI tutor designed around these five principles, and the section near the end shows all five on one physics chapter. Start Learning Free

What does the science of learning say about why studying fails?

That the most common study habits put the material back in front of you without asking you to do anything with it. Rereading and highlighting make a page familiar, and familiar feels like known. The exam then asks you to produce the idea from a blank page, which the evening never practised.

In 2013, John Dunlosky and four colleagues reviewed the evidence on ten techniques students commonly use. They rated two as high utility: practice testing, and distributed practice, which means spreading study out over time. Rereading, highlighting and summarizing were among the five they rated low. The review weighed the cognitive science of learning as it stood then, so read it as a ranking of good bets. The five principles below put those bets into one session.

The order matters. The map tells you what the units are, the units tell you what to practise, practice produces evidence, and the evidence tells you what to bring back.

1. Structure: build the map before the details

Before you learn the details, know the five to eight big ideas of the material and which ones depend on which.

Try this first. Read the paragraph below once, then look away and retell it.

Keep the two ends apart until you are ready. Each side has a marked point and an unmarked one, and matching the marks matters more than anything else. Order counts: the last connection goes somewhere other than where it seems to belong. Then the healthy one runs for a few minutes before the other is asked to try. When it works, undo everything in reverse.

It describes jump-starting a car with cables. Read it again now. The sentences haven't changed, but each one has somewhere to land.

John Bransford and Marcia Johnson (1972) built a study around that moment. People heard a passage written so vaguely it was hard to follow (one described washing clothes without saying so). Those told the topic before they heard it rated the passage easier to understand and recalled more of it than those told the topic afterwards.

Experts organize what they know the same way. When Michelene Chi, Paul Feltovich and Robert Glaser (1981) asked physics graduate students and undergraduates fresh from a mechanics course to sort problems, the novices grouped inclined planes with inclined planes; the experts grouped by the principle that solves them, such as conservation of energy. Elon Musk gave the everyday version in a 2015 Reddit AMA, describing knowledge as a semantic tree: the trunk and big branches come before the leaves, "or there is nothing for them to hang on to" (comment).

Tonight (10 minutes): before reading, skim the chapter's headings, summary, bold terms and figures. On one sheet, write the five to eight ideas that look biggest and draw an arrow from each to the ones that need it. Leave it rough. After reading, turn the sheet over and draw the map again from memory: the second map shows what you understood.

In Ritsu: the chapter you upload comes back as an ordered path in which later points build on earlier ones; /mindmap draws a topic's structure and /prereq lists what a concept depends on.

2. Nodes: make the chapter small enough to master

"Learn chapter 4" sounds like a goal, but there is no moment at which you can check it. Can you explain one mechanism? Tell two similar ideas apart? Derive the main equation? Solve the exam's type of problem? Each is a separate piece of knowledge, and each is either done or not. The video calls these pieces nodes; this guide calls them units: one piece of knowledge small enough to practise and check in a single sitting. Try it now: write "learn chapter 4" at the top of a page and, under it, the one question that would prove you've done it. There isn't one.

Tutoring software works at this grain. Albert Corbett and John Anderson (1994) built knowledge tracing for a tutor that taught programming: instead of one verdict on the course, it kept an estimate, rule by rule, of how likely it was that the student had learned each one, and chose the next exercises from those estimates until every rule was mastered.

There is a second reason to keep units small. Nelson Cowan (2001) reviewed the research on how much the mind can hold in focus at once and put the central limit at about four chunks. By analogy, a unit small enough to keep in mind whole is easier to practise and check than a chapter is.

Tonight (10 minutes): rewrite the chapter goal as six to twelve units, each starting with a verb you can check: explain why…, tell X from Y, derive…, solve a … problem. Under each, write the one question that would prove it. A unit without a question is still too vague.

In Ritsu: the plan is made of Points of Knowledge, one idea each, about 5–10 minutes, with a check built in.

3. Action: produce it instead of reading it again

There is a real gap between "this makes sense when I see it" and "I can produce it when the explanation is gone." Rereading trains the first. Exams ask for the second.

Henry Roediger and Jeffrey Karpicke (2006) had students read short prose passages, then either take recall tests (write down everything you remember, no feedback) or reread the passage the same number of times. Five minutes later, rereading was ahead. Two days and a week later, the tested students remembered substantially more, even though rereading had made students more confident.

Explaining works the same way. Michelene Chi and colleagues (1994) asked eighth graders to explain to themselves, line by line, a text about the human circulatory system, while a comparison group read the same text twice. The explainers gained more from the pretest to the posttest, and every student who explained a lot ended up with the correct model of how blood circulates. It was a small study, 24 students in all.

Tonight (25 minutes): close the book. On a blank page, write what you remember of the first unit. Explain its key step in four sentences, as if to a classmate who missed the lecture. Do one problem without notes. Then open the book and mark what you missed in another color: tomorrow's work. Two guides go deeper: active recall without burning out and the Feynman technique.

In Ritsu: /askme puts a question to you before any explanation, and Teach Me The Concepts grades the explanation you write in your own words, then asks the next question from its gap.

4. Evidence: trust what you can do, not how it feels

Mastery is what your performance can support. "I read the chapter." "I studied for two hours." "I think I understand it." All three describe the evening; none describes what you can do. A strong signal is something you produced with the book closed.

Benjamin Bloom (1968) built a way of teaching on this. In "Learning for Mastery," each unit ends with a short check, and anyone who falls short gets corrective work and a second check before moving on. Bloom also treated aptitude as the amount of time a learner needs to reach mastery, not a ceiling on what the learner can reach. When Chen-Lin Kulik, James Kulik and Robert Bangert-Drowns (1990) pooled 108 controlled evaluations of mastery programs, they found positive effects on exam performance, larger for the weaker students in a class, and named the cost: mastery programs can take more time.

Evidence also tells you what to repair. A wrong answer usually has one of three causes: you know the definition but can't apply it, a prerequisite is missing, or the model underneath the answer is wrong. Each needs a different fix. Seen that way, a wrong answer with the working shown is the cheapest diagnosis you will get all week.

Tonight (5 minutes): keep an evidence log next to your unit list. For each unit, write the check question, your closed-book answer, right or wrong, and, if wrong, which of the three causes. A unit counts as done only after a right answer on a later day, or on a problem that looks different from the one you practised.

In Ritsu: every concept gets a 0–100 mastery score earned by practice, which reading alone only nudges; the Knowledge Map lists the lowest first, and a wrong answer gets its misconception named and a guided retry.

5. Review: learn it once, then come back to it

Learning has to survive time. Return to what matters before it fades, and return by recalling it.

Nicholas Cepeda and colleagues (2006) pooled 839 assessments from 317 experiments comparing spaced and massed study of verbal material. Spacing helped, and the gap that worked best grew with how long the material had to be remembered. Their 2008 study put numbers on that. More than 1,350 people learned a set of facts, reviewed them after a gap of up to three and a half months, and took a final test up to a year later. For a test a week away, the best gap was about 20 to 40% of that week; for a test a year away, about 5 to 10% of the year. So a quiz on Friday wants a review a day or two after learning; a final months away wants reviews spread across weeks.

Tonight (5 minutes): before you close the book, write three questions from today's units on a card. Answer them cold tomorrow, again in about three days, and again in a week, writing first and checking second. If you miss one, bring it back sooner. The spaced repetition guide covers how software runs the same schedule.

In Ritsu: Add to Review puts a finished session on a 1–3–7–16–35-day schedule built from your own file; units you get right step up, and misses come back sooner.

What does one evening with all five look like?

About an hour of work around one read-through of the chapter: the map before you read, everything else after. One evening produces and checks one or two units; the rest take the following evenings, each opening with yesterday's card. Here it is on the chapter the video uses: heat engines and the Carnot limit.

Map. Energy is conserved; heat and work are two ways it moves; a heat engine turns some heat into work; the Carnot cycle is the ideal engine; entropy says why some heat must be given up; the efficiency limit, η, sits at the end of the chain.

Units. Six from the chapter: explain why no engine turns all its heat into work; tell heat from temperature; derive η = 1 − Tc/Th from η = W/Qh for a Carnot engine; solve Carnot-efficiency problems; compare an engine's efficiency with a refrigerator's coefficient of performance; apply η to a power plant.

Produce. With the book closed, write η = 1 − Tc/Th from memory. Then the problem: a Carnot engine runs between 227 °C and 27 °C; what is its maximum efficiency? Try it before you read on.

Evidence. Suppose your first attempt reads 1 − 27/227 ≈ 0.88: 88% of the heat turned into work. The formula is right, so the derivation unit passes. The answer is wrong, and the cause sits underneath it: the ratio Tc/Th only means something on an absolute scale, so the temperatures have to be in kelvin. 227 °C is 500 K and 27 °C is 300 K, so η = 1 − 300/500 = 0.40, or 40%. In the log: derive, right; solve, wrong, cause: temperature treated as a plain number; right on the second try. A right answer straight after a correction is not mastery yet, so the problem goes on tomorrow's card with new numbers.

Review. Tomorrow: why must Carnot temperatures be in kelvin? And a new problem, 400 K and 300 K (answer: 25%). In three days: compare η with a refrigerator's coefficient of performance. In a week: explain without notes why no engine working between two temperatures can beat a reversible one.

The 0.88 was the most useful number of the evening. It showed which unit was weak and why, which no amount of rereading would have shown.

What are the common mistakes and edge cases?

• Copying a concept map instead of recalling one. Jeffrey Karpicke and Janell Blunt (2011) had students study science texts either by building concept maps with the text in front of them or by practising retrieval. A week later the retrieval group did better, even on a final test that asked them to draw a concept map. A map works as the frame you read into and the thing you redraw from memory; copied neatly from the open book, it is another way to reread.
• Producing before you have anything to produce. If you can't even guess, read the section once, then close it and start. Retrieval needs something to retrieve.
• Counting one right answer as mastery. Right after studying, the answer is still fresh. Check it again on a later day, or on a problem that looks different.
• Only three days left. Mastery takes time. Cut the units to what the exam covers most, test yourself first, and space what you can: today, tomorrow and the day before.
• Self learning without a syllabus. With no course to set the chapter, the map in principle 1 does the syllabus's job: draw it first and let it choose tonight's units.
• Facts you can look up. A constant or a unit conversion needs none of this; save the five for what you must explain and use. Once they run, mixing problem types in one session is the next habit to add; the interleaving guide explains it.

How do you run the five principles in Ritsu?

Everything above works with a pencil. What wears people down is the bookkeeping: sketching a map of a chapter you haven't read yet, writing a check question for every unit, grading your own answers honestly late at night, and remembering which unit is due on which day. Alone, all of that falls on the person who is also trying to learn the material.

Ritsu was designed around the same five principles. Here they are on the heat-engines chapter from the worked example, as clips of the video above. The video is an animated explainer, so the clips draw each step instead of recording the screen; the screenshots in steps 2 and 4 are the real app.

1. Drop in the chapter (structure). Upload the PDF. Ritsu reads the whole file and returns an ordered path in which later points build on earlier ones, every item traced to the page it came from.

2. Work one Point of Knowledge at a time (nodes). Each point holds one idea, takes about 5–10 minutes and carries its own check, so "learn chapter 4" becomes a list you can finish.

3. Understand it, then produce it (action). When you need the idea first, /explain, /why or /analogy explain it on your own file. Then the work turns to you: /askme puts questions to you, and you explain the idea back in your own words.

4. Read the evidence, then retry (evidence). This is the step that is hardest to do alone. The video draws it on the worked example's own mistake, 1 − 27/227: the formula credited, the application flagged, and the reason named, "Temperatures must be in kelvin." The second attempt reaches 0.40. What you get back is not "wrong, try again" but which part failed and why.

Here is the same move on a real screen, a graded written answer on a different course. The verdict credits what the answer got right, then names the gap plainly: "Most significantly, Part C was missing entirely." Underneath, Counted toward your mastery lists the concepts the answer moved, and Show Solution waits until you ask for it. A concept's 0–100 score moves through practice like this; reading alone barely nudges it.

5. Add the session to Review (review). Press Add to Review when you finish. The session returns on a 1–3–7–16–35-day schedule built from your own file; units you get right step up, and misses come back sooner.

One more thing matters when you study alone: every question and explanation shows the page of your file it came from, so you can check any claim against your own book. To see how a source becomes a path before you sign up, look at Points of Knowledge.

Start with the chapter on your desk this week. Upload it, let the path build, and answer the first question with the book closed. Start Learning Free Free forever · No credit card · No time limit

FAQ

Q: What is the best way to study?

Study by doing, not by reviewing. Break the material into small pieces, explain each one in your own words, then close your notes and recall it, solve problems before checking solutions, fix what you get wrong, and come back to it days later. The top students' edge is how they study, not how long.

Q: Is the learning pyramid real?

No. The chart that gives each method a retention percentage has no study behind its numbers; Letrud and Hernes (2018) found versions going back more than 160 years, none from empirical research. What holds up is narrower: producing the material, by recalling, explaining or solving, tends to beat taking it in again.

Q: Are learning styles real?

People have preferences, but matching instruction to a visual, auditory or kinesthetic style has no adequate evidence behind it (Pashler and colleagues, 2008). Few studies used a design that could test the idea, and several that did contradicted it. Pick the format the material needs, a diagram for a circuit or sound for pronunciation, and use it to produce.

Q: What is mastery learning?

Mastery learning is an approach in which you move on only after showing you have mastered the current unit, instead of after a fixed amount of time. Benjamin Bloom described it in 1968. Each unit ends with a check; anyone who falls short gets correction and another try before continuing.

Q: How do you beat the forgetting curve?

You can't stop forgetting, but you can slow it. Recall the material soon after learning it, then again at growing intervals, and recall it rather than reread it. Each effortful return makes the memory last longer. Connecting new ideas to what you already know also makes them easier to retrieve later.

Q: What does Make It Stick say about studying?

Make It Stick: The Science of Successful Learning (2014), by Peter Brown, Henry Roediger and Mark McDaniel, argues that rereading and highlighting create an illusion of mastery. It recommends testing yourself, spacing practice out, mixing problem types and accepting practice that feels harder.

Q: Can Ritsu run these five principles on my own material?

Yes. Upload a chapter, slide deck, lecture video or paper, and Ritsu turns it into an ordered path of Points of Knowledge, asks before it explains, grades your answers and explanations, scores each concept from what you do, and brings sessions back on a review schedule. You can start on the Free plan: Free forever · No credit card · No time limit.

The takeaway

The hours were never the problem; the evening was missing five moves: map it, cut it small, produce it, check it, and come back to it.

Tonight, draw the map of the chapter you're studying on paper first, then upload it to Ritsu and compare its path with yours. Start Learning Free

Sources

• Bloom, B. S. (1968). Learning for mastery. Evaluation Comment, 1(2). UCLA Center for the Study of Evaluation of Instructional Programs. https://eric.ed.gov/?id=ED053419
• Bransford, J. D., & Johnson, M. K. (1972). Contextual prerequisites for understanding: Some investigations of comprehension and recall. Journal of Verbal Learning and Verbal Behavior, 11(6), 717–726. https://doi.org/10.1016/S0022-5371(72)80006-9
• Brown, P. C., Roediger, H. L., III, & McDaniel, M. A. (2014). Make It Stick: The Science of Successful Learning. Belknap Press of Harvard University Press. https://www.hup.harvard.edu/books/9780674729018
• Cepeda, N. J., Pashler, H., Vul, E., Wixted, J. T., & Rohrer, D. (2006). Distributed practice in verbal recall tasks: A review and quantitative synthesis. Psychological Bulletin, 132(3), 354–380. https://doi.org/10.1037/0033-2909.132.3.354
• Cepeda, N. J., Vul, E., Rohrer, D., Wixted, J. T., & Pashler, H. (2008). Spacing effects in learning: A temporal ridgeline of optimal retention. Psychological Science, 19(11), 1095–1102. https://doi.org/10.1111/j.1467-9280.2008.02209.x
• Chi, M. T. H., de Leeuw, N., Chiu, M.-H., & LaVancher, C. (1994). Eliciting self-explanations improves understanding. Cognitive Science, 18(3), 439–477. https://doi.org/10.1207/s15516709cog1803_3
• Chi, M. T. H., Feltovich, P. J., & Glaser, R. (1981). Categorization and representation of physics problems by experts and novices. Cognitive Science, 5(2), 121–152. https://doi.org/10.1207/s15516709cog0502_2
• Corbett, A. T., & Anderson, J. R. (1994). Knowledge tracing: Modeling the acquisition of procedural knowledge. User Modeling and User-Adapted Interaction, 4(4), 253–278. https://doi.org/10.1007/BF01099821
• Cowan, N. (2001). The magical number 4 in short-term memory: A reconsideration of mental storage capacity. Behavioral and Brain Sciences, 24(1), 87–114. https://doi.org/10.1017/S0140525X01003922
• 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, 14(1), 4–58. https://doi.org/10.1177/1529100612453266
• Karpicke, J. D., & Blunt, J. R. (2011). Retrieval practice produces more learning than elaborative studying with concept mapping. Science, 331(6018), 772–775. https://doi.org/10.1126/science.1199327
• Kulik, C.-L. C., Kulik, J. A., & Bangert-Drowns, R. L. (1990). Effectiveness of mastery learning programs: A meta-analysis. Review of Educational Research, 60(2), 265–299. https://doi.org/10.3102/00346543060002265
• Letrud, K., & Hernes, S. (2018). Excavating the origins of the learning pyramid myths. Cogent Education, 5(1), 1518638. https://doi.org/10.1080/2331186X.2018.1518638
• Musk, E. (2015, January 5). Comment in "I am Elon Musk, CEO/CTO of a rocket company, AMA!" r/IAmA, Reddit. https://www.reddit.com/r/IAmA/comments/2rgsan/comment/cnfre0a/
• Pashler, H., McDaniel, M., Rohrer, D., & Bjork, R. (2008). Learning styles: Concepts and evidence. Psychological Science in the Public Interest, 9(3), 105–119. https://doi.org/10.1111/j.1539-6053.2009.01038.x
• Roediger, H. L., III, & Karpicke, J. D. (2006). Test-enhanced learning: Taking memory tests improves long-term retention. Psychological Science, 17(3), 249–255. https://doi.org/10.1111/j.1467-9280.2006.01693.x

By Ritsu Team · Last updated October 18, 2026