The Companion Series

Why productivity tools fail at life admin specifically

They were designed for knowledge work, and life admin has different properties. Four mismatches that explain the abandoned apps.

2 min read30 August 2026

Most productivity tools were designed around knowledge work: projects with owners, tasks with estimates, boards that move left to right. Applied to a job, they work reasonably well.

Applied to renewing a passport, chasing a refund and remembering the boiler service, they fall apart. Not because they are badly made, but because life admin has four properties the design never accounted for.

The four mismatches

  • Tasks are independent.
  • The problem is remembering.
  • Work happens in sessions.
  • More visibility helps.

Independence is the big one

A board of tasks treats every card as a separate thing. Life admin is a web: change your address and eleven things become wrong, move a flight and three bookings need looking at, and a death makes a hundred facts urgent at once.

No general purpose tool models that, because modelling it requires knowing what kind of thing each item is. A tool that does not know a transfer was booked around a flight cannot tell you anything useful when the flight moves.

The maintenance tax

Every general tool needs feeding. Categorise the transactions, update the board, tidy the tags. That upkeep is tolerable at work, where it is part of the job and happens in working hours.

For personal admin it is a second job with no deadline and no colleague noticing, so it stops. And once the data is stale the tool is worse than nothing, because now it is confidently wrong.

Scores and streaks make it actively worse

Gamification assumes you need motivating. For work that arrives during bereavement, illness and moving, a counter of how many days you have failed is not a motivator. It is a reason to close the app.

The reliable outcome is deletion, which takes the only record of what actually needed doing with it.

What a tool for this has to do differently

  1. Know what kind of thing each item is, so it can understand relationships instead of storing rows.
  2. Derive what matters from stored facts rather than asking you to prioritise a list.
  3. Stay roughly right when ignored for a month, because it will be.
  4. Say plainly when nothing needs you, and mean it.
  5. Never score the person using it.

Which is why these are separate products

Understanding that a transfer depends on a flight, or that a warranty requires an annual service, or that a pension nomination overrides a will, requires knowing the domain. A single tool covering everything would have to know all of it, which is how you end up with something that stores rows and understands nothing.

The wider case for the category is in life admin, the work nobody teaches you.

Related guides