How to Write Action Items That Actually Get Done

An action item given to everyone in the room is, in practice, given to no one. In a classic 1968 experiment, college students who believed that others had also heard a person in trouble felt less personally responsible and were slower to report it than students who believed they alone had heard.¹ Meetings recreate that situation every week, one “we should” at a time.

Meeting action items are more likely to get done when each one names a single owner, starts with a verb that describes a finished result, carries a date, is written where the group can see it, and is checked at the next meeting. In a 2012 study that videotaped real team meetings, teams with more action planning and problem-solving talk reported more satisfying meetings, and constructive meeting talk was linked to the organization’s success years later.² The five steps:

1. Give every action item one named owner
2. Start it with a verb and say what done looks like
3. Put a date on it
4. Write it where the whole group can see it
5. Check it at the start of the next meeting

Put together, a finished item is one plain sentence: “Marco sends the revised launch checklist to the whole team by Wednesday.” It goes into the shared notes while everyone is still in the room, and it is read out again at the top of next week’s meeting, where Marco says whether it is done. Anyone who missed the meeting could check it.

Why the last minutes of a meeting carry so much weight

The minutes a team spends turning discussion into plans for action go with better meetings, according to Simone Kauffeld and Nale Lehmann-Willenbrock’s 2012 study of real team meetings, which linked action planning, alongside problem-solving talk, to more satisfying meetings.²

This guide picks up where what usually sinks a meeting leaves off. Once the talk has turned from complaint to solutions, the question is how each solution leaves the room with a person attached to it.

The study

Moderate evidence

Kauffeld and Lehmann-Willenbrock's meeting tapes, 2012

The pair filmed 92 regular team meetings and coded the interaction with the act4teams scheme. Team and organizational outcomes came from questionnaires and telephone interviews. More action planning and problem-solving went with higher meeting satisfaction, better meetings also went with more productive teams, and constructive meeting talk was linked to how the organization was doing 2.5 years after the meeting.²

Its strength is that it recorded what teams actually said, rather than relying only on how people felt about their meetings afterward. It is still an observational studyobservational study: A study in which researchers record what people already do or are exposed to, rather than assigning anyone to anything. It can show that two things go together, not that one causes the other, because the groups being compared may differ in other ways as well.Full entry in the glossary: action planning and good outcomes travel together here, but the design cannot show that one produces the other, and the abstract does not separate action planning from the rest of the constructive talk.

Picture two teams leaving the same discussion about a supplier who keeps delivering late. The first agrees the supplier is a problem and that someone should talk to them. The second leaves with “Dana calls the supplier on Tuesday and reports back on Friday.” Both meetings felt productive. Only the second produced something anyone can check.

A 2026 Annual Review article on meeting science, led by Steven Rogelberg, gives whoever runs the meeting the same advice: summarize the key points and be clear on action items.³ Leave time for it. Reserve the last few minutes of each agenda item, not the last thirty seconds of the meeting, for deciding who does what next.

Why “we should” tasks go undone

Tasks assigned to a group tend to slip because each member can assume that someone else will act, a pattern psychologists call diffusion of responsibility. John Darley and Bibb Latané studied it in their 1968 experiment, in which the presence of other listeners reduced each person’s feeling of personal responsibility and slowed their response.¹

Later research kept finding the pattern. In a 2011 meta-analysismeta-analysis: A study that combines the results of earlier studies on the same question into one overall estimate. Pooling makes the estimate more precise, but it cannot repair the studies it pools: a meta-analysis of surveys is still survey evidence.Full entry in the glossary, Peter Fischer’s team pooled bystander studies covering more than 7,700 participants and confirmed that the presence of other people reduces the likelihood that any one person helps, though less so in situations people saw as dangerous.⁴ Those studies concern emergencies, not work, so the lesson for meetings comes by analogy.

Closer to office life, a 2002 experiment by Greg Barron and Eldad Yechiam suggested that addressing an email request to several recipients at once may reduce the number of helpful replies. We could read only a short published summary, so treat it as a pointer rather than a measurement.⁵ Effort shows a related pattern. Steven Karau and Kipling Williams’s 1993 meta-analysis found that people tend to work less hard collectively than individually, and that the chance of having one’s own contribution evaluated was one of the strongest influences on how much.⁶

A product team agrees that “we need to update the customer FAQ before launch.” Five people nod. The support lead assumes marketing owns it, marketing assumes support does, and the engineer assumes it was never an engineering job. Launch day arrives with the old page. Nobody failed at their task, because nobody had one.

Myth

Giving a task to the whole team shares the load.

Fact

A shared task lets each person assume someone else has it. A named owner can still ask others for help.

The fix costs one question. Whenever you hear “we should” in a meeting, ask “who will?” before moving to the next item. Naming an owner does not mean that person does all the work: their job is to make sure it happens, which is the same logic that gives each row of a RACI chart a single Accountable person.

How to write meeting action items that get done

A meeting action item built to get done has five parts: one owner, a verb with a visible result, a date, a shared record and a check at the next meeting. The first three shape how the item is written; the last two decide whether anyone looks at it again. No trial has tested the five together in meetings, so each step below says where its evidence comes from.

