Routine simplification

Two runners, one habit

Marcus and Priya both decided to start running in January. Marcus, a former college athlete, built a thorough routine: check the weather, select the appropriate outfit, fill a water bottle, strap on a GPS watch and sync it to his phone, load a training playlist, do a five-minute dynamic warmup, run a planned route selected from a rotating set of four, cool down, stretch for ten minutes, and log the run in three apps. On good days, the pre-run setup alone took fifteen minutes. On cold, dark Tuesday evenings, those fifteen minutes became a wall. By February, Marcus was running once a week, then not at all.

Priya, who had never been a runner, built a different routine: put on shoes, walk out the front door, run to the stop sign at the end of the block and back. No watch, no playlist, no warmup protocol, no post-run data entry. She did it every day after work for six weeks straight. By week seven, she was running past the stop sign and looping around the park — not because the routine demanded it, but because automaticity had taken hold and momentum carried her. By March, Priya was running three miles. Marcus was still thinking about restarting.

The difference was not talent or discipline. Marcus had more of both. The difference was complexity. His routine contained so many steps that it never had the chance to automate. Priya's routine was so simple that her basal ganglia could encode it as a single chunk within weeks. Simpler routines automate faster than complex ones, and a routine that automates is worth infinitely more than a superior routine that never does.

Why simplicity accelerates automaticity

The routine is the behavior itself established that the routine must be clearly defined — specific enough to pass the script test, with no ambiguity about what to do. That specificity is necessary. But specificity alone is not sufficient. You can have a perfectly specified routine with eighteen steps, each one unambiguous, that still fails to automate because the sequence is too long and too complex for the basal ganglia to chunk efficiently.

The mechanism is straightforward. Ann Graybiel's research on habit encoding in the basal ganglia shows that chunking — the compression of a behavioral sequence into a single executable unit — works best with short, consistent sequences (Graybiel, 2008). Each additional step in a routine adds a node to the sequence that must be encoded. More nodes means more repetitions needed before the sequence compresses into a chunk. More nodes also means more potential failure points — each step is a moment where attention must be sustained, where a distraction could interrupt the sequence, where the cortex might reassert control and introduce deliberation. A three-step routine has three potential failure points. A fifteen-step routine has fifteen.

This maps directly onto Hick's Law, one of the foundational principles of human factors research. William Edmund Hick and Ray Hyman demonstrated in the early 1950s that choice reaction time increases logarithmically with the number of options available (Hick, 1952). Every step in a complex routine that involves even a micro-decision — which playlist, which route, how long to warm up — adds processing time and cognitive load. The aggregate effect is that complex routines feel heavy. They require engagement, attention, and executive function. Simple routines feel light. They execute almost before you notice they have begun. That lightness is not a trivial aesthetic preference. It is the subjective experience of a behavior transitioning from System 2 control to System 1 control, from cortical management to subcortical automation.

B.J. Fogg captured this principle in what he calls the simplicity chain: the easier a behavior is to do, the less motivation it requires, the more consistently it fires, and the faster it automates (Fogg, 2020). Stripping unnecessary steps from a routine reduces time, physical effort, and mental effort simultaneously. You are not dumbing down the routine. You are removing the friction that prevents the routine from reaching the automaticity threshold.

What the research shows about complexity and habit formation

Phillippa Lally's landmark 2010 study at University College London tracked 96 participants building new habits over 84 days and found that the median time to reach automaticity was 66 days — but with enormous variance. Some participants reached automaticity in 18 days. Others had not reached it after 254 days. The single strongest predictor of speed to automaticity was not personality, motivation, or environmental support. It was the complexity of the chosen behavior (Lally et al., 2010). Participants who chose simple behaviors — "drink a glass of water with lunch" — reached the automaticity plateau in roughly half the time of participants who chose complex behaviors — "do fifty sit-ups before breakfast." The sit-ups required physical preparation, mental psyching-up, physical effort, and recovery. The water required reaching for a glass. Both were habits. One automated in weeks. The other was still requiring conscious effort after months.

