LearnPath
DiscoverFindPricingBlog
Sign inGet started
Home›Blog›How to Study Faster When Topics Take Longer Than Planned

Learning guides11 min readUpdated November 9, 2026

How to Study Faster When Topics Take Longer Than Planned

Find out why topics take longer than you plan, compare timeboxing, unpacking, self-testing and spaced repetition, and follow a plan to set study estimates you can hit.

By LearnPath Team

Example path

Your learning path

Pick a topic. We'll turn YouTube into a course.

Tell us your level. We pick the best lessons, put them in order and check you understood each one before the next.

Building your path is free. Ready in about a minute.

If you finish topics far slower than planned, even with good focus, the problem is usually the plan, not your speed. Plans are built from hope instead of from your past pace. Fix it by measuring your real pace, breaking each topic into small steps before you estimate, timing each step, and swapping rereading for self-testing.

The name for this is the planning fallacy: the habit of underestimating how long a task will take, even when you know similar tasks took longer before. It is not a quirk of lazy students. In a 1994 study, Buehler, Griffin and Ross asked psychology students for their best guess of when they would finish their honors thesis. They predicted 33.9 days on average and took 55.5 days. Only about 30 percent finished by their own predicted date.

Quick Answer: Plan From Your Past Pace, Not Your Best Day

You are probably not slow. Your estimates are optimistic, and almost everyone's are. Track your real pace for a week, multiply new estimates by how far off you were, break each topic into small steps, put a timer on each step, and replace rereading with self-testing so the time you spend actually turns into learning.

That is the whole answer. The question that prompted this post came from a student on r/GetStudying who said they focus well but still finish topics way slower than planned. Good focus is the hard part, and they already had it. What they were missing is a plan that matches how long studying really takes, and a study method that does not waste the focused hours. Both are fixable in about a week.

Why topics take longer than you planned

The main reason is that you plan with an "inside view". You picture how this particular topic will go, step by step, on a good day. You do not look at how long the last five topics took. That gap between the picture and the record is where your evenings go, and it shows up in almost everyone.

Daniel Kahneman and Amos Tversky first described the planning fallacy in 1979, in a paper called "Intuitive prediction: Biases and corrective procedures". Their point was that people think about the task in front of them and the steps they expect, and they set aside what happened with similar tasks before. The past record is the best predictor you have, and it is the one most people ignore.

The Buehler, Griffin and Ross study, published in 1994 in the Journal of Personality and Social Psychology, shows how big the gap can be. These were students planning a project they cared about. They still guessed 33.9 days and needed 55.5, even though they were asked for their best estimate.

Douglas Hofstadter put the same idea into a joke in his 1979 book "Gödel, Escher, Bach". Hofstadter's law says: "It always takes longer than you expect, even when you take into account Hofstadter's Law." It is funny because it is true. Simply knowing you are optimistic does not fix it. You need a method that forces your plan to use real numbers.

Work also expands to fill the time you give it

The planning fallacy makes your plan too short. A second effect makes the work too long. If a topic has no clear end, you keep polishing notes, checking one more source, and re-watching one more section. A fixed limit per step stops that drift and shows you what you can really do in the time.

In The Economist on 19 November 1955, C. Northcote Parkinson wrote that "work expands so as to fill the time available for its completion". He was writing about government offices, but it fits a study evening very well. If your plan says "do chapter 4 tonight", chapter 4 has the whole evening to spread into. It usually takes it.

The combination is what hurts. Your estimate for chapter 4 was too short, so you are behind before you start. And because the task has no edge, it grows to fill whatever time is left. You end the night feeling like you worked hard, which you did, and still finished less than you planned.

Passive studying feels fast but is not

Some of the lost time is not lost to planning at all. It is lost to methods that feel productive and leave little behind. Rereading, highlighting and rewatching move your eyes over the material quickly, so a topic feels covered. Then you meet it again a week later and have to learn it a second time.

A 2013 review by Dunlosky and colleagues in Psychological Science in the Public Interest, "Improving Students' Learning With Effective Learning Techniques", rated 10 common study techniques. Practice testing and distributed practice (spreading study over time) got high utility ratings. Rereading and highlighting got low utility ratings. The two most popular habits were near the bottom.