1. Give every action item one named owner

Write a person’s name, never a team, a shared role or “we”. The diffusion research is the reason: when responsibility is shared, each person’s sense of it shrinks.¹ If the task needs several people, name one owner who coordinates them. If the right owner is not in the room, record the item as a request to that person and confirm it with them before treating it as assigned.

Say the owner’s name out loud as you write it. It sounds formal the first few times, but it gives the named person a moment to object (“I can’t take that this week”) while the group is still there to find someone else, instead of a week later when the date has already passed.

2. Start it with a verb and say what done looks like

“Budget” is a topic. “Send Sam the vendor quotes before the budget review” is an action item. Goal-setting research explains why the wording matters. In their 2002 review, Edwin Locke and Gary Latham report that specific, difficult goals consistently produced better performance than an instruction to “do your best”, because a vague target lets each person decide privately what success means.⁷ They studied goals, not meeting tasks, but the problem they describe, ambiguity about what counts as finished, is exactly what a vague action item creates.

Could someone who missed the meeting tell, a week later, whether the item is done? If not, rewrite it.

3. Put a date on it

A date sets the pace. Locke and Latham report that tight deadlines led to a faster work pace than loose ones, in the laboratory and in the field.⁷ Planning the moment you will begin, which researchers call an implementation intentionimplementation intention: A plan in if-then form that ties a specific action to a specific situation, such as 'if it is nine o'clock, then I open the report.' It hands the decision about when and where to act to the situation itself.Full entry in the glossary, helped people reach their goals across 94 tests in Peter Gollwitzer and Paschal Sheeran’s 2006 meta-analysis, and setting goals with if-then plans walks through the method and its newer evidence.⁸

In practice, let the owner say the date aloud and write down exactly that. “Next week” becomes a day, and “soon” becomes a decision.

• Owner: one named person, not "we" or "the team"
• Verb and result: what "done" looks like, starting with an action word
• Date: a day, not "soon" or "next week-ish"
• Record: written where the whole group can see it
• Check: reviewed at the start of the next meeting

4. Write it where the whole group can see it

An item that lives only in one person’s notebook is easy to lose and impossible for anyone else to check. Benjamin Harkin and colleagues’ 2016 meta-analysis pooled randomized studies that prompted people to track their progress toward a goal. Tracking helped them get there, and more so when progress was written down and when it was shared with others or made public.⁹ Almost every study in the pool involved a health goal, from weight loss to blood pressure, so applying the result to meeting tasks is a reasoned transfer that no one has tested.

Where the list lives matters less than that everyone can find it: a shared document, the team’s task board, or the top of the next agenda. Full minutes, the follow-up email that carries them and a log of team decisions each answer different questions, and each is a planned guide of its own in the meetings and workplace communication section.

5. Check it at the start of the next meeting

Opening the next meeting with the open action items turns each one into a short progress report made in front of colleagues. In Harkin’s review, progress that people reported to someone or shared publicly showed bigger effects than progress tracked in private.⁹ Locke and Latham add that goals work better with feedback on progress, because people cannot adjust their effort or strategy without knowing where they stand.⁷

1. 1Read the itemowner, task and date, as written
2. 2Owner answersdone, blocked or a new date
3. 3Close, help or rewriteremove done items; fix the rest

Keep it brisk: a sentence per item. An item that slips twice deserves a real conversation about whether the owner, the result or the date was wrong. An item that is no longer needed should be closed openly, with a word on why, rather than left to fade: a list full of dead items can teach people that the list does not matter. The check also tells people their items will be read again, and the chance of being evaluated was among the strongest influences on group effort in Karau and Williams’s meta-analysis.⁶

Before anyone leaves the room

• Every item has one named owner
• Every item starts with a verb
• Someone else could tell when it is done
• Every item has a day, not "soon"
• The list is in a place the whole group can see
• The next agenda opens with these items

Download PDF ↓

Get this checklist as a one-page PDF. We'll email you the download link.

Your emailAlso send me the weekly newsletter (launching soon)Email me the PDF

We use your address to send this link and, only if you tick the box, the newsletter. Privacy policy.

Where each step borrows its evidence

The five steps rest on well-studied psychology, but no randomized trial has yet tested any of them as a meeting practice. The closest meeting evidence is observational, and the 2026 Annual Review still lists as an open question how AI tools that automate follow-up, such as summaries, task assignment and progress tracking, affect meeting outcomes and team accountability.³

Read the table as a map of where each habit gets its support. The strongest findings come from settings unlike a team meeting, and the one study here set inside real meetings cannot show cause. That is a reason to try the steps and watch what happens on your own team. A simple way to watch: for the next month, note at each meeting how many items were closed by their date. If the share rises once the team uses all five parts, keep them; if it does not, look for the part that keeps getting skipped.

The bottom line

An action item is finished being written when someone who missed the meeting could read it and know who will do what by when. Give each one a single owner, a verb, a date and a place on a shared list, then open the next meeting by checking the list. The evidence behind each habit is indirect, so for a month note how many items closed by their date and keep the parts that raise that share.