The Slow Leak: Building a Life System That Survives Week Six

Every year has a season that quietly eats your systems.

For a lot of us in software, spring is the loud one. Event season arrives, the calendar fills with travel and booths and pipeline pushes, and everything that is important but not urgent slides one week to the right. Then summer arrives and does the opposite kind of damage. It is concentrated family time, which is the point of the whole thing, but it is also five weeks where nothing strategic happens because you have deliberately stopped.

Both are fine. Both are good, actually. The problem is that neither one feels like a failure while it is happening. It is a slow leak in a tire. You top it up without thinking about it, twice, three times, and then one morning you are flat in a car park wondering when that started.

August is when you look at the tire. A pile of loose ends that were never dropped on purpose, they just stopped being visible. Writing here regularly was one of them. So was every bit of routine upkeep on the property that does not shout at you.

That is the honest starting point. Nothing in my life is obviously broken, but I have no master list aligned to my priorities across work, husband, father to three, and owner of a large property that needs constant attention.

Here is what I did notice. My work system has never failed me. It is a paper notebook next to my desk, top priorities written each morning, and I execute against them reliably. It works for one reason that has nothing to do with paper: the notebook sits in my visual field during the exact hours I am at that desk. Nothing plays that role for any of the other roles I hold.

So the strategic work gets done and the strategic life stuff evaporates. I wanted to find the leak without disappearing into the productivity rabbit hole for a month.

---

Four Frameworks, Compressed

I started where everyone starts, by asking people I respect what they actually use. Two answers came back and both said the same thing: cherry-pick, do not convert.

Here is the compressed version of what they pointed at.

• GTD (David Allen). The full system is heavy. Three mechanics carry almost all of the value: capture everything into one trusted place immediately, phrase every item as the specific physical thing you do next, and hold a recurring review where you re-decide. Capture without review just builds a pile nobody reads, so those last two are a pair.
• Cal Newport. Deep work is the famous part and it was not my gap. The useful piece is autopilot scheduling, where recurring obligations get a permanent calendar slot so you stop re-deciding when to do them. His sharper claim: a to-do list is timeless and therefore toothless. Nothing gets done until it has a time attached.
• Bullet Journal (Ryder Carroll). Rapid logging plus migration. At month end you hand-copy unfinished tasks forward, and copying something by hand for the third time is annoying enough that you either do it or admit you never will. It is a deliberate friction filter, and it is the thing digital apps are worst at.
• Theory of Constraints (Goldratt). Throughput is set by the single tightest bottleneck, and work pushed in beyond that bottleneck does not become output. It becomes inventory. Applied to a life: cap how many things are simultaneously active, or you make 30 new things happen and none of them do.

---

The Task That Was Never a Task

Everyone has an item that has survived six versions of their list. It is never the hard thing. It is usually something you could genuinely finish, sitting there in a form that guarantees you never will.

Mine was “clear the ditches.” Routine maintenance, nothing dramatic, and it still refused to move because my brain priced it as a full Saturday I do not have. That price is fictional. “Clear the ditches” is not a task, it is a project, and the actual next action is closer to walking the back stretch to see which sections need cutting at all. Ten minutes in boots.

The habit worth building is that small: when something refuses to move, ask what the next physical action is, and write down that instead. If you cannot phrase it in eight words, you are still looking at a project.

The second observation stung more. I had tried Obsidian for this and dropped it. Obsidian is not bad. It failed because it had no daily trigger, and anything I adopt has to attach to something I already do without thinking, or it dies the same way in six weeks.

---

One System, Two Surfaces

The obvious question was whether work and life belong in the same place. I argued both sides properly, because the case for separation is real. Confidentiality is not theoretical when you carry deal specifics and personnel conversations. Work capture happens at a desk, life capture happens on a phone at 19:00 when you notice the gutter.

But the complaint I actually made was that I had no master list aligned to my priorities. Priorities compete across domains. The blog post I keep meaning to write and the strategic work initiative are pulling on the same finite attention, and if they never appear on the same surface I can never weigh them. I just default to whichever is more urgent, which is always the work one.

So the split is by time horizon, not by domain. The notebook holds today, work and life both, disposable and rewritten each morning. The app holds anything that must survive past today, work and life both. Confidentiality gets solved with a rule rather than a second system: work entries are pointers, not content. The app only needs to remember that a thing exists, not what is inside it.

---

Friday, Not Monday

The review slot mattered more than I expected. Monday loses for a structural reason: a slot surrounded by meetings is a slot that gets bumped, and a review bumped twice is a review that is dead.

Friday morning is the block that is reliably mine. Reviewing on Friday also means I decide the weekend before the weekend starts, which matters because property and family work gets executed on Saturday and Sunday. The real cost is that Friday morning is my best unblocked execution time, so it is capped hard at 08:00 to 08:25 with a timer. Not “Friday morning,” which expands to fill whatever you give it.

Todoist won the tool decision on one dimension: my failure mode is things disappearing from view, and a persistent project sidebar keeps five domains permanently visible. Five projects, two sections each, Active and Someday. No tags, no labels, no filters, no priorities. If a piece of structure has not been demanded by an actual problem, I do not need it yet.

---

Week One Friction

Two things bit almost immediately.

The first was that I found myself clicking into all five buckets to see anything. That felt like the buckets were wrong. They were not. Nothing was dated, so Today and Upcoming were empty and the store was the only view available. Dating six items across the week fixed it in five minutes.

The second is a genuine Todoist limitation. Subtasks do not carry their parent into date-based views, so “walk the back stretch” shows up naked with no indication of what it belongs to. The workaround is to front-load the parent into the title: “Ditches: walk the back stretch and check it.” It looks clunky and it survives every view, every device, and any setting change. It also turned out to be a better rule than a workaround, because a good task title should be self-contained anyway. Write it for the version of you who has forgotten the context in six weeks, because that is who reads it.

---

Where This Goes

The brain dump took 25 minutes and a walk through the house room by room, then the buildings, then the yard, then each kid, then my wife, then money and admin, then my own career and health. The physical walk is what surfaces the things you have stopped seeing. Everything landed in five buckets, three things are marked active, and the rest went to Someday without guilt.

The next thing to solve is calendar sprawl, which is a real problem and a completely separate one. Work Outlook, family Google, my Google, my daughter’s, Proton. I deliberately left it alone, because mixing it in is exactly how a 45-minute start becomes a lost Saturday. First I want six weeks of evidence that this survives. This post is the first test case, and it is the one you are looking at.

---

The System at a Glance