A 2006 study by Roediger and Karpicke in Psychological Science, "Test-enhanced learning", shows why the slow-feeling method wins. In one experiment, students who repeatedly practiced recalling a prose passage remembered 61 percent of it a week later. Students who repeatedly restudied it remembered 40 percent. On a test five minutes later, restudying looked better. That is exactly the trap: rereading wins in the moment and loses over the week.

So if your topics keep "taking longer", ask whether you are counting the re-learning. A topic you reread three times and still cannot explain is not done, and the next pass will cost time your plan never included. We compare the two approaches side by side in active recall vs rereading notes.

Perfectionism and rewatching quietly eat your hours

The last common cause is wanting every topic finished perfectly before moving on. You rewrite notes until they look clean, rewatch a section you half understood, or read three explanations of one idea. Each step feels responsible. Added up, they stretch a topic far past its plan, and most of them add little you could not get from one self-test.

Rewatching is the version that hits people who learn from video the hardest. A confusing two-minute stretch turns into ten minutes of scrubbing back and forth. The better move is usually to keep going, write down the question you have, and test yourself at the end of the section. Often the next part of the lesson answers it. If it does not, you now know exactly which two minutes to rewatch, instead of rewatching everything.

Your realistic options, compared

No single tool fixes slow topics, because the causes are different. Some tools fix the estimate, some put an edge on the work, and some make the hours count. The table shows what each one targets, what it costs, and where it falls short, so you can pick the one or two that match your actual problem.

OptionWhat it fixesCostBest forWeakness
Timeboxing with a timer (for example 25-minute Pomodoro blocks)Work that spreads to fill the evening; shows your real pace in blocksAny timer you already ownPeople who polish and drift inside a topicDoes not fix a bad estimate or a weak study method on its own
Unpacking the topic into subtasks before you estimateEstimates that are too shortPen and paper, a few minutesAnyone whose plans keep running longTakes discipline to do before every topic; still needs your past pace
Practice testing (self-quizzing, writing answers from memory)Hours spent rereading that do not stickNo cost; you write the questionsExams and anything you must recall laterFeels slower and harder than rereading at first
Spaced repetition with AnkiRe-learning the same material laterAnki is free on Windows, macOS, Linux, Android (AnkiDroid) and the web; the official iPhone and iPad app, AnkiMobile, is a one-time USD 24.99Facts, terms and formulas you must keep for monthsMaking good cards takes time; it does not plan your topics
A structured path with quizzes, such as LearnPathChoosing what to study next, and checking understanding before moving onThe Free plan covers step 1 of each path and up to 2 paths; every later step is Pro (see pricing)Learning a new topic from YouTube lessons in orderBuilt on video lessons; does not time your sessions or fix your estimates

A few honest notes on the table. The first two rows are about time, and they work best together. Unpacking makes the estimate longer and more honest. Timeboxing makes the work stop at the edge you set. Neither costs anything, and they are the right place to start if your main complaint is "my plans are always wrong".

The middle two rows are about whether the hours count. Practice testing is one of only two techniques the Dunlosky review rated high utility. Anki adds spacing on top, which matters when you need to keep material for months. Our post on spaced repetition and how it boosts learning covers how to set it up without drowning in cards.

LearnPath is one row here, not the answer. You type a topic and your level, and it builds a path of YouTube lessons in order, with a short quiz after each lesson that checks you understood it before the next one. That removes the "what do I study next" decision and puts a self-test at the end of every lesson. It does nothing about your time estimates, so pair it with the first two rows if those are your problem.

How to fix it: step by step

