Every year, enormous numbers of people build routines. Morning routines, workout routines, journaling practices, productivity systems. Most of them are gone within weeks.
This is not a discipline problem. It is a design problem.
What routines are actually built for
Most routines are built for the idealized version of the person building them. They assume adequate sleep, available time, a stable schedule, a reasonably functional emotional state, and an absence of competing demands.
None of these can be assumed consistently.
The routine breaks on the first disrupted night, the first overloaded week, the first emotionally difficult period. Once it breaks, it typically does not restart. The failure feels like a personal failing rather than a design failure, which makes it harder to try again.
The design failure
A routine designed for ideal conditions will fail at the first deviation from those conditions. A routine designed with deviation built in will not.
The difference is whether the routine has:
A minimum viable version. On days when the full routine is not possible, what is the minimum that maintains continuity? Without this, any disruption resets to zero.
A recovery protocol. When the routine breaks, what is the clear path back? Without this, the gap between a missed day and abandonment narrows quickly.
Honesty about your actual conditions. The ones you have regularly. Including the hard days, the disrupted ones, the ones you didn't plan for. Not the idealized version.
Why the minimum viable version matters
The psychological value of maintaining continuity is high. A five-minute version of a practice has almost no direct impact but preserves the identity of someone who does the practice. From that identity, returning to the full version is natural.
Abandoning the practice entirely and then trying to restart from scratch is significantly harder. Every restart carries the memory of previous abandonment.
Building something that lasts
The most important question when building a routine is not "what is the ideal version?" It is "what can I do on my worst day?"
Build from there. Let the full version be what you do when conditions allow. Let the minimum version be what maintains continuity.
MetaOS is built around understanding how you actually function under pressure, which is the honest foundation for building anything that lasts.
The FAST Newsletter
Weekly conversation, the FAST Framework, and feedback that helps the work take. Free.