Best books to learn anything faster: a reading order for beginners

Oakley avoided maths and science as a young woman and worked as a Russian translator in the US Army. She later went back to study engineering and ended up as a professor of it. She wrote the book for readers convinced they are "not maths people", but the tools fit any subject that feels hard. At its centre are two modes of thinking, focused and diffuse. Bearing down hard on a problem is part of the work. So is stepping away for a walk, because the brain often makes its connections in that gap. The second big idea is chunking: compressing a sequence of steps into a single mental unit through understanding and repetition.

Why first? It is the least intimidating book on the list, and it tackles the most ordinary obstacle to learning head-on: procrastination. Oakley's advice is to focus on process rather than product, so "twenty-five minutes without my phone" replaces "finish the chapter". This is also where the illusion of competence first becomes clear. Looking at a worked solution and feeling you understand it is not the same as producing that solution yourself.

Its limits are plain. The brain science is deliberately simplified into metaphors, the pinball analogy being the best known, and the examples lean heavily on maths and engineering. If you want research depth, the next book is where you will find it.

Two cognitive psychologists from Washington University in St. Louis, Henry Roediger and Mark McDaniel, wrote this book with the writer Peter Brown. Its central claim is uncomfortably simple. The methods most of us trust, rereading and highlighting, build familiarity with a text, and familiarity is not knowledge. That gap is what the authors call the illusion of fluency. What actually strengthens memory is the effort of pulling information back out: closing the book and writing down what you remember, testing yourself instead of reviewing.

Several other tools join retrieval practice. Spacing spreads study out over time. Interleaving mixes different problem types in the same session. Generation means trying to produce an answer before you see it. Behind them all sits Robert Bjork's idea of desirable difficulties: conditions that make learning harder in the moment but make it last. The findings come wrapped in stories about pilots, surgeons and students, which keeps the research from feeling abstract.

Why second? Oakley gives you the intuition, and this book gives you the experimental ground under it. To be fair, the prose repeats itself in places. Its weight also falls on making information stick, and it says less about pushing a skill to performance level. If you read only one book from this list, it is still the strongest candidate.

Benedict Carey is a science reporter at The New York Times, and his book is good science journalism more than a manual. Its most memorable chapter treats forgetting as a filter for learning rather than its enemy. Robert and Elizabeth Bjork distinguish between a memory's storage strength and its retrieval strength. Effortfully recalling something you have partly forgotten makes it stronger than it was before. That is what we mean by productive forgetting.

Carey also covers ground the other books pass over quickly. He looks at the role of different sleep stages in consolidating memory, the effect of changing where you study, and the incubation that brings a solution once you step away. He also shows how ideas percolate over time in long projects. Stories from his own unremarkable school years keep the narrative warm.

Why third? It overlaps heavily with Make It Stick, and that is not a flaw. Reading the same ideas a second time through different stories is exactly how these books say knowledge gets consolidated. Still, if your time is short, this is the book to skip or skim.

Anders Ericsson is the central figure in expertise research. His 1993 study of violinists at a Berlin music academy was later popularised as the "10,000-hour rule". In Peak, Ericsson rejects that rule outright: what matters is not how many hours you log but how you spend them. Deliberate practice, as he defines it, has well-defined goals. It sits just outside your comfort zone, comes with immediate feedback, and usually happens under a teacher's guidance.

The book's most valuable contribution is the idea of mental representations. Experts carry the patterns of their field as ready-made structures that beginners cannot see. One example makes this concrete. Over months of work, a student named Steve Faloon raised the number of digits he could recall in sequence from around seven to more than eighty. His progress shows how such representations are built step by step.

Why fourth? The books so far are about retaining knowledge; Peak is about improving at a skill. For a balanced reading, it helps to know that Ericsson is a committed advocate of his own view. Some later meta-analyses found that practice explains a smaller share of performance differences than he suggests. Deliberate practice in the strict sense also requires a field with teachers and established training methods, and much of what adults want to learn is not like that.

Scott Young became known for trying to complete MIT's computer science curriculum in about a year using free online materials. He then spent a year learning languages in four countries without speaking English. The book distils nine principles from these projects: metalearning, focus, directness, drill, retrieval, feedback, retention, intuition and experimentation.

Most of those principles are the earlier books put into practice. Young's real contribution is project design, which rests on three moves. First, research how a field is learned before you start. Second, practise in the context where you will actually use the skill. Third, isolate the sub-skill that slows you down most and attack it. For someone facing a job interview in Spanish in three months, that means real conversation practice far more than vocabulary apps.

Why last? If you know the research, the book becomes a template; if you do not, it reads like a hero story. It also calls for some distance. Young's projects were full-time and intense. The MIT challenge was measured by exams, not labs or projects. The book's examples are drawn from people who succeeded. For most readers, scaling the method down to a project of a few hours a week is more realistic.