Watching Others Do It Procrastination

A simple explanation

You meant to write today. Instead you watched three hours of someone else writing — a livestream of a novelist drafting, a YouTube essay on a screenwriter's day, a documentary about a poet. The hours felt productive. You learned things. By the end you were tired in a particular way, and you had not written.

This is the loop. The body sat through hours of the felt-shape of doing the thing, conducted by someone else's hands. The Reward System registered arrival without you having traversed the difficulty. The Meaning System registered direction without you having tested it against your friction. Effort was paid in attention. Deposit, at the level of skill or artefact, was near-zero. Residue accumulated as a borrowed sense of having already done it, which made the next session of actually doing it harder to start.

An everyday example

You want to learn to cook. On a Sunday you open YouTube. You watch a forty-minute video on knife technique, a profile of a chef you admire, a livestream of someone making a curry. You take mental notes. You order takeout the next three nights.

On the fourth night you stand in the kitchen with an onion and a knife and the felt sense that you already know how to do this — but your hand does not. The gap between watched-knowing and hand-knowing is wider than it felt on Sunday. There is a small disappointment that is not about the onion. It is about discovering that Sunday's hours did not deposit what they seemed to. The takeout that follows is not convenience — it is the loop closing again, the watched competence preferred over the unwatched fumbling.

Why does watching tutorials feel like I'm making progress?

Because progress has a felt shape, and the felt shape can be borrowed. When you watch someone solve a problem you have not solved, your nervous system tracks their solving — the orientation, the small recoveries, the moment the piece clicks. You experience these as if from inside, because human cognition is built for vicarious learning: we evolved to learn by watching kin, and our reward systems make watching-the-doing intrinsically satisfying.

The mismatch is that watching evolved as a prelude to attempted doing, within hours or days. Modern viewing severs that link. The prelude becomes the whole loop. The Reward System, which cannot distinguish prelude from completion, logs arrival anyway. The hour produces real learning. The dishonesty is in letting the learning stand in for the practice it was meant to inform.

The behavioral loop

A long loop with a long after-tail:

1. Trigger — the desire to do the thing surfaces, often alongside the felt edge of where the difficulty would begin.
2. Threat flicker — the Threat System registers the difficulty as cost; the urge to delay opens.
3. Substitute offered — a related video, stream, or repo is one tap away. The substitute is related to the original ask, which is what makes it a substitute and not pure distraction.
4. Vicarious arrival — the Reward System receives the satisfying moments of the doer's work: the click, the breakthrough, the finished artefact. The Meaning System receives the direction: this is the kind of person I am, or could be.
5. Borrowed-completion signal — the watcher logs a felt sense of having done something in the domain. The urge to begin one's own work softens.
6. Re-entry — when the watcher next tries to start, friction reads larger than expected, because the borrowed-completion signal raised the relative cost.
7. Loop compounds — the next session begins inside this residue. Watching is now more attractive than starting, by a slightly larger margin than the day before.

Emotional drivers

Three feelings, layered and rarely separated:

• Genuine interest — the watched material is in the direction of who the watcher wants to be. The interest is real, and is what makes the substitute close enough to mimic.
• Vicarious arrival — the felt-shape of finishing, claimed through identification. The loud, immediate driver, even though rarely named.
• A low-grade dread of one's own friction — the watcher's own version is less polished, less fluent, less fast. Watching defers contact with the gap.

The third driver is the engine. Substitution is most powerful when the substitute is also a refuge from the original's friction.

What your nervous system does

Two systems run during watching: the mirroring system that tracks the doer's actions as if from inside, and the agency system that would be active if you were doing the work. Mirroring fires; agency stays quiet. The reward signal arrives without the proprioceptive cost.

This produces a specific fatigue — attentional depletion without the felt deposit of having moved through difficulty. The body reads tired but not used. Over longer arcs, the agency system loses tone — starting one's own work begins to feel disproportionately harder, because the system that initiates it has been under-recruited.

The DojoWell interpretation

This loop is a clean case of substitution mimicry where the substitute is unusually close to the original. Watching a coder code and coding yourself share substantial outer shape: same screen, same vocabulary, same scenes of struggle and click. The Reward System, reading shape, fires the satiation signal. The Meaning System, reading direction, also fires. Both Systems are doing their job. The mechanism that fails is the one MDT was built to catch: outer shape arrives, effort runs, deposit does not land. The deposit, here, is practice tone — the body's accumulated familiarity with one's own version of the difficulty. It cannot be borrowed. It only accumulates through one's own friction.

Reading the equation: deposit near-zero; residue large (the borrowed-completion signal that suppresses initiation, plus self-trust erosion); effort moderate-to-high (hours of attention, often at the time reserved for one's own work). Density: low. Closure: borrowed. The signature is borrowed_completion because the loop closes — but the closure was someone else's. Pure distraction breaks against an honest end-of-day reading; borrowed completion does not, because the watcher did engage with the domain.

How do I stop binge-watching coding streams and actually code?

The work is not to swear off watching. Watching has a real role: orientation, technique exposure, motivation. The work is to restore the link between watching and doing — to make watching a prelude again, not a destination.

The most reliable interruption is structural: shorten the watching window and place a small doing-block immediately after, before the borrowed-completion signal can do its dampening work. Five honest minutes of one's own friction, within an hour of watching, is denser than the five hours of perfect tutorial that preceded it. The second move is to notice the dampening signal. I already kind of did this today, after a session in which you did not in fact do it, is the substitute speaking. It is not a lie; it is a misread. The slow signal speaks later.

Practical steps

1. Set a watch-then-do contract before opening the material. Even a small commitment — I will write three sentences after this video — keeps the watching a prelude. An unstated contract barely binds.
2. Watch shorter, do sooner. A ten-minute clip followed by fifteen minutes of one's own work deposits more than a two-hour stream followed by nothing.
3. Notice the borrowed-completion signal. I already kind of did this today is the signature speaking. Treat it as data, not verdict — the slow system has not voted yet.
4. Protect the time-of-day reserved for your own work. Watching is most damaging when it occupies the hour earmarked for practice, because it borrows the satisfaction the practice would have produced.

Reflection questions

• Pick a domain where you have watched hours and done little. What was the felt-shape the watching delivered? What is the gap between that and your own first attempt?
• When does the urge to watch arrive in relation to the urge to do? Before? Instead of? After?
• Is there a watched figure whose work you have used as a borrowed identity in place of practice in their domain?

Frequently Asked Questions