Speed versus accuracy — the trade-off no one mentions

The standard framing of speed-versus-accuracy in Sudoku — and in most cognitive activities — is that going faster increases your error rate. Push the pace, lose precision; slow down, recover precision. This is true and uninteresting. It's also not the most expensive trade you make when you solve fast.

The more expensive trade is the one that doesn't show up as an error. Going fast doesn't only make you more likely to misplace a digit. It makes you systematically less likely to notice the better move that was available — the one a slower solver, on the same grid, would have spotted twenty seconds later. The fast solver places the first move they see, the slower solver places the third move they see, and the third move is sometimes the one that unlocks the next ten cells where the first move would have unlocked one. We don't usually count this as an error. It looks, from the outside, like you solved the puzzle. From the inside, it's a measurably worse solve disguised as a successful one.

This piece is the longer version of that distinction.

What speed pulls you toward

Solving fast is, mechanically, a process of optimising for placement rate. The brain wants to fill cells. It gets a small reward each time it does. Under time pressure, the optimisation pushes you toward the first valid move you can identify, because committing to a move means another reward; pausing to look for a better move means deferring it.

The first valid move is usually the one that's perceptually loudest. A cell with one obvious candidate. A row where eight of the nine digits are placed and the ninth is unambiguous. A naked single in plain sight. These are the moves that surface in the first few seconds of looking, and they're the ones the speed-optimisation reaches for.

The problem is that the perceptually-loudest move isn't always the most useful move. In hard and expert puzzles especially, there are often several legal moves available at any given moment, and they're not all worth the same amount. One might solve the cell directly in front of you. Another might force a chain of three or four placements once made. The speed-optimised brain takes the first one, because finishing-the-cell is the reward function it's running. The slower brain notices the second is more useful and takes that one instead.

Across a full puzzle, the difference compounds. A solver picking cells in the perceptually-loudest order will finish a hard Sudoku in (say) eighteen minutes, with most of the difficulty concentrated in the back half where the easy moves have run out. A solver picking cells in the most-useful order finishes the same puzzle in twelve, because the back half never accumulates the same level of stuckness. The slower-thinking solver is faster overall, even though they're slower per move.

What accuracy pulls you toward

The same dynamic, in reverse. A solver who optimises for accuracy slows their placement rate to a level where the first move they make is almost certainly correct and almost certainly useful. The cost is the time spent considering. The benefit is that fewer of those considerations need redoing later — fewer placements have to be undone, fewer chains have to be retraced from scratch because of an early cascading error.

There's also a subtle perceptual benefit. The accuracy-optimised brain, by lingering on a cell longer, gives the eye a chance to pick up patterns that the speed-optimised brain would have skipped past. The scanning shift from cell-first to unit-first is a classic example — a fast scan stays at the cell level, a slower scan picks up the unit-level patterns that surface harder moves. The slow-and-careful solver doesn't only place fewer wrong digits; they actively see more of the puzzle because they're giving themselves the time for the seeing to happen.

Where the true cost of speed shows up

The cost of going fast on a hard puzzle isn't usually a misplaced digit. It's a stalled position around minute fifteen of a twenty-minute solve, where the easy moves have all been taken and the harder moves have to be excavated by hand because the perceptual habits weren't engaged earlier. We've written separately on the half-finished-grid problem — the stuck-at-60% pattern that fast solvers run into more often than they expect.

A useful diagnostic: if you regularly hit a wall in the back half of hard puzzles, where your placement rate drops to nearly zero and you can't find the next move, the wall isn't a failure of skill. It's an artefact of the front half. The early placements were fast, optimal-looking, and not particularly useful; they didn't set up the back half the way slower placements would have. Diagnosing this is the first step out of it. Slowing down on the front half — even if it feels like wasted time — is what fixes the back half.

The honest framing

The trade-off isn't binary. Pure speed and pure accuracy are theoretical end-points; real solvers settle somewhere on the spectrum, and the right place on the spectrum depends on the tier and the goal.

For easy and medium puzzles, pure speed is fine — there are few enough moves that the perceptual-loudness order and the most-useful order are basically the same. For hard and expert puzzles, the gap between the two orders opens up, and the cost of staying at the speed end of the spectrum becomes real. We covered the wider stopwatch question in the stopwatch problem; the trade-off this piece names is the part of the question that doesn't show up in the timer's reading at the end.

The slower solver's secret isn't that they're slower at the moves. It's that the moves they pick are doing more work per move. Once you notice that pattern in your own solves, the case for not racing through the front half of a hard puzzle becomes much clearer. The minutes you don't spend rushing in the first ten cells are the minutes you don't have to spend later, stuck at sixty percent, looking at a grid where every easy move is gone and the harder ones haven't been set up.