You followed the lesson and every step made sense. You read the chapter and nothing in it felt new. Then you opened the exercises and the pen stopped. "I understand the topic but I can't solve the problems" is one of the complaints teachers hear most, and the cause is almost never intelligence. Two different skills are being mixed up: recognising information when it is in front of you, and retrieving that same information on a blank page and putting it to work.
Seeing that distinction is half the job. The other half is working out which kind of mistake you are making, because a knowledge gap and an arithmetic slip do not respond to the same cure.
Why is understanding a topic not the same as solving problems?
Because understanding is usually recognition, and solving is retrieval plus production. During an explanation the information sits in front of you; your mind's job is to follow along and say "yes, that makes sense". In a problem the information is not in front of you. You have to call it up yourself, decide which part is needed and apply it step by step. Memory research has long shown that recognising is far easier than recalling. When a song plays you can sing along; try singing it from the start in silence and you stall on the second line. Did you know the song? You recognised it.
There is also a trick your mind plays on you. A well-explained topic flows smoothly, and because you followed it without stumbling you get a feeling of "I know this". The name for it is the fluency illusion: processing something easily gets confused with knowing it. Reading worked examples sets the same trap. Every step of the solution makes sense, you nod at every step, but nodding is not producing. The hard decisions were made for you by whoever wrote the solution: which formula, which order, which transformation. In your own problem, you have to make them.
The third reason is that problems do not ask for knowledge in the form you learned it. The textbook teaches ratio as a comparison of two quantities; the problem hands you a cake recipe and asks how much milk goes with 12 cups of flour if 3 cups take 2. A bridge is needed in between: "Which topic is this, which rule?" Call it matching. It never gets practised during a lesson, because during a lesson you already know which topic you are in. It develops only when you solve mixed problems.
Finally, reading and calculation errors are a class of their own. You know the topic, you find the method, you match correctly, and then you multiply 7 by 8 and write 54, or you tick the true statement when the question asked for the false one. These are not knowledge gaps, and rereading the chapter does nothing for them. So the first task is to sort your mistakes by class.
What kind of mistake are you making? A diagnosis table
Take your last twenty wrong answers and place each one in a row below. If they pile up in one row, the prescription is obvious; if they spread out, start with the fullest row.
| Symptom | What is missing | First step |
|---|---|---|
| Nothing comes to mind when you read the question | Knowledge | Write the topic closed-book, then fill the gaps from the book |
| You can explain the topic but don't know where to start | Method | Study three worked examples of the type, then solve three yourself |
| You see the solution and think "oh, it was that topic" | Matching | Solve mixed-topic sets; write the topic and rule before each answer |
| You misread the question or skipped a given | Reading | List what is given, write what is asked in one sentence |
| Right method, wrong result | Calculation | Write every step, then check the result against the question |
| Fine at home, out of time in the exam | Speed | Practise with a timer; mark hard questions and move on |
The table's real job is to break a huge sentence like "I can't solve problems" into small, fixable parts. A knowledge gap closes with the book. A method gap closes with worked examples and imitation. A matching gap closes only with mixed problems; rereading the chapter does not touch it. Reading and calculation errors are fixed not with knowledge but with habits: slowing down, writing things out, checking.
An example: if twelve of your last twenty maths mistakes land in the "right method, wrong result" row, rereading the chapter gains you nothing, because those mistakes come from haste. If most sit in the "nothing comes to mind" row, more problems are wasted until you have been back to the book. Without a diagnosis you treat both with more questions, and nothing changes.
How do you get from worked examples to solving on your own?
In three stages: read and close, complete one step yourself, then do all of it yourself. A finding that comes up again and again in learning research is that for someone just starting a topic, studying a worked example is more productive than solving from scratch, and that this reverses with practice, when solving on your own takes over. Most students never leave stage one: they read example after example, understand them all, and go into the test without having written a line.
1. Read, close, write. Read the worked example once, carefully. Then close it and solve the same problem from the beginning on a blank sheet. When you get stuck, don't peek straight away; think for a minute first, then look, then close it again. The step where you got stuck is the real boundary of your "I understand".
One more habit pays off while reading an example: at every step, ask "why was this step taken?" and answer, even in a single word. A step you cannot explain is a step you have not understood, so stop there. Learning research calls this self-explanation, and it gets far more out of the same example.
2. The half-finished solution. On a new example of the same type, cover the last step of the solution and write it yourself. On the next one cover the last two steps, then half the solution. The load shifts to you gradually, and at no stage are you left alone in front of an empty page.
3. From scratch. Without opening any example, solve three problems of the same type. If all three are right and you can say why you did each step, that type is done. The part to watch is "say why": a right answer can come by luck, a reason cannot.
Should you finish the topic first or start solving problems?
Both, in pieces. Split the topic into small sections and solve three to five problems right after each one. While the section is small, matching is easy, and when a mistake appears you know where it came from. A student who finishes the whole topic and then sits down to the test cannot tell, twenty pages later, which page the error in question one came from; the mistakes pile up and turn into "I just can't do this topic".
End every study session with a closed-book check as well. Shut the book and the notes and, within ten minutes, write down the rules, formulas and one sample problem from that session from memory. Whatever you cannot write is the part you only recognised while thinking you had understood it. Those ten minutes tell you more than an hour of rereading, because testing yourself both measures knowledge and strengthens it. How that works, and how to turn it into a revision schedule, is covered in the guide to spaced repetition and active recall.
In what order should you solve problems?
Easy to hard, without skipping the easy ones. A problem carries three loads at once: understanding the text, choosing the method and carrying out the calculation. All of that is held in working memory, the amount of information you can keep in mind at one moment, and its capacity is limited. Jumping to a hard problem on a freshly learned topic means loading all three at once, and usually you can carry none. Easy problems make the method automatic; once it runs on its own, a hard problem leaves only the text and the decisions.
The signal for moving up a level is this: four or five problems of the same type right in a row, and you can explain each one by answering "why did I do it this way?". Getting faster is not a signal; a memorised pattern is fast too, and it collapses at the first problem that looks different.
Once a type has settled, it is time to mix: when you finish a topic, solve its problems shuffled with problems from earlier topics. It feels harder and produces more mistakes at first, but this is exactly where matching gets trained, because every problem forces you to answer "which topic?" yourself. The exam works the same way: no question has its topic written above it.
How do you keep an error log, and what is it for?
One line per mistake: a short description of the problem, the error type from the table, and what you will do differently next time. Do not copy out the whole solution; the log is not an archive of answers but a map of your errors. When you look through it once a week and see the same type repeating, your study direction has just changed. How to take a full mock exam apart this way is in the practice-test analysis guide.
With tests that explain their solutions, one small rule changes a lot: write your own solution before reading the explanation. When a question comes back wrong, resist going straight to the explanation; write your own steps beside it first, then compare the two to see exactly which step went wrong. Read the explanation first and you will say "ah, yes", and the fluency illusion is back at work. Why testing yourself has such a strong effect on learning is explained in the benefits of practice tests.
When should you go back to the topic?
When two out of three problems show the same type of error. That is a clear enough signal to stop; a single wrong answer is not. What going back looks like depends on the error type. For a knowledge gap, reread only that part of the topic and confirm it with a closed-book check. For a method gap, run the worked-example stages again. For a matching gap, going back does not mean the topic at all but a mixed test, because one more explanation will not move you a step further.
The opposite of going back exists too: not daring to move on. A student reading the topic for the fifth time usually feels safe but is only polishing the recognition level. Four or five right answers in a row, with reasons you can give, mean it is time for the next topic. If a gap is left, a mixed test will expose it anyway.
The same decision exists for a single problem: how long to keep struggling with it. As a general frame, a few minutes of real thinking is productive; half an hour of staring is not. A solution you read after genuinely trying sticks better than one you read cold, because your mind knows what it was looking for. Past a certain point, though, what builds up is fatigue, not learning.
Understanding the topic is the start of the road, not the end. Once you can produce what you understood with the book closed, match a problem to its topic, and name the type of your mistake, the sentence "I can't solve problems" disappears on its own. Intelligence does not change; the way you study does, and the results follow.
Frequently asked questions
I understand the solution when I read it but can't do it myself. Is that normal?
Yes, it is the most common situation of all. Reading a solution is recognition; solving is production, and the second is harder. Once you start reading a worked example, closing it and writing the same problem out from the beginning, the gap begins to close within days.
Should I finish the topic first or start solving problems?
Go in pieces: solve a few problems right after each small section of the topic. That way, the moment a mistake appears you know where it came from. Finishing the whole topic and then testing piles the mistakes up and hides their causes.
How many problems should I solve a day?
There is no single number. As a general frame, ten to twenty problems on one topic per session, with the type of every mistake written down, teach more than a hundred solved without analysis. Increase the number only as long as you still have time to classify the mistakes.