System Fragility: Why Good Systems Still Collapse
You are not bad at sticking with things. You've just been sticking with things that were never designed to survive a bad week.
I want to be precise about what I mean by that, because "bad week" is doing a lot of work in that sentence. I don't mean a rare catastrophe — a death in the family, a health crisis, something genuinely exceptional. I mean the ordinary bad week. The one where a client emergency eats your Tuesday, you sleep badly twice in a row, and something you'd normally handle without thinking takes three times the effort it usually does. That week isn't an edge case. For most people, it's a semi-regular feature of an actual life.
The quiet assumption most systems make
Almost every productivity system — the planners, the apps, the color-coded calendars — is designed and tested under stable conditions. Someone builds it (or adopts it) on a good day, with clear energy and a reasonable amount on their plate. And it works beautifully, because good days are exactly what it was built for.
Then a bad week arrives, as bad weeks reliably do, and the system doesn't bend. It breaks. A missed daily check-in turns into three missed check-ins, which starts to feel less like a system to return to and more like a system to feel guilty about — and feeling guilty about a system is one of the fastest ways to stop using it altogether.
This is the part that gets misread most often: the system's failure under stress gets interpreted as evidence about the person, not evidence about the system. "I couldn't stick with it" becomes the takeaway, when the more accurate takeaway is usually "it was never tested against the conditions I actually live in."
A system's real test isn't the good days
Here's a reframe I come back to constantly: the measure of a system isn't how well it performs when everything is going smoothly. Almost anything performs well when everything is going smoothly — that's a low bar, and it's not the bar that matters, because smooth conditions aren't where systems tend to get abandoned.
The real test is what happens when a bad week hits. Does the system have a way to bend without snapping? Can you miss three days and pick it back up in thirty seconds, or does picking it back up require an hour of reconstruction and a fresh wave of guilt? A system that only works under ideal conditions isn't really a system in any durable sense. It's a description of what you do on your best days, dressed up to look like something more reliable.
Why "just try harder to be consistent" makes this worse
The standard advice for a collapsed system is more discipline next time — set a stronger intention, use more willpower, don't let yourself off the hook. This advice assumes the system was sound and the person was the weak link.
But if the system itself was built on an assumption of stability that doesn't match reality, more willpower doesn't fix a design flaw. It just delays the next collapse by a little while, at a higher personal cost, and sets up the same guilt cycle to repeat with a new tool next time. Eventually this produces a genuinely painful pattern: a growing collection of abandoned systems, each one treated as further evidence of a personal failing, when the actual common thread was that none of them were built to survive contact with an ordinary hard week.
This is where I think most productivity advice measures the wrong thing entirely. It optimizes for consistency — don't break the chain, don't miss a day — when the trait that actually determines whether a system survives a real year is recovery: how cheap and how fast it is to rejoin after a gap, of any length, for any reason. A system that demands consistency will eventually meet a week it can't survive, because everyone eventually has one. A system built around recovery treats that week as the normal case it was designed for, not an exception it has to apologize for.
What a question can do instead of a verdict
The next time a system falls apart, there's a more useful question available than "why couldn't I stick with it." Try: what did this system assume about my life that wasn't true?
Did it assume a consistent hour every day, when your hours are genuinely unpredictable? Did it require remembering where you left off, with no easy way back in after a gap? Did it treat every day as equally available, when some days you have far less to give than others?
The answer to that question usually points somewhere useful — not toward more discipline, but toward a different design. Something simpler. Something that degrades gracefully instead of collapsing outright. Something built for the week you actually have, instead of the week the system's designer imagined you'd have.
The pattern underneath
Like the last two patterns in this series, this one often traces back to the same root: a system built without enough slack to absorb the ordinary volatility of a real life ends up looking fragile — not because you're inconsistent, but because volatility is the normal condition, and the system was quietly designed to pretend it isn't.
