David Ogaro
← All articles

Discipline Is a System, Not a Feeling

Discipline & Growth — Fitsum Admasu via Unsplash

I used to wait to feel motivated before doing hard things, and for a long time I genuinely believed that was a reasonable way to operate — that discipline was a kind of internal weather you either woke up with or didn't, and the people who seemed relentlessly consistent simply had better weather than I did. I don't believe that anymore, and the thing that changed my mind wasn't a self-help book. It was noticing how much my professional work as a systems architect had already taught me about exactly this problem, just applied to code instead of people.

In software, you don't build a reliable system by hoping the servers feel motivated to stay up. You build redundancy, you remove single points of failure, you design so that the correct behavior is the path of least resistance rather than something that depends on a component performing heroically under pressure. A well-designed system produces consistent output specifically because it doesn't rely on any one part of it being exceptional in the moment. I had spent a decade internalizing this principle professionally while completely failing to apply it to my own habits, where I kept expecting a version of consistency from myself that depended entirely on feeling exceptional every single morning.

The shift that actually worked was treating my own behavior as a system to be designed rather than a character trait to be summoned. Instead of asking "how do I become someone with more willpower," I started asking the much more specific and answerable question I would ask about any unreliable system: where exactly is this failing, and what's the smallest structural change that would make the failure less likely? It turns out that's a far more productive question than any amount of motivational self-talk ever was.

A concrete example: I used to fail at exercising consistently, and I told myself this was a discipline problem. When I actually looked at the failure pattern the way I'd look at a bug report, it wasn't a discipline problem at all — it was that I'd only succeed on days when I decided, at the actual moment, whether and when to go, which meant every single day required a fresh act of willpower under whatever conditions I happened to be in that day, tired or not, busy or not. The fix wasn't more willpower. It was removing the decision entirely — a fixed time, clothes laid out the night before, no morning choice left to make. The failure rate dropped enormously, not because I became a more disciplined person, but because I stopped requiring discipline from a part of the process that didn't need to depend on it.

This reframing has a humbling side effect: it makes it much harder to feel morally superior about your own good habits, because you start to notice how much of what looked like character was actually just favorable design — an environment that made the right behavior cheap and the wrong behavior expensive. I'm not more virtuous than I was five years ago. My environment is better engineered around the person I actually am, including my actual, unglamorous weaknesses, rather than the more disciplined hypothetical person I kept designing my routines for.

The other principle I borrowed from engineering is smaller and maybe more useful day to day: fail fast and cheap, rather than trying to prevent every possible failure in advance. I used to treat a missed day of a new habit as evidence the whole plan had failed, which usually meant I abandoned it entirely rather than just resuming the next day. Systems that are actually robust don't try to never fail — they're designed to fail small and recover quickly. A missed day is a small, cheap failure if you treat it as one. It only becomes an expensive failure if you let it cascade into abandoning the whole system out of something closer to shame than reason.

Growth, in this frame, stops being about becoming a fundamentally different, more disciplined person, and becomes something closer to an ongoing engineering practice: notice where the current design is producing inconsistent output, make a small structural change, observe the result, adjust again. It's slower and less inspiring than the story of sudden willpower and transformation. It's also, in my own experience and in watching people I've mentored, considerably more likely to actually hold up over years rather than weeks.