Key takeaways
- An action item is the smallest unit of agreed work: one thing, one owner, one deadline, written down somewhere both people can see it.
- It is not a task and not a note. A task is work already tracked. A note records what was said. An action item is the promise in between, and it is the one with no home.
- The three parts are the whole definition. Drop the owner and it is a wish. Drop the deadline and it is a someday. Drop the record and it is a conversation.
- Most action items are agreed in chat and lost in chat, because writing one down is a second task that lands right after everyone agreed the first one was handled.
- The test of a good one is whether somebody who was not in the room could pick it up a week later and know what to do.
An action item is a single task, assigned to one person, with a clear finish. It comes out of a conversation rather than out of a plan. If nobody can say who owns it or how you would know it was done, it is not an action item yet.
What is an action item?
Wikipedia opens its entry with a good one: in management, an action item is a documented event, task, activity, or action that needs to take place.
The word doing the work in that sentence is documented. Something everyone nodded at in a conversation is not an action item. Something written down, with a name against it, is.
In practice a real one has three parts, and dropping any of them is what turns it back into a nod.
- An owner. One person, not a team and not a channel. Two owners means nobody.
- An outcome you can check. Look into pricing cannot be finished. Send the new pricing sheet to Dana can.
- A date. Even a rough one. Without it the item is a wish with a name attached.
How is an action item different from a task or a note?
These three get used interchangeably, and it causes real confusion during a handover, so they are worth separating.
- A note records what was said. Dana raised the pricing question. Nobody owes anything.
- An action item records what somebody agreed to do about it. Dana sends the updated pricing sheet by Friday.
- A task is what that action item becomes once it lives somewhere that tracks it. The same sentence, now with a status and a place to check it.
The gap between the second and the third is where most of them die. The agreement happened. The tracking never did.
What does a good action item look like?
The difference is almost always specificity, and you can hear it if you read the pair aloud.
- Weak: follow up with the client. Strong: Priya emails the client the revised scope by Tuesday and posts their reply in this channel.
- Weak: we should fix the onboarding bug. Strong: Sam opens a ticket for the onboarding bug today, with the reproduction steps from this thread.
- Weak: think about the Q4 numbers. Strong: Alex brings a first draft of the Q4 forecast to Thursday's call.
Every strong one names a person, something to produce, and a moment. Every weak one could stay true forever without anybody doing anything about it.
Where do action items actually get made?
The standard advice assumes a meeting. Wikipedia describes action items as being recorded in the meeting minutes and in the task list of the group, which pictures a room with an agenda, somebody taking notes, and a board to copy them onto afterwards.
That is not where most of them happen now. They happen in a thread. Somebody asks a question in a channel, three people answer, and one of them says I will handle it. That sentence is an action item. It has an owner and it has an outcome. It has no minutes, no note taker and no board.
Teams who work this way are not being sloppy. Chat is genuinely faster than a meeting for most decisions. It simply has no step where the decision gets written down, because nobody in the thread has that job.
Why do the ones agreed in chat go missing?
Four failure modes, and they compound.
- The agreement scrolls. A thread from Tuesday is unreachable by Friday, and nobody remembers which channel it was in.
- The owner is implied. Someone should ping legal is agreed by everyone and owned by no one.
- The finish is undefined. Work that cannot be marked done stays open in somebody's head instead of on a list.
- Rewriting it is a second job. Copying an agreement out of a thread and into a tracker takes a minute, and it is the exact minute nobody has right after a decision.
The fourth one is the one that actually matters. Most teams already know they should be tracking this. The cost of the retyping is what stops them, and no amount of advice about discipline makes that cost any smaller.
How do you write one that survives the week?
Two habits do most of the work, and neither of them needs a new tool.
- Say the sentence back. Before the thread moves on, write the item as one line with a name in it. So Priya sends the scope by Tuesday. It takes seconds, and it catches the ones nobody actually agreed to.
- Put it somewhere other than the thread. A tracked ticket, a shared list, anywhere that is not the conversation it came from. The thread is the worst place to leave it, because the thread is where it already got lost once.
If your team keeps everything in one tool, the second habit is easy. If the work lives in Linear and the conversation lives in Slack, you are back at the retyping problem, several times a day.
What does Ray do about this?
Ray sits in the channel and does the transcription step. When somebody commits to something in a thread, Ray can turn it into a tracked ticket in the tool your team already uses, carrying the owner and a link back to the thread it came from.
Two things are worth knowing before you try it. Ray reads the channels it has been added to and decides for itself when something is worth acting on, so nobody has to remember a command. Anything that writes to another tool, creating that ticket included, asks for approval first.
What Ray does not do here
Worth knowing before you try it, rather than after.
- Ray does not attend meetings and does not transcribe calls. If your action items are agreed on a video call rather than in a channel, Ray never hears them and cannot capture them.
- Ray does not produce meeting minutes. It captures individual commitments as they are made in chat, which is a different job from writing a record of a meeting.
- Ray reads only the channels it has been added to. Anything agreed in a private channel or a direct message it is not part of stays invisible to it.
- Deciding what counts as a commitment is the model's judgement, and in busy channels it is deliberately biased towards staying quiet. It will miss some, and it would rather miss one than turn every hypothetical into a ticket.
What people ask next
What is the difference between an action item and a task?
An action item is the commitment as it was agreed, usually a sentence somebody said out loud. A task is that same commitment once it lives somewhere with a status and an owner. Most teams lose their action items in the gap between the two.
Who should own an action item?
One named person. Assigning one to a team or to a channel reliably produces nothing, because everybody assumes somebody else picked it up.
Do action items need a due date?
A rough one is enough and it beats none. Without any date the item cannot be chased, and anything that cannot be chased quietly becomes optional.
Where should action items be written down?
Anywhere except the conversation they came from. A tracker your team already checks is ideal, but a shared list beats a thread, because the thread is where the item got lost the first time.
Sources
- Wikipedia, Action itemThe formal definition quoted in the first section, and the description of action items being recorded in meeting minutes and in a group task list.
Read next
- Create a Jira ticket from Slack, without leaving the threadChat becomes a real ticket, in your tracker. How it works, what it looks like in a channel, and what Ray does not do here.
- A Slack standup bot that already knows what happenedStandups built from the record, not from memory. How it works, what it looks like in a channel, and what Ray does not do here.
- SecurityThe approval gate, tenant isolation, what Ray never does, and the memory controls.