Accuracy Before Speed

A familiar process already sits near the fastest pace the quality bar still allows. Real speed arrives from changing the process and running the current one at a quality-surviving pace. An efficient technique run accurately produces that pace as a by-product.

The arithmetic of one error

The competing picture treats a person like a factory line or a car: press the pedal and more product comes out. That is what makes leftover minutes look like unused capacity. Work that fails the quality bar is not finished work. Pages turned that later have to be done again add nothing.

Familiar work already sits at roughly 80–90% of the fastest pace that still survives that bar. That band is a practitioner estimate, not a measured constant. There is usually an internal sense of where mistakes start to climb, noisy as that sense is. The unused band is maybe 5–10%. Taking it makes more mistakes.

Repair, in this system’s teaching picture, runs near four times the time of doing the step right once. That 4x is a heuristic the speaker who taught it disclaimed as research, not a laboratory result. The four costs are catch the error, restore context, do the step again, and unpick whatever was stacked on top. Errors cascade. Treat 1+1 as 3 and the next line becomes 1+1+2=5.

Foundation errors hide longest — weeks or months — then show up everywhere and refuse a clean trace. After a rush the person often feels more sure, not less: the knowledge that would catch the failure is the knowledge that was never built. There is no last-save. Later material sits on the error, so diagnosis stops being which of four to six clean mistakes and becomes which of a dozen to thirty interacting ones. Rebuild costs more than first-pass care and is more confusing, which is why people walk away from it. A mid-arc repair can eat a season that a careful fortnight at the start would have spared.

In this arithmetic, add a tenth of speed and a tenth of errors and the bill is about four tenths extra overall. To break even the rush would have to be four times the leftover that exists. A rush with zero errors still only returns that leftover band, and it is rarely worth the exposure. A stretch of rushing tends to finish with the same finished work as a stretch at a pace that can be held, and with more tiredness that then makes more mistakes.

Where real speed comes from

Switching to a fundamentally better technique can be worth several times — a gain no amount of hurrying the old one reaches. The comparison only holds at a comfortable pace: same process, calm against rushed. Done correctly, the efficient process throws off fewer errors to review, so its built-in advantage pays out in full. The gain only disappears if the pace is slowed on purpose.

Hands get faster once the method is known. Speed that arrives without being forced is the mark that the method has settled, the readiness mark in Rapid Skill Acquisition. Careful work can feel slow in the sitting. Fewer pages, more held. The fast-shallow path pays those hours back later as relearning and re-testing. Time efficiency is judged across the whole arc of mastery, not the single sitting.

Elapsed time is not practice time. Two months in which the method was not actually run is the same as no time having passed. Two weeks of heavy, accurate practice can be enough to move on. The unit is what was practised, plus an honest check that the work now runs correctly without strain — not how long the topic has been on the calendar. Pacing Skill Development owns the same load logic for how many processes to run at once.

A new technique is practised for accuracy alone, and pace is left to arrive once the motions are right. Forcing speed while the method is still wrong bakes the mistakes into the habit. Relearning a mislearned skill then runs much slower — around three times, with the same heuristic status as the 4x — each move watched for the old version firing.

The split, at full magnification

An efficient process, rushed, loses to the same process run calmly. That is the whole page at the scale of one session: leftover minutes on the current method barely exist, and claiming them raises the error rate the quality bar was there to stop. The lever with range is a better process at a quality-surviving pace. Marginal Gains is that lever as a practice — one named change to the method, not a harder push on the old one.

The hustle trap

Trying hard all the time crowds out the pause that would aim the work. Consumed by the push, there is no mental space left to notice whether the method still aims at the goal. The picture is a fly beating against glass while the sash sits open a hand away. All the effort, none of the room.

Work that actually aims at the goal seldom has to feel like a grind. Productive is whatever moves the goal. A rest, a walk, an hour with people is the productive move when focus or mood is what is binding. The same hour flips as state flips. Priorities get recalibrated weekly — on rough days, daily.

A level that can only be held by grinding is a verdict on the method. Absorb the short hit and build the method that holds the level without the grind. Priority 0+1 System is the companion: ranking work only pays when each unit of work is done right.

Agents, and what is actually known

Accepting agent work without checking buys minutes today and pays the fourfold repair when the fault appears later in the chain. This is the cleaner 4x: later commits sit on the bad one, so the cascade is steeper. Throughput lives in the harness — the prompts, checks, and reusable patterns around the agent — not in running more jobs. Watching more jobs per day is hustle in a new shirt. It spends the exact hours that improving the prompts and checks would have used.

The two mistakes are not equal. Going too slow takes work. Going too fast happens on its own. If it is unclear, stay on the current level another week or two — and actually practise it. Sitting on a calendar without running the method is not holding the level.

What is actually known, and what is not: the speed–accuracy tradeoff says faster work produces more errors. That direction holds. Late-found defects cost more than early ones, and schedule pressure raises defect count. Those are different 4xes from “one study error costs four times the time of doing it right.” The study-repair 4x remains this system’s teaching number. The 80–90 / 5–10 / several-times figures are the same family. The checkable expectation is the unforced speed-up arriving, or a first rush that already produced work that had to be done again.

Leftover ambition goes into the process, or into the harness, not into pushing the old one. The fly has a name now. The open sash is a better method at a calm pace.

Links

• Priority 0+1 System — ranking work only pays when each unit of work is done right.
• Rapid Skill Acquisition — unforced speed as the mark that a method has settled.
• Pacing Skill Development — same load logic for how many processes to run at once; elapsed time is not the unit.
• Marginal Gains — process change as the one speed lever with range.

Open Questions

When is a 5–10% rush actually worth the exposure?

How is habituation-speed told from rushed-speed from inside the session?

Sources

• Fitts 1954 — speed–accuracy tradeoff: faster responses produce more errors. Support for the direction of C8, not for a study-repair multiplier.
• Wickens, Engineering Psychology and Human Performance; Pachella 1974 — same SAT family. Bound: the finding is error rate under speed, not repair-time arithmetic.
• McConnell, “Software Quality at Top Speed” — excessive schedule pressure associated with up to 4× defects. Different claim: defect count, not time-to-repair a learning error.
• IBM Systems Sciences Institute (widely cited); Boehm defect-cost curve; Labovitz & Chang 1992 — late defects cost more than early ones (design-to-release ~4–5×; earlier phases up to 100×). Different 4x: phase of discovery. Fits agent-output better than study errors.
• Newell & Rosenbloom 1981, power law of practice; Fitts & Posner 1967, autonomous stage — hands get faster once the method is known. Support for unforced speed as a habituation mark.
• Bouton 2004 — extinction is not unlearning. Support for early-automated errors being expensive to reverse.