The Real Reason Your To-Do List Keeps Failing (It Isn't Willpower)

If you've cycled through five to-do apps and stopped opening each one within three days, you're not alone. Most people blame their own willpower. But between my own repeated failures and asking the people around me why they wrote a task and still didn't act on it, the answer turned out to be far more structural.

The task is written in a shape you can't act on

Look at the lists of people who can't stick with them, and almost all of them write tasks as nouns:

• "Hospital"
• "Tax return"
• "Quote for Company A"

They look like a proper list. But the moment you try to start, your brain fires back: "Hospital... what time was the appointment? Do I need my insurance card? Which train line was it again?" That bundle of unresolved questions hits you right before you start. That is the true source of "meh, later."

Psychologists call the energy needed to begin an action its activation energy. The number one reason to-do lists fail is that this starting cost is too high — not that you're short on discipline.

The fix: write the first action

The solution is simple. Rewrite each task as a verb — the first concrete action — instead of a noun.

• ❌ "Hospital" → ⭕ "Leave home at 8:50 on the Blue Line to make the 9:30 appointment"
• ❌ "Tax return" → ⭕ "Open the accounting app and log just one June receipt"
• ❌ "Quote for Company A" → ⭕ "Open last week's email and check only the quantity"

The trick is to make it absurdly small — "just one," "only." People don't stumble on finishing; they stumble on starting. Once the first action is fixed as a verb, momentum carries the rest.

Don't drag prep into the day itself

There's a second lever: clear the information you need to start ahead of time. For a hospital visit that's the appointment time, what to bring, and the route; for shopping it's the ingredient list; for going out it's the departure time. Trying to look all of this up in the moment is exactly what spikes the starting cost.

If you resolve the prep back when you logged the task — the energetic moment — then at execution time there is nothing left to think about. The list stops being "a place to park tasks" and becomes "a device that does your future self's thinking for you."

How to not quit in three days

• Three per day, max. A list is not a warehouse. Pick only three first-actions for today.
• Make completion visible. The small hit of satisfaction when you check something off is what makes you open the app tomorrow.
• Carry-overs get rewritten. A task you couldn't start yesterday is proof the first action is still too big. Split it smaller.

FAQ

Writing tasks in detail is itself a chore I can't keep up. What do I do? Don't try to write everything perfectly when logging. Just write the first action as a verb; add prep whenever it occurs to you. Some apps now use AI to auto-fill candidate times, routes, and items, which offloads exactly this chore.

My list gets so long I don't even want to open it. That's because you're mixing in "someday." Quarantine "someday" in a separate backlog and keep only today's first-actions in today's list. The fewer items in view, the higher your start rate.

Paper or an app? If the goal is lowering the cost of starting, an app that can hold the prep (times, routes, items) alongside the task has the edge. Paper has a low writing cost but can't keep the supporting information attached.

Takeaway

Your to-do list isn't failing because of your willpower — it's failing because the task is written in a shape you can't act on. Turn nouns into verbs, turn "perfect" into "just one," and pull the prep forward from the day itself. Those three shifts turn a list from "a thing that reminds you" into "a thing you can act on in zero seconds."

---

The author builds "THE TASK: AI To-Do Prep" (App Store, free), an iOS app that tries to automate this "first action + prep-in-advance" idea by having AI complete a written task into an actionable state (subtasks, transit, maps, items to bring). This piece isn't an ad for that app — it's shared in case the underlying idea is useful on its own. The messy parts of building it are written up in the build log series.