· by 42 todo!

You don't need a to-do list system

The search for a to-do list system usually starts the week after something got dropped. A missed renewal, an awkward apology, and now you're up at midnight reading about famous methods.

Here's what we'd tell you before you build anything. The dropped ball almost never came from having no system. It came from one unwritten task, and no amount of weekly reviewing catches what never got written down.

The Sunday you built the system

It's a nice Sunday, honestly. You pick a method, set up the lists, decide what goes where, maybe watch a video by a man with strong opinions about folders. It feels like finally taking this seriously.

Monday through Wednesday, the system is great. Then Thursday gets loud, Friday gets worse, and by the next Sunday you owe the system an hour of upkeep you don't have. Skip it once and the whole thing feels behind, and things that feel behind get abandoned1.

Rules are chores in disguise

Every rule in a system is a small recurring chore. Sort the inbox daily. Review weekly. Tag by context. Keep projects separate from areas, whatever an area is.

Each one sounds cheap on that Sunday. But you pay for them during real weeks, and real weeks are exactly when you can't. A system that needs feeding during your worst week is a houseplant that dies every time you travel.

The two habits that survive

Strip every famous method down to what its happiest users actually do, and you find the same two habits.

They write things down the moment things show up, wherever they happen to be. And they put a day on anything that isn't for today, so the list carries itself forward. Those two habits survive vacations, flu, and product launches, because neither one needs a Sunday.

What the fancy parts were standing in for

The elaborate parts of systems are mostly patches over hard writing-down. When saving a task takes six steps, you need an inbox to dump things into, then a rule for emptying the inbox, then a review to catch what the emptying missed.

Make writing it down cost one sentence from wherever you're standing, and that whole scaffold has nothing left to hold up2. The reviews get short because nothing piled up, and the someday list stops mattering because everything either has a day or didn't deserve one.

A bad month is the real test

Judge any setup by its worst month, not its first week. In the bad month you'll skip every ritual, ignore every folder, and do exactly one thing: scribble tasks down and glance at today.

If the setup keeps working under just that, it can carry you through anything. If it needs the rituals to stay standing, the bad month knocks it over and takes your trust in lists down with it.

You never needed the system, just a list that keeps working when you can't.

Frequently asked questions

What's the best to-do list system?

The one with the fewest rules you'll actually break. For most people that's two habits and no name: write it down the moment it shows up, and put a day on anything that isn't for today. Everything past that should have to prove it earns its upkeep.

Does GTD work?

Parts of it are genuinely right, especially writing everything down the moment it shows up. The full routine, with the weekly review and the many lists, is where most people fall off. Keep the writing-down, put days on things, and feel free to skip the ceremony.

How do I actually stick with a to-do list?

Make adding a task nearly free, from anywhere, and keep today's list short enough to finish. People don't quit lists out of laziness, they quit lists that demand maintenance. A list that needs nothing from you is easy to keep for years.

What system does 42 Todo! push?

None. It's tasks, dates you say in plain words, and a few lists you name yourself, reachable from your phone, your car, Slack, and the AI assistants you already talk to. The product is built on the two habits, and the rest we deliberately left out.

Footnotes

  1. The weekly list, without the ceremony what happens when the ritual grows into an hour of tidying.
  2. What a to-do list app is actually for the one job underneath every method with a name.