How to write action items that actually get done

An action item survives the week when it names one owner, one plain verb, and one date, and when it sits somewhere that owner already opens. Everything else is a souvenir from a conversation.

Laziness usually gets the blame for the ones that rot. The real cause is a sentence nobody could finish. You cannot do "align on pricing". You can send one draft of the pricing page by Thursday.

Why items die between the meeting and Thursday

An item dies when nobody can tell, by reading it, whether it has been done.

That is the whole test. Read the line cold on a bad morning. If you cannot answer done or not done in about a second, the line is decoration.

The usual killers are easy to spot once you know their faces.

• The verb is not a verb: discuss, explore, look into, align, circle back.
• The owner is a group, so the item belongs to the space between people.
• The day on it is a season rather than a date, so it can always be a bit later.
• The item exists only inside a recap that nobody opens twice.
• It is too heavy to finish in one sitting, so it never gets started.

All of these feel fine in the room, because the room carries context the line does not. Everyone in there knows who was annoyed and which half of the problem was already solved before the call started. None of that gets written down, and by midweek none of it is in anyone's head either.

One owner, one verb, one date

Write each item as a single sentence containing a person, a verb you could film someone doing, and a day.

The person goes first. A line that starts with "we" is a line nobody starts.

• "Look into the refund bug" becomes "I post the two failing refund cases in the channel by Thursday."
• "Team to align on the pricing page" becomes "You send one draft of the pricing page around by Wednesday."
• "Follow up with the supplier" becomes "I email the supplier today and paste their answer here when it lands."
• "Think about the onboarding copy" becomes "I bring two rewritten screens to the next call."

The date is the part people quietly drop, because naming a day feels like applying pressure. It is pressure. That is what it is for, and an item with no pressure in it is a wish with formatting.

Two names on one line is the other common dodge, and it is the one I will argue about. I would rather have one slightly wrong owner than a perfectly fair pair. A pair spends the week waiting to see who moves first, and both of them are being polite, and nothing happens for five days.

Make it small enough to finish in one sitting

An item you cannot finish in one sitting is a project, and a project will not move until its first step is written out as its own line.

Size is what most follow-through advice skips. People blame memory. Memory is usually fine. The item was just too heavy to pick up in the twenty free minutes anyone actually gets.

"Rewrite the onboarding" sits on a list until the list is deleted. "Rewrite the first onboarding screen" is done before lunch, and the second screen stops looking like a mountain once the first one exists.

When the real work is genuinely big, write the smallest visible piece and let the next piece fall out of doing that one. Your list then describes the week you are actually going to have.

Move it out of the recap and into your own system

An item survives only if it lives in the place its owner opens without being reminded.

A recap is a record. It is written for the group, it has to stay stable, and nobody opens it on a Tuesday to decide what to do next. Treating it as a to-do list is why careful notes so often produce nothing at all.

Copy your own items out the moment you send or read the recap, into whatever you actually open first thing, and rewrite them in your own words as you go. The rewording matters more than it should. An item phrased in someone else's language keeps reading like someone else's job.

My own list is a text file that sits next to the code I am working on. The items I copied over in my own words got done. The ones I left sitting in a thread are still in that thread, and I could show you exactly which is which.

If the item belongs to someone else, the same move has to happen on their side, and you cannot make it happen. What you can do is write the line so plainly that copying it takes them no thought at all.

Check once, halfway

Ask about an item once, halfway to the date, in a question someone can answer with one word.

Waiting until Thursday to learn that Monday never happened is not politeness. It is arranging to be surprised. How to word that check without turning into a nag is a whole separate problem, and I have already written it up, so I will not do it again here.

The part I will admit to is my own drafts. They come out soggy. Three clauses of apology wrapped around a question that was fine on its own, sent at eleven at night to somebody who will read it at nine. I make Unvent for that gap, so what leaves my keyboard is the plain line.

Kill the items that are not happening

An item that has rolled over twice should be deleted or renegotiated, never quietly moved a third time.

Rolling things forward keeps a list looking alive while the work inside it is dead. Everyone can see it happening. The list loses its authority the third time a line reappears untouched, and once that happens nothing else on the list gets read carefully either.

Say the true thing instead. "I am not doing the report this week, and I do not think it is worth doing at all" ends something. So does "this needs a full day I do not have, so it moves and I am booking the day now."

Both of those are decisions, and decisions want a person to land on. If the call is not yours to make, put it in front of whoever owns it rather than letting a dead line ride along for another week pretending to be work.

One more habit worth stealing. Once a month, read the items you deleted rather than the ones you finished, because that list tells you what you keep agreeing to in rooms and never intended to do. Mine is embarrassingly consistent. Half of it is work I said yes to because saying yes ended the conversation faster, and knowing that has made me slower to volunteer, which nobody in the meeting enjoys and every Thursday of mine has benefited from.