Precrastination: Why Your Brain Rushes to Finish Things Too Soon

You get an email that needs five real minutes of thought — check a date, confirm a number, phrase two sentences carefully. You have the whole afternoon for it. And yet your thumb is already moving toward reply before you've finished reading the second line, because some quiet part of you would rather have this done and off the list than have it done well. Ten minutes later you notice the date was wrong.

That instinct has a name now, and it isn't laziness, or its opposite. It's called precrastination, and it may be shaping more of your day than procrastination ever did.

The Bucket Study That Gave This Instinct a Name

In 2014, psychologist David Rosenbaum and colleagues ran an experiment that looked almost too simple to matter. Participants walked down an alley lined with two buckets: one close to where they started, one much closer to the finish line. The instructions were plain — pick up either bucket, carry it to the end. The economical choice was obvious: walk empty-handed toward the far bucket, pick it up near the finish, and carry it only a short distance. Almost nobody did that. Most people grabbed the near bucket immediately and hauled it the entire length of the alley, taking on more time, more distance, and more physical strain than the task required.

Rosenbaum's explanation wasn't that people are bad at arithmetic. It was that holding an unstarted subgoal in mind — "I still have to go pick up a bucket" — carries its own cost, even when the eventual physical effort of picking it up is trivial. Once the bucket is in hand, the mental tab closes. The relief of no longer having to track an open task outweighed the extra weight and distance people were willing to carry it. He called the behavior precrastination: the rush to complete a subgoal as early as possible, even at a real cost, in order to lighten the mental load of keeping it open.

It's the mirror image of procrastination in the most literal sense. Procrastination delays a task despite the cost of delay. Precrastination completes a task early despite the cost of completing it early. Both are driven by the same discomfort — an open loop, sitting there, asking to be resolved — they just resolve it in opposite directions.

Precrastination Beyond the Lab

Nobody is carrying literal buckets most days, but the pattern shows up constantly once you know what to look for.

It's the email answered in a hurry, before you've actually thought through what you want to say, because an unread message sitting in the inbox generates a small, steady itch that a rushed reply relieves immediately. It's the task moved from "later today" to "done" the moment you have five free minutes, regardless of whether those five minutes were the right five minutes to spend on it. It's grocery shopping for the whole week on Monday because holding "I still need to plan meals" open in your head for six more days feels worse than the cost of guessing wrong about what you'll actually want to eat on Thursday.

I see a version of it in code review. A pull request comes in with a comment attached, and the instinct is to resolve it — approve, request changes, something — right now, this minute, so the item drops out of the queue in your head. Sometimes that instinct is correct. Often the better move is to actually go read the diff carefully first, which takes longer and leaves the item open a while longer, and that open-ness is exactly what the instinct is trying to avoid.

Errands cluster the same way. You'll drive fifteen minutes out of your way to handle a return today rather than folding it into a trip you were already taking tomorrow, because "I have a return to make" sitting unresolved on a mental list costs something, even if the return itself doesn't need to happen today at all.

Why Finishing Feels Like Relief, Even When It Shouldn't

There's a well-documented cousin of this effect called the Zeigarnik effect — the finding that unfinished tasks tend to intrude on memory and attention more than finished ones. An open task keeps a small process running in the background, the way a browser tab you meant to read later keeps drawing your eye back to the tab bar. Precrastination is what happens when you'd rather pay a real cost now than keep tolerating that background hum.

Working memory is limited, and holding a subgoal open — "I still need to do X" — occupies a slot in it whether or not X is urgent. Closing that slot produces a real, measurable sense of relief, separate from whether closing it was the right call. That's the trap: the relief is genuine and immediate, while the cost of having closed it too early — the wrong grocery guess, the reply that needed a correction, the pull request approved before it was actually read — usually shows up later, disconnected from the moment that caused it. Nothing in the moment of hitting send tells you that you just traded a small, real cost for the relief of an empty mental slot.

When Getting It Done Early Helps, and When It Just Feels Like It Helps

Not all early completion is precrastination in the costly sense Rosenbaum described. Packing the diaper bag the night before, instead of assembling it in a rush at the door, is frontloading a task at a moment when you have slack to do it carefully — that's a genuine win, not a trap. The difference isn't when you do something; it's whether doing it early cost you information, flexibility, or quality that waiting would have preserved.

Useful frontloading has a specific shape: you do the work when you have the capacity to do it well, and nothing meaningful changes between now and the deadline that would have improved the outcome. Premature closure has the opposite shape: something relevant is still unresolved — a number that hasn't been confirmed, a decision someone else hasn't made yet, information that will arrive later — and you closed the task anyway because the open state was uncomfortable, not because the work was actually ready to be finished.

A useful test: if you'd make the exact same choice with unlimited patience and zero discomfort about the task being unresolved, it's probably frontloading. If waiting would let you make a better choice and you finished anyway, that's precrastination costing you something real.

A Three-Scenario Test for Catching Yourself in the Act

Try these against your own week:

Scenario one — the reply. You get a message that deserves a considered answer, and you have hours before it's actually due. Do you draft a fast reply within minutes to clear the notification, or do you let it sit until you've actually thought it through? If you notice yourself sending before you've finished thinking, that's the tell.

Scenario two — the errand. You have a task that could be folded into something you're already doing tomorrow, but doing it today, alone, would cost you extra time or a special trip. Do you go today anyway, purely to get it off the list? If the only reason for today is that today feels lighter than carrying the thought of it for one more day, that's precrastination.

Scenario three — the decision. You're waiting on one more piece of information that would meaningfully change your choice, and it's arriving soon. Do you decide now anyway, because sitting with an open decision is uncomfortable, or do you wait the extra day the information is worth? Deciding before the input that would change your mind has arrived is the clearest version of the bucket-carrying instinct at work.

None of these are moral failures. They're the same wiring that makes an open tab pull at your attention, applied to slightly bigger stakes.

Common Questions

Is precrastination the same thing as being a "completer-finisher" personality type? Not quite. A general preference for finishing things is a broad trait; precrastination specifically describes choosing to finish a subgoal early even when doing so costs more time, effort, or accuracy than waiting would have. You can be someone who finishes things reliably and still notice this pattern showing up in specific moments.

Is precrastination ever the right call under time pressure? Often, yes — under real time pressure, the cost of holding an open task in mind can genuinely outweigh the cost of a slightly rushed answer. The pattern becomes a problem specifically when there's no real time pressure and the rush is driven only by discomfort with the task being unresolved.

Why does the itch to finish feel so strong even for small tasks? Working memory doesn't scale its discomfort to a task's actual importance. A trivial open loop can feel just as insistent as an important one, which is part of why precrastination shows up as often on errands and emails as it does on anything higher-stakes.

Does slowing down always produce a better outcome? No — sometimes the extra information you're waiting for never arrives, or arrives too late to matter, and an early decision would have been fine. The three-scenario test is meant to catch cases where waiting would clearly help, not to argue for stalling on everything.

How do I actually stop myself in the moment? Naming the discomfort as it happens helps more than willpower does. Noticing "I want this done because it's open, not because now is the right time" turns an automatic reflex into a choice you can actually evaluate.

The bucket study never got much attention outside psychology, maybe because carrying a bucket a little too far isn't dramatic enough to be a warning. But most of us are carrying some version of that bucket most days — closing a loop early because open feels worse than heavy — and the cost rarely shows up until well after we've set it down.