What Drift Costs

4 minute read

You sit down to return to a goal and wonder where the last hour went. You opened the thing. You meant to work. Somehow you spent the first stretch just remembering what the thing is. It feels like you are already behind before you begin. That sensation has a source. Drift creates specific, repeatable taxes that you pay on the way back in.

Hidden overhead

When a goal falls out of view, the next visit carries hidden overhead. You pay in a time tax to get re-oriented. You pay in context reload to reconstruct your map. You pay in decision fatigue because choices feel heavier after a gap. You pay in identity friction because the promise to yourself feels less certain. And you pay in opportunity cost because time went somewhere else while the goal sat cold. These are not moral debts. They are ordinary costs of reactivation.

Start with the time tax. Returning requires setup. You have to find the file, open the right tools, scan prior notes, and remind yourself where the edges are. The first block is not progress so much as clearing the runway. When the gap is small, the runway is short. When the gap is long, you taxi for a while before takeoff.

Then comes context reload. Context is that thin, lived sense of where you were headed and why. It includes half-decisions, patterns you were using, and open questions you were holding. Distance evaporates that. So you re-read. You chase breadcrumbs you left for yourself. The brain can reconstruct, but it charges for the rebuild.

When decisions get heavier

Decision fatigue often arrives next. Choices that felt light inside momentum now feel consequential. Do you change direction or finish the draft you are lukewarm about? Do you refactor first or ship something imperfect? The gap heightens the stakes. Heavier decisions burn more energy, and avoidance tempts you to delay until you can do it right.

Identity friction is quieter but real. The story that you are someone who keeps this promise loses volume during drift. When you whisper a new promise, it can land a little softer in your own ears. That means the next start requires not only action but a small act of re-belief.

A concrete example

Picture reopening a codebase or a long writing draft after two weeks away. The first thirty minutes are setup: installing updates, running tests, scanning TODOs, reminding yourself which branch held the experiment. Then you reload context: you trace the last change, re-read a function to remember why the awkward part was necessary, skim the outline to hear the structure again. Decisions feel heavy: do you refactor now or later, keep the subplot or cut it? Identity friction hums: you wonder if you are still the person who writes this kind of thing.

Notice how a small thread would have reduced each cost. If you had left a one-sentence note to future-you, the time tax and decision fatigue would both shrink. If you had glanced at the draft once midweek and typed a line you believed, context would reload faster. If you had touched the project lightly enough to remember you still care, identity friction would soften.

A caveat

Not every cost is a problem to be eliminated. Rest can be an investment. Incubation can yield better answers than forcing progress. Some goals need a cooling period. The point is not to police pauses or worship unbroken streaks. The point is to see the tradeoffs clearly so you can choose pauses on purpose and protect the thread when you intend to come back soon.

Relationship to return

When you keep even a toe in the water, each cost category shrinks. The time tax goes down because setup is familiar. Context reload is faster because you left yourself a live thread. Decision fatigue drops because you pre-named the next honest move. Identity friction eases because the promise never fully left the room.

The greatest cost of drift is often invisible until the moment you try to return.

This is why drift and Decision Fatigue often meet at the same threshold: the return feels heavier before the work even begins.

Continue the Guide

Continue with Small Gaps Become Big Gaps.

Guide

The Cost Of Drift

  1. 1. CostPrevious
  2. 2. CostsCurrent
  3. 3. GapsNext
  4. 4. Return EarlyLater
  5. 5. ConnectionLater

Place this question in context

Return to the full Guide to see what comes before and after this question.