The stopwatch problem

There's a small but real subculture of competitive Sudoku — the World Sudoku Championship, online speed-solving leaderboards, communities of solvers who can finish a hard 9×9 in under three minutes. The competition is real; the people are talented; the puzzles get solved fast. None of which is the same question as whether you should be timing yourself.

This piece is about the stopwatch — what it does to a puzzle, when it helps, and the honest case for solving without it most of the time.

What the stopwatch does

A stopwatch reframes the puzzle. The activity changes from "find the moves" to "find the moves quickly," and the difference is bigger than the word quickly makes it sound.

In timed mode, the brain optimises for placement rate rather than placement quality. It picks the first move it sees rather than the best one. It pencil-marks reflexively even when restraint would surface patterns faster. It races past the thirty-second warm-up that would have produced two early placements at zero time cost. All of these are subtle, none of them is a conscious choice, and the cumulative effect is that timed solves and untimed solves are different activities even when the grid is identical.

The reframing isn't always bad. For solvers who already know the techniques cold and want to push their pattern recognition into reflex territory, the stopwatch is the exact right tool. Speed-solving sharpens the lookups — the way a digit reads on a partially-marked grid, the way a pointing pair jumps out from a cluster, the rhythmic cadence of place-then-update. These are real skills, and they get sharper under time pressure in a way they don't in untimed practice.

When timing helps

Three specific cases where the stopwatch earns its keep.

You've internalised the techniques and want pattern-recognition speed. Solvers who can finish hard puzzles cleanly in twenty-five minutes can usually drop that to fifteen with a few weeks of timed practice — the bottleneck at that level is recognition rather than reasoning, and recognition responds to time pressure. If you're at this stage and want to compete or just solve faster for its own sake, the stopwatch is the lever.

You're doing maintenance practice on already-mastered material. Easy and medium puzzles, for an experienced solver, are practising fluency rather than learning. Timing them turns them into something more like an exercise — the speed itself becomes the point of the activity, and the puzzle is the medium. This is a perfectly valid use of Sudoku, and one a lot of longtime solvers settle into for some portion of their solving.

You're entering competitions. The World Sudoku Championship and most online competitive scenes are timed. If you're competing, untimed practice doesn't prepare you for the actual conditions. Time the practice, time the solve.

When timing hurts

Three cases where the stopwatch does more harm than good.

You're learning a new technique. New techniques live in the head before they live in the eye, and the head needs slow, deliberate attention to convert them into perceptual habits. Timing yourself while learning a technique trains the brain to skip the careful step that would have made the technique automatic — you place fast, you find moves through your existing toolkit, and the new technique stays abstract for an extra few weeks. We covered this at length in the puzzle that taught me the X-wing. The lesson generalises: untimed solving is the right mode for techniques you don't fully have yet.

You're using the puzzle as a quiet ritual. A daily morning Sudoku is, for most people, valued for the quiet space it creates more than for the speed of the solve. Adding a stopwatch to that ritual changes the experience — the quiet attention turns into a performance, the satisfaction shifts from "I finished" to "I finished in X minutes," and the comparison-to-yesterday becomes part of the activity. For a lot of solvers, this is exactly the wrong direction for what they wanted from the habit.

You're solving hard or expert puzzles. Hard Sudoku rewards slowness. The deduction work happens at a pace the timer can't usefully accelerate, and timing yourself on a hard puzzle mostly produces frustration when the inevitable stuck moments push you past a perceived target. Most experienced hard-puzzle solvers don't time their solves. The right pace is the pace at which you don't make mistakes, and that pace varies by puzzle.

The compromise that works

A useful pattern for solvers who want some timing but not all timing: time the easy and medium puzzles, untime the hard ones. The easy and medium times track real fluency improvements over weeks and months, which is satisfying in a quantifiable way; the hard puzzles get the slow patient attention they reward. The two modes don't compete; they handle different parts of the practice.

The other useful pattern, especially for daily-puzzle ritualists, is to time after the fact rather than during. Note the start time and the finish time, do the puzzle without watching the clock, calculate the duration when you're done. The information is preserved without the pressure being applied during the solve.

The honest version is that most solvers don't need a stopwatch most days. The puzzle is good company at any pace, and the pace it asks for is rarely the pace a stopwatch would impose. Speed solving is a real and valid form of Sudoku; it isn't the only form, and it isn't the one most readers of this piece are probably looking for. The stopwatch is for when you want it. The puzzle is for the rest of the time.