It starts with a clean, hopeful template. A dashboard, a few linked databases, a page for everything. For a fortnight it feels like you have finally got your life into one place.
Then a hard week arrives. You stop tending it for a few days. Something goes in the wrong place, or does not go in at all. The neat structure has gaps, and fixing it is its own chore on top of an already-full week. You tend it less. A month later you are back to notes in your phone, and it sits there, half-maintained, quietly reproaching you.
If you have done this with an elaborate app, a forest of folders, or a system you spent a Sunday building, you have not failed at organisation. You have run into a design that treats maintenance as part of the job.
Some systems ask you to build the structure, then keep it up. Every new thing needs a home: which database, which page, which property. That is fine when you have capacity. Maintenance is highest exactly when capacity is lowest: a deadline, an illness, a stretch you cannot quite name. The tool needs the most from you when you have the least.
Once a system has gaps, trust goes with them. If you are not sure the system is complete, you stop relying on it. A second brain you cannot rely on is not doing its one job.
There is a quieter version of the same tax: deciding where something belongs before you are allowed to save it. Paid on every capture. Across a busy day the sensible move becomes a note in the chat instead, where adding costs nothing and finding it again costs everything.
You can add structure when you want it, when you have the energy. Not at the moment you are trying to catch a thought before it disappears.
In jotsum, capture is type and enter. Come back after the hard stretch and the timeline is still there, with everything you put in it dated where you left it.
A good system survives your worst week.