Task organising

Next actions: writing a to-do list you'll actually do.

Most to-do lists are lists of projects wearing task costumes. The next-action format fixes the stall.

By Mathias CelisApril 28, 20265 min readLast updated July 2026
TL;DR

A next action is the single, physical, visible next step on something: 'Email Anna the draft for review,' not 'Website project.' Lists stall when entries are secretly projects requiring a decision before any action is possible. The fix: every entry starts with a verb, names one concrete step, and could be started cold by a tired version of you.

Look at a stalled to-do list and you'll find the same species of entry over and over: "Website," "Insurance," "Mom's birthday," "Q3 planning." None of these is a task. Each is a project wearing a task costume, and each requires a decision before any action is possible, which is exactly why the eye slides past it every single day. The list isn't failing from laziness. It's failing from ambiguity.

The next-action standard

David Allen's fix, and the most practically useful idea in GTD: every list entry must be the single next physical action, described so concretely that you could watch someone do it. His test is visibility. "Plan the offsite" fails; nobody can watch you plan. "Email the team three date options for the offsite" passes. The rewrite takes ten seconds and changes the entry from a small daily guilt into something a tired version of you can start cold.

Anatomy of an entry that works

  • Verb first. Email, call, draft, review, book. The verb is the ignition.
  • One step only. The next action, not the next five. When it's done, the following one gets written.
  • Context attached. The link, the name, the deadline, sitting in the entry. If completing it requires a search expedition first, the entry is unfinished.

Projects still exist, elsewhere

The offsite, the website, the insurance situation: these live on a separate projects list, each defined by its outcome. The working rule that connects the two lists: every active project has exactly one next action on the actions list at all times. Project stalled? Check whether its next action exists and passes the visibility test. It almost never does, and writing it un-stalls the project more often than any motivation trick.

If nobody could watch you do it, it isn't an action yet.

Where email fits

Most next actions arrive disguised as email, which makes extraction (getting the verb, the deadline, and the source link out of the thread) the daily skill; the full format is here. It's also the step Pidgy automates: requests in your Gmail or Outlook inbox become verb-first next actions with the thread attached, so the list builds itself to the standard instead of depending on your discipline at 4pm. Choosing which action to do next is a separate question, covered in prioritising when everything is urgent.

Frequently asked questions

What is a next action in GTD?

The single next physical step that moves something forward: a call to make, an email to send, a draft to open. David Allen's test is visibility: you could watch someone do it. 'Plan the offsite' fails the test; 'Email the team three date options' passes.

Why do to-do lists stop working?

Usually because entries are projects, not actions. 'Sort out insurance' requires decisions before anything is doable, so the eye slides past it every day and the list becomes a guilt archive. Rewriting each entry as its literal next step restores movement.

How specific should a task be?

Specific enough to start cold: verb first, one step, any needed context attached (a link, a name, a deadline). If tasks come from email, keep the source thread linked; Pidgy does this automatically when it converts emails into next actions.

Pidgy on top of the panel, looking through binoculars

Let Pidgy read your inbox so you don't have to.

Pidgy turns what lands in Gmail and Outlook into clear next actions, waiting-fors, and reference. One place, nothing slips.

Join the waitlistSee how Pidgy works