Wendy Wood's research reinforces this from a different angle. Wood's central argument, synthesized in Good Habits, Bad Habits (2019), is that habits form through the repeated pairing of a consistent context with a consistent behavior. The more complex the behavior, the harder it is to keep it truly consistent across repetitions. A fifteen-step routine is likely to vary slightly each time — you swap two steps, skip one when rushed, add one when you have time. Each variation disrupts the context-behavior pairing that the habit system depends on. A simple routine — three steps, same order, every time — naturally produces the iron consistency that habit formation requires. Simplicity is not just easier. It is more consistent, and consistency is the raw material of automaticity.

Fogg's data on thousands of Tiny Habits participants confirms this practically: the probability of performing a behavior on any given day is inversely related to the number of steps required (Fogg, 2020). Each step is a potential interruption point — a moment where a notification, a stray thought, or simple fatigue can derail the sequence. Fewer steps means fewer opportunities for derailment.

The simplification protocol

The practical work of this lesson is to take the fully specified routine you built in The routine is the behavior itself — the one that passes the script test — and systematically strip it to its simplest viable form. This is a structured process, not an intuitive one, because your intuition will resist simplification. Complex routines feel more serious, more thorough, more worthy of the effort. Your ego is invested in the elaborate version. The simplification protocol overrides that instinct with a deliberate procedure.

Step one: enumerate every step. Write down every action in your routine as a separate line item. Do not summarize or group. If your morning journaling routine is "sit down, open the notebook, uncap the pen, set a timer, write until the timer rings, close the notebook," that is six steps. Write all six.

Step two: classify each step as essential or optional. An essential step is one without which the routine cannot deliver its core reward. An optional step improves the experience but is not required for the fundamental behavior to occur. In the journaling example, "sit down," "open the notebook," and "write" are essential. "Set a timer" is optional — you could write without one and still journal. "Close the notebook" is optional — it signals completion but the journaling has already happened.

Step three: eliminate every optional step. Remove them entirely. Do not demote them to "nice to have" or "do if time permits." Remove them. The simplified routine is: sit down, open the notebook, write. Three steps instead of six. This version can execute in sixty seconds on a day when the full version would take fifteen minutes and therefore would not happen at all.

Step four: test the simplified version for one week. Perform the stripped-down routine every day for seven consecutive days. Pay attention to two things. First, does the routine still deliver enough reward to close the habit loop? If writing without a timer leaves you feeling unfinished and unsatisfied, the timer may be essential for you, not optional — add it back. Second, does the simplified routine fire more reliably than the complex version did? If you complete seven out of seven days when you were previously completing four or five, the simplification is working. The lost steps were friction, not value.

Step five: resist the urge to re-add. After a successful week, you will be tempted to restore the eliminated steps. This is the complexity creep that killed Marcus's running routine. Each restored step seems harmless; collectively, they rebuild the wall that prevented automation. The rule is: do not re-add any step until the simplified routine has reached full automaticity. Only then can you layer in additional elements, one at a time, testing each addition for a week before adding the next.

The minimum effective routine

Pharmacology has a useful concept: the minimum effective dose — the smallest quantity of a drug that produces the desired therapeutic effect. Below it, nothing happens. Above it, the drug works, but additional dosage adds side effects without proportional benefit.

The minimum effective routine applies the same logic to behavior. It is the smallest version of the routine that still delivers the core reward — the reward that closes the habit loop and makes the cue worth responding to tomorrow. Your journaling routine does not need a specific pen, a leather-bound notebook, a designated chair, and ambient music. It needs a writing surface and a writing instrument. Everything else increases the activation energy required to begin, and activation energy is the primary killer of habits in their first sixty days.

