# Activation Energy

URL: https://mechanisticmindset.com/wiki/activation-energy
Tags: core-framework, computational-lens

# Activation Energy

#core-framework #computational-lens

## What It Is

Before you can work on a project, you have to decide what to do, bring the relevant context to mind, and move away from whatever you were doing. Once the work is underway, those preparations are already in place. Starting therefore costs more than continuing.

**Activation energy** is the cost of initiating a behavior: the threshold an action must cross before it becomes self-sustaining. Starting work draws heavily on [willpower](/wiki/willpower); continuing draws on it very little. The difference is a requirement of the transition.

## The Mechanism

The required transition determines the cost. Checking a visible phone, following an established routine, and continuing the current activity each cost very little. These are low-activation behaviors.

Making a decision and actively resisting temptation take more. A single context switch takes little, but each one is paid for separately, so repeated switches add up. These sit in the middle of the range.

Starting work from rest is a larger threshold to cross, and so is initiating a difficult conversation. A cold start after dormancy can take more still. At a decision point, the behavior with the lowest cost is the one that most often runs.

## The 30x30 Pattern

Repetition reduces the starting cost, and the 30x30 pattern allows approximately 30 days for that change, in four stages. During days 1-7, execution is forced. During days 8-15, the cost falls. During days 16-30, the behavior approaches automaticity. From day 31 onward, it is meant to feel effortless.

This pattern is based on habit-formation research and observation in practice. The practice is 30 days of consistent execution, and its aim is a behavior that is cached and starts automatically.

## Why Starting Is Hardest

Starting requires three kinds of work. First, you load the context into [working memory](/wiki/working-memory): what am I doing, why, and what is the first step? Then you overcome inertia by moving from a low-energy `rest_state` to a high-energy `work_state`. If the behavior is not yet cached, you must also work out afresh how to carry it out.

Once you have started, the context is loaded, momentum is established, and the way through the task is already worked out. Continuing is now cheaper than stopping. This is **hysteresis**, or path dependence: the same task has a very different energy cost depending on the state from which you approach it.

## The Boltzmann Distribution

In statistical mechanics, a system is most often found in its low-energy configurations. The probability of occupying a state is proportional to `e^(-E/kT)`, where E is that state's energy.

Behavior can be pictured the same way: you tend to do what is easiest. People described as [disciplined](/wiki/discipline) have often arranged their environment so that desired behaviors require less energy than the alternatives. The environment changes which behavior the same person is most likely to perform.

### Example: Phone on Desk vs Drawer

```mermaid
graph TD
    subgraph "Phone on Desk (Bad Landscape)"
    A1[Work State] -->|Check phone: pick it up| B1[Phone State]
    A1 -->|Resist: inhibit it each time| A1
    B1 --> B1
    style B1 fill:#ff9999
    end

    subgraph "Phone in Drawer (Engineered Landscape)"
    A2[Work State] -->|Check phone: walk and unlock| B2[Phone State]
    A2 -->|Continue work: very little| A2
    style A2 fill:#99ff99
    end
```

A phone on the desk takes almost nothing to check: you pick it up. Resisting it takes active inhibition each time you see it. Checking is much the easier of the two, so checking is what tends to happen.

A phone in a locked drawer takes far more to check because you have to stand, walk over, unlock the drawer, and retrieve it. Continuing the work already underway takes very little. Continuing is now the easier of the two, so the work tends to continue. The person has not changed; the energy landscape has, and the behavior tends to follow the lower-cost transition.

A physical energy can be measured and added up; the cost of starting something can only be compared, one start against another.

## Bridge Scripts

A **bridge script** uses a sequence of smaller transitions to prepare for an expensive one. Moving directly from `rest_state` to `work_state` means paying the whole cost of the transition in one move. A morning sequence can distribute that work:

1. `rest_state` → `wake_state` happens automatically through the circadian rhythm.
2. `wake_state` → `alert_state` uses morning light.
3. `alert_state` → `ready_state` uses a 10-min braindump.
4. `ready_state` → `work_state` uses a pre-work checklist.

Each of these steps is a small one. The sequence distributes the cost across 30 minutes, which is easier than crossing the whole threshold at once. By the time you sit down, the bridge has already paid the activation cost. The aim is for work to be the lowest-energy option available from your prepared state.

