Retrospect | Tuition | RFE | Help
There is a sentence I hear quite often.
“He is very slow.”
Parents say it.
Teachers say it.
Students say it about themselves.
Sometimes I say it too.
And usually everyone knows roughly what we mean.
The worksheet takes too long.
The composition takes too long.
The child cannot finish the paper.
Homework stretches into the evening.
Another student has already completed Question 8 while this student is still somewhere inside Question 4.
So yes.
The student is slower.
But lately I have been thinking that this may be where the useful information begins, not where it ends.
Because:
slow is something we observe.
It is not necessarily what is wrong.
Two Students Can Take Ten Minutes for Completely Different Reasons
Imagine two students solving the same Mathematics problem.
Both take ten minutes.
Student A understands the question immediately.
They know the method.
Their working is accurate.
But every calculation is deliberate.
They check frequently.
They rarely make mistakes.
Student B also takes ten minutes.
But the ten minutes look completely different.
Read.
Stop.
Try something.
Erase.
Read again.
Ask which formula applies.
Start.
Lose the route halfway through.
Restart.
Same duration.
Different machinery.
If I treat both students with:
“You need to work faster,”
I have not diagnosed very much.
One may need fluency.
The other may need understanding.
I Think We Compress Too Much Into the Word “Slow”
A child can be slow because they are still decoding the question.
Slow because retrieval is weak.
Slow because every basic operation still requires conscious effort.
Slow because they cannot decide between two possible methods.
Slow because they are afraid to commit to an answer.
Slow because they repeatedly check things that no longer need checking.
Slow because their working is disorganised and they keep reconstructing where they are.
Slow because they genuinely think more deeply.
Slow because they are tired.
Slow because they do not know what to do.
All of these can produce the same thing on a clock.
Ten minutes.
That is why I have become uncomfortable with treating speed as though it explains itself.
It doesn’t.
The Examination Does Care About Speed
There is another easy mistake here.
We could say:
“Every child learns at their own pace. Speed doesn’t matter.”
Unfortunately, sometimes it does.
An examination has a clock.
Pens down means pens down.
A student who understands every question but completes only 70 percent of the paper has a real examination problem.
We should not hide that behind comforting language.
If the environment requires a capability within two hours, then the time component is part of the capability.
But that still leaves the important question:
What is consuming the time?
Because the answer determines the repair.
Sometimes Speed Is Really a Knowledge Problem
A student encounters 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?
What did the tutor say?
Was the negative sign supposed to change here?
The student eventually gets the answer correct.
But twenty seconds became ninety.
If this happens once, perhaps it does not matter.
If it happens twenty times inside a paper, the student runs out of time.
Now the visible problem is:
slow examination performance.
But the underlying problem may be:
knowledge that is present but not sufficiently retrievable.
That is a different problem from simply telling the student to hurry.
Sometimes the Child Is Carrying Too Much
I see this with working quite often.
A student tries to keep several steps in their head.
They do not write an intermediate line.
They remember a number.
Transform an expression.
Hold another number.
Then something disappears.
Stop.
Go backwards.
Recalculate.
Continue.
The student looks slow.
But perhaps the process is slow because the working memory is being used as storage.
A small change in written structure may make the student faster without asking them to think faster at all.
Write the intermediate result.
Label the quantity.
Separate the steps.
Now the page carries some of the load.
The brain does not have to.
This is why:
“Work faster.”
can be a very weak instruction.
Sometimes the faster route is not more speed.
It is less load.
Sometimes Slow Is Actually Careful
This one is awkward.
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?
Perhaps some of it.
In an examination, excessive checking can become expensive.
But I should be careful.
If I repeatedly tell a naturally careful student to rush, I may eventually succeed.
They become faster.
And less accurate.
Congratulations.
I repaired the number on the stopwatch and damaged the capability.
That is not a good trade.
The useful question is not:
How do I make this student fast?
It is:
Which parts of this student’s slowness are still buying something useful?
If the extra thirty seconds catches real errors, perhaps it has value.
If the student checks the same obvious arithmetic three times because they do not trust themselves, perhaps that time is no longer earning its place.
Now we have something to work on.
Three Students Make This Very Easy to See
This is one of the advantages of teaching three students together.
One finishes quickly.
One follows shortly afterwards.
One is still working.
It is tempting to create a ranking.
Fast.
Medium.
Slow.
But when I watch more carefully, the ranking often becomes much less interesting than the mechanisms.
The fast student may be fast because the knowledge is fluent.
Good.
Or fast because they skipped half the reasoning.
Not so good.
The slow student may be slow because the concept is missing.
Problem.
Or because they are constructing a very strong solution carefully.
Different problem.
Or perhaps no problem at all yet.
The clock tells me who finished first.
It does not tell me who learnt best.
Fast Can Hide Weakness Too
I think this matters because speed gets rewarded socially.
The child who answers first looks clever.
Sometimes they are.
But quick performance can also hide shallow processing.
A student sees a familiar surface pattern.
Immediately applies the familiar method.
Wrong.
Another student pauses.
Checks whether the problem really is the familiar type.
Chooses correctly.
The second student took longer.
But perhaps their decision system is better.
So we should not create a simple world where:
fast = strong
and
slow = weak.
Reality is much messier.
What I Really Want to Know Is Where the Time Goes
This may be the most practical question in the whole article.
Not:
“Why are you so slow?”
That is too large and can sound like a judgement.
Instead:
“Where did the time go?”
Read the question again.
Did understanding it take too long?
Did choosing the method take too long?
Did the calculations take too long?
Did checking take too long?
Did the student stop because they were uncertain?
Did they restart unnecessarily?
Suddenly “slow” starts decomposing.
And once it decomposes, the intervention can become smaller.
A Stopwatch Is Useful Only If We Know What We Are Timing
There is a temptation in examination preparation to time everything.
Ten minutes.
Fifteen minutes.
One hour.
Good.
Timing is useful.
But a stopwatch tells me how long.
It does not tell me why.
If a student takes twelve minutes instead of eight, I still need to inspect the twelve minutes.
Perhaps three minutes disappeared because the student did not know one prerequisite.
Teach it.
Perhaps two minutes disappeared because every multiplication fact was retrieved slowly.
Build fluency.
Perhaps two minutes disappeared because the student reread the question five times.
Improve representation.
Perhaps the student simply writes slowly.
That may require an entirely different decision.
The clock is a sensor.
It is not the diagnosis.
Parents Often See the End of the Time Problem
This becomes painful at home.
Homework begins at seven.
It is still going at ten.
Everyone becomes frustrated.
The parent sees three hours of homework.
The child experiences three hours of failure.
But perhaps the useful unit is smaller.
What consumed those three hours?
Was the child actually working for three hours?
Were they stuck repeatedly?
Did they lack knowledge?
Were they switching attention?
Was the task genuinely too large?
Did perfectionism make every answer take three times longer?
These 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 task.
Sometimes a missing concept.
Sometimes fewer interruptions.
Sometimes sleep.
I Think We Should Separate Learning Speed From Execution Speed
This distinction helps me.
A student may learn a new concept slowly.
They need examples.
They need time.
They ask many questions.
But once the concept is built, their execution may become perfectly fast.
Another student learns the idea almost immediately.
Wonderful.
But weeks later, they still execute it slowly because nothing has become automatic.
These are different students.
The first needs enough time during construction.
The second may need repetition after construction.
If I rush the first because they look slow during learning, I may damage the construction.
If I keep explaining to the second when what they need is fluency practice, I may waste time.
So:
learning speed and performance speed are not the same thing.
That is worth retaining.
Slow Today Can Be Fast Tomorrow
There is also a time dimension.
When a student first learns simultaneous equations, they may be painfully slow.
That is not surprising.
The procedure is new.
Every choice is conscious.
With understanding and practice, groups of steps become chunks.
What once required ten conscious decisions becomes three.
The student speeds up.
This is ordinary learning.
So the first slow attempt should not automatically trigger intervention.
The question is whether speed is changing as capability stabilises.
If the student remains equally slow after substantial correct practice, then we investigate.
The trajectory matters.
But More Practice Is Not Always the Answer
Suppose the student has completed fifty questions.
Still slow.
Perhaps they need fifty more.
Maybe.
But perhaps the practice is exercising the wrong bottleneck.
If every question requires the student to rediscover a poorly understood concept, repetitions alone may simply reproduce slow uncertainty.
If the issue is method selection, fifty identical questions may not help because the method is always obvious from the worksheet heading.
If the issue is examination switching, isolated practice may never expose it.
Again, reality should guide us.
Practice.
Observe.
Did the relevant part speed up?
If yes, continue.
If no, change the explanation of the problem.
Speed Should Be Located, Not Demanded
This may be the compact rule.
Do not demand speed everywhere. Locate where speed is being lost.
That changes the tone of tuition.
Instead of:
“You are too slow.”
we can say:
“You understand this quickly, but calculation is taking too long.”
Or:
“Your calculations are fine. Most of the delay is deciding how to start.”
Or:
“You’re actually fast until you make one mistake, then you spend a long time rebuilding the answer.”
Those sentences are much more useful.
They also feel different to the child.
The student is no longer globally slow.
There is a specific piece of the process that needs improvement.
Specific problems are usually easier to live with.
And easier to repair.
Examination Training Should Eventually Compress the Route
As examinations approach, I do want students to become faster.
But I think the best speed comes from compression.
Know the knowledge well enough that retrieval is cheap.
Recognise the question efficiently.
Represent it clearly.
Choose without unnecessary hesitation.
Execute with enough structure that you do not repeatedly backtrack.
Check where checking is valuable.
Move on.
That is not rushing.
It is a well-built route becoming economical.
There is a big difference.
Rushing tries to make the same inefficient system run faster.
Fluency changes the system.
This Is Why Telling a Student to “Hurry Up” Rarely Teaches Much
Sometimes “hurry up” is necessary.
We are late.
The paper is ending.
The student is daydreaming.
Fine.
But as an educational intervention it contains very little information.
Hurry how?
Read faster?
Think faster?
Retrieve faster?
Write faster?
Check less?
Choose sooner?
The student already knows time is passing.
What they often do not know is which part of their process is costing the time.
That is what the tutor should help reveal.
Reality Has to Decide Whether the Speed Improvement Is Real
Suppose we believe retrieval is the bottleneck.
We practise retrieval.
Good.
Now retest.
Does the student begin faster?
Does that improvement survive tomorrow?
Does it survive inside mixed questions?
Does the total paper timing improve without accuracy collapsing?
If yes, we probably found something real.
If no, perhaps retrieval was not the main bottleneck.
Change the model.
Likewise, if a student becomes faster but starts losing more marks, that is not automatically progress.
The point is not to minimise seconds.
The point is to produce enough correct capability inside the available time.
The examination clock matters.
But correctness still matters too.
Perhaps the Goal Is Not Fast
This is where I finally arrive.
I do not really want a fast student.
I want a student whose time matches the task.
Some questions deserve ten seconds.
Some deserve ten minutes.
Some deserve a pause before commitment.
Some require immediate retrieval.
The mature learner needs to distribute time intelligently.
That is different from simply becoming quick.
So perhaps after saying:
“He is very slow,”
there should always be another sentence.
Slow where?
Because once we can answer that, the problem becomes much smaller.
Maybe the child needs teaching.
Maybe fluency.
Maybe structure.
Maybe confidence.
Maybe a decision rule.
Maybe nothing yet except more experience.
And that is a far more useful place to begin than asking the whole child to somehow become faster.
eduKate Sengkang 