Procrastination

What People Think It Means

You meant to work, but an hour later you are still on your phone. Calling this laziness tells you that you have failed to do what you intended. It does not explain what prevented you from starting.

The usual judgment goes further: someone who procrastinates must not care enough, must have bad priorities, or must be choosing to sabotage themselves. These are judgments about character. They offer no way to distinguish a task you cannot define from a task you find aversive, even though the two problems need different responses.

The branches are possible places to investigate, not a claim that every delayed task has the same cause.

Read this diagram

Inspect the failed start branches into Is the task concrete?; Is there a cue?; What competes with it?; What resources are available?.

What It Actually Is

Procrastination occurs when work_launch_script fails to load and default_script runs instead. These names distinguish the sequence that would get work underway from the sequence that takes over when it does not.

The state machine is executing its existing instructions. An intention to work has not supplied the conditions needed to enter the work state, so the available default continues.

Why work_launch_script Fails to Load

There are several places where the launch can fail:

1. The task has ambiguous success criteria. "Work on project" does not identify a concrete next action or a way to tell when it is finished. Before beginning, you still have to decide what the task is.
2. No trigger condition exists. "I should work" expresses an intention without specifying when or how the work begins.
3. The environment contains conspicuous competing stimuli. A visible phone, an open YouTube tab or a nearby bed supplies a definite option. In the account of salience, a distinguishable stimulus wins attention over a vague goal. "Work on project" has no clear edges; the phone does.
4. The task is genuinely aversive. Avoidance can carry information. The task itself may be wrong, rather than merely hard to start.
5. Available energy is below the launch threshold. If a morning launch costs 4–6 willpower units and you wake with 3, the intention to work does not cover the difference.

What Runs Instead

When work_launch_script == null, default_script runs. A lounge_script might involve the phone, YouTube and lying around. A distraction_script might involve compulsive task switching, repeated email checks or "research" that never produces anything.

These sequences have near-zero activation costs and provide immediate dopamine hits, so they run automatically. "Just start" does not explain how to replace them. It repeats the request to execute a program without explaining how that program will be loaded.

How to Build It

A useful diagnosis identifies the point where starting breaks down. The interventions below change different parts of that sequence.

1. Make the Task Concrete

"Write 300 words of documentation for the skills API" specifies what "work on idyllic" leaves undecided. You know what you are producing and how much counts as completing this step. Resolving that ambiguity before the decision point reduces the cognitive work required to begin.

2. Install a Trigger Condition

A trigger specifies the event that starts work. It can be time-based ("At 9am I work"), location-based ("When I enter the library I work"), or ritual-based ("After 10-minute braindump I work").

The condition has to be unambiguous and automatic: when condition X occurs, work_launch_script runs. Otherwise the trigger leaves you with another decision about whether now is the right time.

3. Remove Competing Stimuli During Launch Window

Putting the phone in a drawer, closing every browser tab except the 3 needed for work, and using a room that contains only the work setup change the choices available during launch. Making distractions inaccessible removes the need to resist them at the same moment you are trying to begin.

4. Build a Bridge Script

A cold start is expensive because it asks for the whole transition from default_state → work_state at once. A bridge script supplies intermediate steps so that the transition does not require one large burst of willpower.

One example has four steps:

1. A morning mantra takes 15 minutes.
2. A 10-minute braindump makes the upcoming work explicit.
3. A pre-work checklist turns the phone off, sets the timer and starts OBS streaming.
4. Work follows automatically.

Once the bridge sequence is complete, you are in the work state and continuing costs less than stopping. The activation-energy spike occurs while crossing the threshold; afterward, inertia carries the work forward.

The Bottom Line

Under this account, a failed launch calls for a repaired launch sequence. Asking for more motivation or discipline leaves the task, trigger and competing options in the same condition.

Related Concepts

• Salience explains why a conspicuous distraction wins attention over an indistinct goal.
• Willpower concerns the energy available to cross the starting threshold.
• Discipline describes what automatic launch sequences look like from the outside.
• Laziness is often confused with procrastination but names a different mechanism.
• Activation Energy explains why starting is the expensive part.
• State Machines describes how the available sequences run.
• Focus concerns what happens after a successful launch.
• Moralizing vs Mechanistic explains why a character judgment cannot diagnose a launch failure.

Key Principle

An execution condition connects an intention to an event: when the condition occurs, the work begins. "I should work" contains no such connection.