## Detraining and Reactivation

A pattern that goes unused for months becomes harder to start, and the difficulty comes from the disuse. After a 3-month dormancy, the practice is to come back in steps: about 20% of the previous load in week 1, when the activation cost is high; about 40% in week 2, as the cost decreases; about 60% in week 3, approaching the earlier state; and 80% or more from week 4, with the aim of a fully reactivated pattern.

As with physical training, starting at 20% and building through consistent execution accommodates the loss of capacity. Expecting former performance on day 1 ignores the cost of reactivation. That high starting cost is expected, and the ramp is meant to bring it down.

## Reducing Activation Energy

### 1. Make It Concrete

“Work on project” leaves decisions to be made at the moment of starting. “Write 300 words of documentation for skills API” has already settled what to produce and how much. Removing that ambiguity reduces cognitive load at the decision point and lowers activation energy.

### 2. Install Triggers

A trigger settles when to act. It can be a time, as in “At 9 AM I work”; a location, as in “When I enter library I work”; or a preceding ritual, as in “After braindump I work.” Each removes one decision from the start of the task.

### 3. Remove Competing Options

An inaccessible phone cannot be checked by reflex. Blocking Netflix removes the option to watch it, and deleting delivery apps removes the option to order delivery. Prevention is done once, while active resistance has to be done again at every exposure. Removing the option avoids paying that resistance cost repeatedly.

### 4. Rehearse Until Cached

Behaviors become automatic through repetition, and a simple behavior takes fewer repetitions than a complex one. As the pattern caches, activation cost falls and execution takes less effort.

## Why "Just Start" Fails

“Just start” asks someone to pay the full activation cost without making it affordable. If starting requires more willpower than is available at that moment, the command asks for something the person cannot pay.

A bridge gives the person a way to prepare for that demand. The actionable instruction is to distribute the cost across a 30-minute warm-up sequence, so the transition does not have to be made all at once.

## Backward Chaining Reduces Activation Cost

[Backward chaining](/wiki/question-theory) starts with the desired outcome and works back through its prerequisites. Forward planning asks “What should I do?” from an unbounded current state. The options branch at every step with nothing to rule any of them out, which makes the search exponentially expensive and produces analysis paralysis. Backward planning asks what the specific goal requires, narrowing the search to relevant prerequisites.

For a work launch, the chain might be: work launched requires the sequence to have run; running the sequence requires the script to be loaded; loading the script requires the morning mantra and braindump; the braindump requires waking on time; and waking on time requires sleep by 10pm. Each step adds specificity. At “sleep by 10pm,” there is a concrete action with a clear path forward.

The goal filters out irrelevant paths, so you no longer have to figure out where to begin at the moment of action. Staring at an ambiguous project, you have to resolve the ambiguity before anything else can begin, and that is the expensive part. A predetermined, cached sequence costs little per step because each step already follows from the previous one.

## Related Concepts

- [Willpower](/wiki/willpower) is the resource spent on activation.
- [State Machines](/wiki/state-machines) describes the transitions whose cost activation energy determines.
- [Procrastination](/wiki/procrastination) often follows when energy is insufficient to cross the starting threshold.
- [Discipline](/wiki/discipline) describes what low activation costs look like from outside.
- [The Braindump](/wiki/the-braindump) can serve as a bridge into work.
- [Prevention Architecture](/wiki/prevention-architecture) removes undesired behaviors from the available choices.
- [30x30 Pattern](/wiki/30x30-pattern) describes a month of daily repetition and how the starting cost is expected to change across it.
- [Question Theory](/wiki/question-theory) develops backward chaining from goals.
- [Pedagogical Magnification](/wiki/pedagogical-magnification) explains specificity as matching resolution to reduce ambiguity.
- [Ignition](/wiki/ignition) covers warm-up protocols, identity loading, and the distinction between ignition and selection pressure.
- [Container Design](/wiki/container-design) creates bounded contexts in which starting is cheap and stopping is expensive.

## Key Principle

Bridge scripts, triggers, and concrete instructions lower the cost of starting a desired behavior. Prevention architecture raises the cost of the competing behavior. These changes aim to make the available energy sufficient for the action you want to take.
