You didn't build it badly. You built it for a version of yourself who had two free evenings and something to prove. That person was real, briefly, and they were unusually generous with your future time.
The first week is easy to misread as evidence. Everything is captured, everything is tagged, the week ahead is legible for the first time in years. What you can't see from inside week one is how much of that legibility is being paid for by novelty — and novelty is not a renewable resource. It arrives once, in full, and then it is spent.
The cost you didn't price in
Every system has a running cost: the review, the re-sorting, the small daily decision about where a thing goes. When you set it up, that cost was invisible, because setting it up was the fun part and you were happy to pay in advance. Week two is simply the first week you are asked to pay at the normal rate, in a normal mood, on a normal Tuesday.
This is the point at which most people conclude something about themselves. It is almost always the wrong conclusion. A system that only functions at your peak has not been tested — it has been previewed.
A system that needs you at your best is not a system. It's a second job with a nicer interface.
What actually survives
The systems that last are embarrassingly plain. A single page. One list, rewritten when it gets ugly. No categories, because categories are a maintenance contract you signed without reading. The test is not how well a system works when you are motivated; it's how little it asks of you when you are not.
So the question to ask of the next thing you try isn't whether it's powerful. It's what happens to it on the worst Tuesday of the month — and whether anything at all is required of you to keep it alive.
Filed under · collapse · maintenance-cost