There is a sentence I hear quite often.
“He is very slow.”
Parents say it. Teachers say it. Students sometimes say it about themselves. I say it too from time to time.
And usually we know roughly what we mean. Homework stretches into the evening. The composition takes too long. The child cannot finish the paper. Another student is already on Question 8 while this one is still working through Question 4.
So yes, the child may genuinely be slower.
I just do not think “slow” tells us enough about what to do next.
It is an observation.
It is not yet an explanation.
Ten minutes can contain very different stories
Imagine two students solving the same Mathematics problem. Both take ten minutes.
The first understands the question immediately. They know the method and their working is accurate, but every calculation is deliberate. They check often because they care about getting it right.
The second also takes ten minutes, but those ten minutes look completely different. Read. Pause. Try something. Erase it. Read again. Search for a formula. Start. Lose the route. Restart.
The clock records the same duration.
The learning problem is not the same.
If I tell both students, “You need to work faster,” I have not been particularly helpful. One may need fluency. The other may need understanding, a clearer method choice, or simply a way to organise the working so they stop rebuilding the route.
This is why I have become wary of treating speed as though it explains itself.
“Slow” compresses too many possibilities
A child can be slow because they are still decoding the question.
Slow because they know the method but retrieve it weakly.
Slow because every basic operation still requires conscious effort.
Slow because they cannot decide between two possible approaches.
Slow because they do not trust their own answer and check the same thing three times.
Slow because their working is disorganised and they repeatedly have to work out where they are.
Slow because they are tired.
Slow because they genuinely think carefully.
And sometimes, of course, slow because they simply do not know what to do.
All of these can produce the same thing on a stopwatch.
That is why the useful question is rarely “How do we make this child faster?”
I would rather ask: where is the time actually going?
Unfortunately, examinations really do have clocks
There is an easy way to make this discussion comforting but unhelpful.
“Every child learns at their own pace. Speed does not matter.”
Sometimes it absolutely does.
An examination ends when it ends. A student who understands every question but completes only seventy per cent of the paper has a real examination problem.
We should not hide that behind gentle language.
But accepting that speed matters does not mean the solution is to keep saying “hurry up”.
If the child needs to produce correct work within two hours, then we need to know what consumes those two hours.
The clock gives us the symptom. The lesson still has to find the cause.
Sometimes speed is really a memory problem
Think about a familiar algebraic operation.
For a secure student, the method arrives almost immediately. They begin.
For another student, there is a search. Was it this rule or that one? Does the sign change here? What did we do last time?
The student may eventually get the answer right. But twenty seconds has become ninety.
Once or twice, that may not matter. Repeated twenty times across a paper, it matters enormously.
The visible problem is “slow examination performance”. The more useful problem may be that knowledge is present but not readily available.
That child does not need to be told to think faster.
They may need the underlying knowledge to become easier to retrieve.
Sometimes the page can make a student faster
I see another kind of slowness in students who try to carry too much in their heads.
They remember one number, transform an expression, hold another number, skip an intermediate line and then lose something. So they stop, go backwards, recalculate and begin again.
The student looks slow.
Perhaps the thinking is slow because the page is not carrying enough of the thinking for them.
Write the intermediate result. Label the quantity. Separate the steps. Leave enough structure on the page that the learner does not have to reconstruct the entire route after every interruption.
Sometimes a child becomes faster without being asked to think faster at all.
They simply stop wasting time recovering information they could have written down.
That is one reason “work faster” can be a surprisingly weak instruction.
Sometimes the faster route is better organisation.
Sometimes slow is buying something useful
This is the awkward case.
A student takes longer than their classmates, but the work is consistently accurate. They are not lost. They are not confused. They are simply cautious.
Do I want to remove that caution?
Perhaps some of it. Excessive checking can become expensive in an examination.
But I have to be careful about what I am trading away.
If I repeatedly push a careful student to rush, I may succeed. The child becomes faster and less accurate.
That is not necessarily progress.
The useful question is: which parts of this slowness are still earning their time?
If an extra thirty seconds catches real errors, perhaps it has value. If the child checks the same obvious arithmetic three times because they do not trust themselves, perhaps that time is no longer helping.
Now the problem has edges.
Fast can hide weakness too
Speed gets rewarded socially. The child who answers first looks strong.
Sometimes they are.
But a fast answer can also be a fast mistake.
A student sees a familiar-looking problem and immediately applies the familiar method. Another pauses for ten seconds and checks whether this is actually the same kind of problem.
The second child was slower.
The second child may also have made the better decision.
So I do not want a simple world in which fast means strong and slow means weak.
Speed is valuable when it comes from secure knowledge, clear recognition and economical execution.
Speed produced by skipping thought is something else.
At home, “slow” can swallow the whole evening
Parents often meet this problem in a much less tidy form.
Homework begins at seven and is still going at ten. Everyone is tired. The child feels they have spent three hours failing. The parent sees three hours disappearing.
But perhaps “three hours of homework” is too large a unit.
Where did the time go?
Was the child actively working for three hours? Were they repeatedly stuck? Switching attention? Looking for materials? Rewriting work to make it perfect? Facing a task that was simply too large for the evening?
Those differences matter because the solution to a three-hour homework session is not automatically “try harder to finish faster”.
Sometimes the child needs a better route. Sometimes a smaller starting task. Sometimes fewer interruptions. Sometimes a missing concept. Sometimes, quite simply, sleep.
The parent does not need to diagnose all of this. Even noticing where the time disappears can make the next conversation with a teacher or tutor much more useful.
Learning slowly is not the same as performing slowly
This distinction helps me a great deal.
Some students need time when a new idea is being built. They ask many questions. They want several examples. They seem slow during the lesson.
Then, once the idea settles, they become perfectly efficient.
Another student understands the idea almost immediately but, weeks later, still executes every step slowly because nothing has become fluent.
These students do not need the same response.
If I rush the first student during construction, I may weaken the understanding. If I keep explaining to the second student when they already understand, I may delay the repetitions that would make the skill economical.
A child can therefore be a slow learner in one sense and a fast performer later, or a quick learner who still needs considerable practice before performance becomes efficient.
The word “slow” cannot carry all of that by itself.
Good examination speed should feel economical, not frantic
As examinations approach, I do want students to become faster.
But the speed I want does not look like panic.
It comes from knowing enough that retrieval is cheap. Recognising the question without excessive hesitation. Writing clearly enough that the route is easy to follow. Checking where checking is worthwhile. Moving on when the work is complete.
That is not rushing.
It is a well-built process becoming economical.
Rushing tries to force the same inefficient process to run faster.
Fluency changes the process itself.
Perhaps the goal is not “fast”
I do not really want a fast student.
I want a student whose use of time matches the task.
Some questions deserve ten seconds. Some deserve ten minutes. Some need an immediate answer because the knowledge should be fluent. Some deserve a pause because choosing the wrong route quickly is still choosing the wrong route.
That kind of judgement is more mature than simply becoming quick.
So the next time I hear, “He is very slow,” I think I would like one more sentence before we decide what the child needs.
Slow where?
Because once we can answer that, the whole child no longer has to carry the label.
There is simply a part of the work that is taking too long.
And that is a much smaller, calmer place to begin.