This is not the same as the minimum possible routine from Start smaller than you think necessary. "Take one step outside" has its place during initial habit installation, but the routine component of the habit loop must deliver enough reward to sustain the loop. One step outside does not produce the endorphin release that makes running rewarding. Running to the stop sign and back does. The minimum effective routine sits at the intersection of two constraints: simple enough to automate, and complete enough to reward.

Finding that intersection requires honesty about which elements are genuinely reward-producing and which are ritual, preference, or perfectionism. The five-minute warmup before a run may feel essential, but if you can run comfortably without it, it is ritual. The GPS tracking may feel like part of the habit, but if you can run without recording data, it is perfectionism. Strip these away and you find the routine's load-bearing structure.

The cognitive load argument

John Sweller's Cognitive Load Theory offers a deeper explanation for why simplification accelerates automation. Sweller distinguishes between extraneous load — unnecessary complexity added by poor design — and germane load — cognitive effort devoted to building lasting schemas (Sweller, 2011). In habit formation, germane load is the brain's work of encoding the routine into a basal ganglia chunk. Extraneous load is every unnecessary step, decision point, and preparation task wrapped around the core behavior. The critical insight is that extraneous load competes directly with germane load. Every unit of cognitive bandwidth consumed by unnecessary complexity is a unit unavailable for the automation process. When Marcus spends mental energy selecting a playlist and syncing his watch, those resources cannot encode the running pattern. When Priya puts on shoes and walks out the door, virtually all of her bandwidth is available for germane processing.

This is why simple routines feel different in real time, not just in laboratory measurements. A simple routine feels like it is happening to you — the cue fires, the behavior unfolds, and you notice midway through that you are already doing it. A complex routine feels like something you are doing — each step requires attention, each transition requires a small act of will. The subjective experience of automaticity arrives weeks earlier for simple routines because there is less extraneous load competing with the encoding process.

The Third Brain

An AI assistant is particularly valuable for routine simplification because it does not share your emotional attachment to complexity. You built your elaborate routine for reasons that felt compelling — each step was added because it seemed to improve the experience, because an article recommended it, because a more experienced practitioner included it. Asking yourself to remove steps feels like admitting you were wrong to include them. An AI has no such attachment. It can evaluate each step with the cold question that simplification requires: does this step contribute to the core reward, or does it add friction without adding value?

Describe your full routine to an AI and ask it to identify the three to five steps that constitute the load-bearing structure — the steps without which the routine would not deliver its reward. Then ask it to challenge each of the remaining steps. For each one, the AI should ask: "If this step were removed, would the routine still produce the reward? Would it still feel complete?" You will discover that many steps you considered essential are actually habitual — you do them because you have always done them, not because they serve a functional purpose. The AI can distinguish between structural steps and inherited steps in a way that your own attachment to the routine makes difficult.

You can also use an AI to design a complexity budget. Decide in advance how many steps your routine is allowed to have — say, five — then ask the AI to allocate those steps to maximize reward delivery while minimizing activation energy. The constraint forces prioritization: you cannot include everything, so you must include only what matters. The result is a routine designed from the constraint of simplicity rather than one that has simplicity imposed after the fact.

When simplification meets rigidity

You now have a routine that is both fully specified (from The routine is the behavior itself) and minimally complex (from this lesson). It passes the script test — anyone could execute it. It passes the simplification test — every remaining step is load-bearing. It is engineered for the fastest possible path to automaticity.

But there is a tension worth acknowledging. A routine stripped to its simplest form and executed identically every day can become brittle. What happens when you travel and your usual environment is unavailable? What happens when boredom sets in and the mechanical repetition of the same three steps starts to feel deadening? Too much simplicity can produce rigidity — and rigidity breaks under the pressure of a life that does not stay the same from day to day.

Routine variability within bounds addresses this directly: how to introduce variability within bounds. The key is not to abandon simplicity but to define a narrow range of acceptable variation — a corridor within which the routine can flex without losing its identity. The simplified routine becomes not a single fixed script but a small family of closely related scripts, any of which the basal ganglia can recognize as "the same behavior."