Why to-do lists and productivity apps fail at life admin

Productivity apps are built for knowledge work: tasks with owners, boards that move left to right, projects with a deadline. Life admin doesn't behave like that. Its tasks are connected rather than independent, so a generic list can track that something exists without ever telling you that changing one thing breaks three others.

This is for anyone who has set up a board or a list for personal admin and watched it go stale within a month. It won't tell you which specific app to pick; the mismatch sits in the structure, not the brand, and switching tools rarely fixes it on its own.

One change, as an example

Say a flight moves by four hours. In a task app, that's one card with a new time on it. In real life, it also touches the airport transfer booked separately, the hotel's check-in window, a pet sitter's schedule, and a connecting flight with its own tight layover. The list only knows about the card you edited. It has no way of knowing the transfer exists at all, let alone that it now needs a phone call before the driver shows up at the wrong time.

Where the assumptions and the work part ways

The upkeep that has no deadline

Every general-purpose tool needs feeding: categorizing, tagging, moving cards, archiving what's done. At a job that upkeep is part of the role and happens inside paid hours. For personal admin it's a second task with no deadline and no one checking, so it's usually the first thing dropped when a week gets busy.

Once the data is stale, the tool becomes worse than nothing, because it now answers confidently and wrong. A task board that still lists a subscription you cancelled months ago isn't neutral; it's actively misleading.

Interruptions cost more than the interruption itself

Life admin rarely arrives as a scheduled session. It shows up as a call while you're doing something else, a letter you open between two other things, a form due while you're mid-task on something unrelated. Research on task switching backs up why that costs more than the few minutes the interruption itself takes: workers who get pulled off a task can take close to half an hour to return to it at the same level of focus, and the switch itself raises the odds of a mistake. A tool that assumes admin happens in one dedicated block is planning for a session that, in practice, rarely comes.

What a tool for this actually has to do

1. Know what kind of thing each item is, not just that it exists, so it can show you what else a change touches.
2. Work out what's due from stored facts and real dates, rather than asking you to rank a list by hand.
3. Stay roughly accurate after being ignored for a month, because it will be, more than once.
4. Say plainly when nothing is due, and mean it, rather than manufacturing a reason to open the app.
5. Hold the connections between items across areas, not just a title and a due date.

Why this ends up needing more than one app

Knowing that a transfer depends on a flight, or that a warranty needs an annual service to stay valid, or that a nomination on a pension can override a will, requires knowing the domain those facts live in. A single generic board covering everything would have to encode all of that at once, which is how you end up with a tool that stores rows and understands none of them.

Questions people ask

Where the Companion Series fits

The Companion Series takes the opposite approach: nine Companions across six life areas, each built around the kind of admin its area actually contains rather than a single board asked to understand everything at once. See the Companion Series.