You know the cycle because you've run it. Find a promising system, or app, or method. Spend an evening setting it up properly this time. Half the time the “new system” is just another notes app pressed into service as a planner, which was never going to hold. Use it well for a fortnight. Drift. Abandon. Feel vaguely guilty. Repeat, some months later, with the next one.
The standard explanation is discipline: you didn't stick with it. I want to argue the opposite. The cycle isn't evidence that you lack discipline. It's evidence that the systems keep failing a test they were never honest about setting.
The maintenance tax
Every productivity system has two costs, and only one gets advertised. The visible cost is setup: the evening of projects, tags, contexts, and folder structures. The hidden cost is maintenance: the ongoing work of keeping the structure true. Filing new things correctly. Reviewing the lists. Pruning the stale. Keeping the taxonomy honest as your work changes shape underneath it.
The systems that get abandoned are almost always the ones with a high maintenance tax, and the abandonment follows a predictable curve. Weeks one and two, you pay the tax happily; the system is new and the paying feels productive. Then a genuinely busy week arrives, you skip the maintenance because the actual work has to come first, and the system starts drifting out of date. A drifted system is worse than none: it confidently shows you a picture that's wrong. So you trust it less, maintain it less, and the spiral completes. You didn't fail the system. The system billed you a tax that no real working life can pay every week, and then punished you for missing a payment.
There's a second mechanism underneath, and it's less comfortable: starting a new system feels productive. The setup evening is organising, and organising delivers a hit of control at exactly the moment you feel least in control. (That loop has its own post.) Some part of the cycle isn't about finding the right system at all. It's that starting one is the most satisfying part, so the cycle quietly optimises for more starts.
My twist: judge a system by its worst week
Here's the test I'd apply to anything before adopting it, and it's the one I used when building my own: not "how good is this when I'm using it properly?" but "what happens in the week I barely touch it?" A system for real life has to survive neglect. If a fortnight of chaos leaves it wrong and untrustworthy, it was only ever a fair-weather system, and your working life has weather.
Concretely, that means: capture must work with zero filing decisions, because on the bad weeks you'll capture or you'll do nothing. The picture must stay roughly true without a weekly review propping it up. And re-entry after neglect must take minutes, not an evening, or the guilt of the mess becomes one more reason to start fresh somewhere else.
How ka-do handles it
This test is most of why ka-do is shaped the way it is. Capture takes no decisions: dump it in, tidy nothing. The zones keep themselves current, because they're positions relative to today and today moves them on its own; a week of neglect leaves the picture dated but not lying. And there's no taxonomy to keep honest, because there's almost no taxonomy: a short window, an Unscheduled pile, and that's the structure. Nothing to lapse from.
What ka-do won't do is offer you the satisfying setup evening. There's genuinely little to configure, which feels underwhelming for about a day and turns out to be the entire point.
Full honesty: I ran the cycle for years, through more apps than I'll admit, and my eventual answer to it was the most extreme restart of all — I built one. But the thing I built was shaped by every abandonment that came before it, and its first design rule was the worst-week test.
The one-line version
You don't keep starting new systems because you're undisciplined. You keep starting them because they keep billing a maintenance tax real life can't pay. Pick the one that survives your worst week, not the one that demos best in your best. The systems that survive tend to share one trait: they sit underneath the organisation instead of trying to fix it.
Ka-do is built for the week you barely touch it. Try it free →