The plan below turns the research into a routine you can start this week. Do them in order the first time. The first two fix your estimates, the middle two put an edge on each session, and the last two make sure the time you spend becomes learning you keep. It is advice built on the studies above.

  1. Measure your real pace for one week. Before each topic, write down how long you think it will take. Afterwards, write down how long it really took. Do not change anything else yet. You are collecting the record the planning fallacy tells you to ignore. Five to ten topics is enough to see a pattern.

  2. Find your multiplier and use it. Add up your actual times and divide by your planned times. If you planned 10 hours and spent 15, your multiplier is 1.5. From now on, multiply every new estimate by that number before you put it in your plan. It will feel too generous. It is not, it is your own record.

  3. Unpack every topic before you estimate it. Break the topic into its parts: watch the lesson, take notes, do the practice problems, write answers from memory, check the gaps. Estimate each part separately and add them up. Kruger and Evans showed in a 2004 paper in the Journal of Experimental Social Psychology, "If you don't want to be late, enumerate", that unpacking a task into steps led to longer, more realistic estimates.

  4. Put a timer on each part. Give each subtask a fixed block, such as one or two 25-minute Pomodoro blocks. When the timer goes off, stop and move to the next part, even if your notes are not pretty. This is how you push back against Parkinson's law. If a part keeps running over, that is data for your multiplier, not a personal failure.

  5. Swap rereading for self-testing. At the end of each lesson or section, close the material and write down what you remember, or answer a few questions. Then check against the source. Mark only the gaps for review. This feels slower than rereading, and it saves time over the week because you stop learning the same topic twice.

  6. Cut scope on purpose when you fall behind. If the plan still does not fit the time you have, decide what to drop. Keep what will be tested and what the next topic depends on. Skim or skip the rest. A smaller plan you finish beats a big plan you rush through.

After two or three weeks, update your multiplier with the new numbers. As you switch to self-testing and timeboxing, your real pace often changes, and your plan should change with it. If you want help deciding how much daily time is realistic in the first place, see how many hours a day you should study from YouTube.

What to do on a day that still runs long

Even a good plan will run over sometimes. When it does, do not push late into the night to catch up, and do not throw the plan away. Finish the current timed block, write down where you stopped and why it ran long, and move the rest to the next session with an updated estimate.

The note about why it ran long is the useful part. "The practice problems took twice as long as the lesson" is a pattern you can plan for next time. "I rewatched the same section four times" is a sign to self-test sooner. Over a few weeks, these notes turn into a plan that matches you, which is the whole point. A plan that is often wrong in the same direction is not a plan, it is a wish, and you can fix a wish with data.

Frequently Asked Questions

These are the questions people ask next, each answered so it makes sense on its own. The short version of all six: your estimates are too hopeful, so build them from your real pace, break topics into steps, put a timer on each one, and test yourself instead of rereading.

Why do I always finish study topics slower than I planned?

Mostly because the plan was wrong, not because you were slow. People estimate by imagining how this one topic will go and ignore how long similar topics took before. Kahneman and Tversky named this the planning fallacy in 1979. In a 1994 study, students expected to finish a thesis in 33.9 days and took 55.5 days on average.

What is the planning fallacy in studying?

The planning fallacy is the habit of underestimating how long a task will take, even when you know similar tasks ran late before. In studying it shows up as a plan that covers three chapters tonight when your last three nights each covered one. The fix is to plan from your past pace, not from your hopes.

How much extra time should I add to my study estimates?

Use your own numbers, not a rule of thumb. Track how long a week of topics really takes, then divide actual time by planned time to get your personal multiplier. If your plans ran 50 percent long, multiply new estimates by 1.5. Breaking each topic into small steps before you estimate also gives longer, more honest numbers.

Is rereading notes a slow way to study?

Rereading feels fast because the page looks familiar, but it buys little. A 2013 review by Dunlosky and colleagues rated rereading and highlighting low utility, and practice testing high. In a 2006 study by Roediger and Karpicke, students who practiced recall remembered 61 percent of a passage a week later, versus 40 percent after restudying.

Does the Pomodoro technique help you study faster?

It helps you stop polishing and see your real pace. Francesco Cirillo's Pomodoro technique uses 25-minute focused blocks with short breaks. A fixed block puts a limit on a topic, which pushes back against Parkinson's law, the idea that work expands to fill the time you give it. Count how many blocks each topic really takes.

Should I cut topics when I fall behind my study plan?

Often, yes. Falling behind means the plan held more than the time allowed, so something has to give. Keep the parts you will be tested on or need for the next topic, and drop or skim the rest. Cutting a low-value section on purpose beats rushing every section and learning none of them well.

The bottom line

Finishing topics slower than planned is normal, and it is mostly a planning problem. People plan from the inside view, work grows to fill the time it gets, and rereading makes topics feel done before they are. None of that means you are slow.

