Directory · R
New here? Start with the premise →
Routine
2 min read · 514 words
Routine is the structured repetition the operator runs daily — and the routines being run determine much of what the life produces.
Most operators have routines whether or not they have designed them. The morning sequence. The work pattern. The evening configuration. The weekly rhythm. These run by default, accumulating across years into the cumulative pattern that constitutes much of the operator’s life. The routines that produce useful output produce useful lives. The routines that don’t produce dysfunction at scale, even when each individual instance looks small.
The mechanism most operators get wrong: trying to change routines through willpower in single instances. The single morning where the operator did the better routine. The week of trying to follow the new schedule. These usually fail — the underlying routine reasserts because it has the weight of many repetitions behind it, and the new behavior is competing against significant inertia. Lasting change to routine requires sustained substitution: running the new pattern repeatedly until it has accumulated enough weight to compete with the old pattern, and continuing to run it past the point where the old pattern still pulls.
The other distortion: the cultural narrative around routines that emphasizes elaborate optimization. The morning routine that requires two hours of compound activity. The evening wind-down with eleven specific elements. The weekly schedule that looks designed by someone in a wellness magazine. Most of these don’t sustain because they were too elaborate to begin with. The routine that lasts is usually simpler than the operator initially designed, because the operator can sustain the simpler version across the conditions of actual life.
From the chair: identify the routines currently running. The honest catalog of what actually happens in a typical day, not the aspirational version. The routines that are producing useful output can be left alone. The routines that are producing dysfunction warrant attention. Among those, identify the small change — not the elaborate redesign — that would shift the most important element. Run the change consistently for long enough that it accumulates weight. Then assess whether further changes are warranted.
The other discipline: protect the routines that work. The operator who has installed effective routines and then lets them be eroded by other demands loses the structure that was producing the output. The morning routine that gets interrupted because of an early call. The exercise routine that gets skipped because of a busy week. The reading time that gets consumed by other inputs. Each erosion is small; cumulative erosion across months degrades the routine until it functionally is not running anymore. Defending the routines requires saying no to some of the demands that would otherwise erode them, which is uncomfortable in the moment and is often what determines whether the routine survives or not.
The operator who has good routines, defended consistently, runs a substantially different life from the operator running on whatever defaults happen to install. The routines compound. The early years of routine work produce capacity in the later years that the unrouted operator does not have access to.