How Sam Went From 1280 To 1520
Everyone was sure the problem was pacing. For a year. It wasn’t.
David breaks down exactly how it happened, step by step.
Apply for a free assessmentAct I
The year everyone fixed the wrong problem
Sam, his tutor, and his dad all agreed on the diagnosis. It was reasonable, it was obvious.. and it was wrong.
Everyone agreed: it was pacing
Sam kept reaching the end of each section with no time left. The last questions were getting rushed, guessed, or skipped altogether.
So his tutor did what most reasonable people would do.. worked on pacing. Time checkpoints, when to leave a hard question, timed sections over and over. Sam did the work, and he genuinely got faster.
The only problem was that the score didn't move.
Faster every month. Same score every test.
Doing everything right, going nowhere
They'd found a professional. The student was putting in the effort. There was a clear problem being worked on. Months later.. basically the same place.
The issue wasn't effort, and it wasn't necessarily the tutor. Everybody had correctly identified what was happening. Nobody had figured out why.
Act II
The audit told a different story
Instead of another pacing strategy, we went through his test question by question. The “pacing issue” started looking very different.
He was doing every question twice
Sam understood exactly what most of the math questions were asking. The problem happened when he turned that understanding into an equation. He'd build the wrong setup, solve it correctly, get to the end.. and the answer wasn't one of the choices.
Then he'd reread the whole question, find the mistake, rebuild, and solve it again.
Once, that costs a minute. All section long, it explains the empty clock.
Sam wasn't slow. Something earlier in his process kept forcing him to start over. And on top of it, questions he knew cold were leaking points to small execution slips.. a number copied wrong, a flipped sign.
“Careless mistakes” is a misleading phrase
Two students can miss the exact same question for completely different reasons.
You wouldn't fix these three students the same way. A score report can't tell them apart.
That's the distinction the audit is built on. Knowing where a student lost the point is useful. Knowing why is what tells you what to work on. Across 800+ students, the same eight causes kept repeating.. we call them the eight leaks. Not knowing the material is only one of them.
Sound like your teen?
The free assessment finds where your teen’s points are actually going.. before another month goes to the wrong fix.
Apply for a free assessmentAct III
The fix, and what happened to the pacing
We stopped working on Sam's pacing entirely. The work went at what was creating the extra work.
Narrower, not harder
Two targets. The step between understanding a question and building the right setup, and the small execution slips on material he already knew.
Most prep starts with addition.. more questions, more tests, more hours. For a capable student the points are often already there, leaking. Sam's work got narrower instead of harder.
And the pacing fixed itself. He was never slow.. he was redoing work that should have been done once. When he started setting questions up correctly the first time, he solved them and moved on.
Act IV
The result
Thirteen weeks after starting, Sam sat the real test.
1280 → 1520
Two hundred and forty points, one correctly-named problem.
The bigger lesson is why nobody caught it sooner. Everyone had a reasonable theory. Sam thought it was timing, his tutor agreed, his dad watched him run out of time on test after test. He really was running out of time.. they just hadn't found what was causing it.
So if a student has been studying for a while and the score isn't moving, the question isn't how to add more hours. It's why the points are still being lost.
Your teen’s version starts with the assessment.
The free assessment finds where your teen’s points are actually going.. before another month goes to the wrong fix.
Apply for a free assessmentThirteen weeks, one correctly-named problem.
See you on the call.. David, The 1500 Lab