Start this week. Write down your estimate and your real time for every topic, work out your multiplier, and break the next topic into timed parts. End each part by testing yourself from memory instead of rereading. Within a couple of weeks you will have a plan built on your own numbers, and that is a plan you can actually hit.

On this page

Quick AnswerWhy topics take longer than you plannedWork also expands to fill the time you give itPassive studying feels fast but is notPerfectionism and rewatching quietly eat your hoursYour realistic options, comparedHow to fix itWhat to do on a day that still runs longFrequently Asked QuestionsThe bottom line

Your learning path

Any topic, as a course

The right lessons in order, a short quiz after each.

Build my pathFree to start. Any topic.
Any topic, in the right orderBuild your path free
Start free

Keep reading

Learning guides

How to Build a Study Schedule When You Learn on Your Own

Build a study schedule you can keep as a self-learner: set one goal, measure your real free hours, plan with a buffer, use if-then slots and re-plan every week.

12 min read
Learning guides

How to Study Multiple Subjects at Once Without Forgetting

Learn how to rotate several subjects so each one gets spaced review, where interleaving really helps, and follow a weekly plan that keeps every subject from fading.

12 min read
Learning guides

How Do I Avoid Distractions When Studying on YouTube?

Learn why the YouTube feed pulls you off a study session, compare feed hiders, blockers and settings, and follow a plan to pick each video before you open YouTube.

11 min read

More free YouTube learning guides

  • 10 Best AI YouTube Channels in 2026 for Learning AI
  • 10 Best DevOps YouTube Channels in 2026 (Kubernetes & CI/CD)
  • 10 Best YouTube Channels for Cloud Engineering (AWS, Azure, GCP) in 2026 (Ranked)
  • 10 Best YouTube Channels for Go Programming in 2026 (Ranked)
  • 11 Best YouTube Channels for Kubernetes in 2026 (Ranked)
  • 11 Best YouTube Channels for System Design in 2026 (Ranked for FAANG Interview Prep)
  • 8 Best Unity Game Dev YouTube Channels in 2026 (Beginner to Pro)
  • 8 Best YouTube Channels for Android & Kotlin Development in 2026 (Ranked)
  • 8 Best YouTube Channels for React Native in 2026 (Ranked)
  • 8 Best YouTube Channels for Vue.js in 2026 (Ranked)
  • 9 Best Cybersecurity YouTube Channels in 2026 (Ethical Hacking to SOC)
  • 9 Best Game Development YouTube Channels in 2026 (Unity, Godot, Unreal)
  • 9 Best YouTube Channels for Data Engineering in 2026 (Ranked)
  • 9 Best YouTube Channels for Data Science in 2026 (Ranked)
  • 9 Best YouTube Channels for iOS Development in 2026 (Ranked)
  • 9 Best YouTube Channels for React in 2026 (Ranked)
  • 9 Best YouTube Channels for Rust Programming in 2026 (Ranked)
  • Best YouTube Channel to Learn JavaScript: The 2026 Course
  • Best YouTube Channel to Learn Linux in 2026: The Course Path
  • Best YouTube Channel to Learn Python: The 2026 Course Guide
  • Best YouTube Channel to Learn SQL: The 2026 Course Guide
  • CCNA Course on YouTube: The 2026 Path Before v2.0 Lands
  • CKA Prep on YouTube: The 2026 Path to Passing the Exam
  • CompTIA Network+ (N10-009) Prep on YouTube: The 2026 Path
  • Full-Stack Web Development on YouTube: The 2026 Course
  • How to Become a Site Reliability Engineer: The 2026 Path
  • Learn Machine Learning on YouTube: The 2026 Course Guide
  • Learn Python by Building Projects: The 2026 YouTube Course
  • Power BI Certification Prep on YouTube: The 2026 Path
  • Python for AI in 2026: The YouTube Course and Roadmap
  • RHCSA Prep on YouTube: The 2026 Path to Passing EX200
  • Terraform Certification Prep on YouTube: The 2026 Path
  • TypeScript Tutorial on YouTube: The 2026 Course, Ranked

Ready when you are

Pick a topic. We'll find the lessons and put them in order.

Type what you want to learn. We build the path in about a minute.

Free to start. Any topic.
LearnPath · Learn it. Don't just watch it.
AboutPricingSupportPrivacyTerms