Habits & Systems — The Architecture of Behavior

Replace willpower with architecture. Read Wood and Fogg — the primary research underneath the popular habit books — and install three habits using the documented mechanisms (context-cue design; B = MAP; tiny-anchor recipes). Walk away with three habits running on automatic, a 60-day SRHI automaticity curve for one of them, and a written habit-design protocol you can use to build the next habit without rereading the books. Habits are database indexes. Non-zero build cost; near-zero query cost forever after. Engineers happily pay index-build cost on schemas and refuse the equivalent cost on behavior — because this build cost is felt. The 28-day install is the index build; the decade of automatic execution is the query payoff. Cue → routine → reward is event → handler → callback. You don't write code that asks "should I respond to this request?" on every call; the dispatcher routes automatically. When a habit fails, the diagnosis is the routing didn't fire (unstable cue, ambiguous anchor) — not the response was wrong. B = MAP is the stack trace: Motivation, Ability, or Prompt — which variable threw? Bad habits are anti-patterns, and you already know you don't remove an anti-pattern by deletion — you introduce a new pattern that occupies the same architectural slot and make it the default. Wood's data says the same: attack the cue and context, not the routine. And the deepest mapping: habits are configuration; willpower is code. Prefer configuration to code in your own behavior — the habit is the YAML; the willpower is the if-statement you no longer have to maintain.