An action item without an owner and a date is just a wish
"We should probably look into that" is not a task. It's the absence of one, written down in a way that feels like progress.
Look at the action items from your last few meetings. Not the ones you remember — the ones that were actually written down.
A good proportion of them will look something like:
- Look into the pricing question
- Follow up with the vendor
- Think about whether we need a second environment
- Circle back on the onboarding flow
Every one of these is a wish. None of them has an owner, none has a date, and none of them will happen unless someone independently decides to make it their business.
Why the wording matters more than it should
"We should look into the pricing question" describes a topic. A task describes an act with a boundary — something that can be finished, by a specific person, by a specific time.
The gap between the two is not pedantry. It's the difference between something that can be checked and something that can only be remembered. And anything that depends on being remembered is competing with every other thing in that person's week, most of which have deadlines attached.
The three fields
Owner. One name. Not a team, not two people, not "whoever picks it up." A task owned by a group is owned by nobody — every member can reasonably assume someone else has it, and all of them are right until the next meeting proves otherwise.
If nobody will take it, that's real information: the thing isn't actually agreed, or isn't actually important. Better to discover that in the room than three weeks later.
Date. Even a rough one. The date's job is not accuracy — it's to create a moment when someone notices the thing hasn't happened. Without one there is no such moment, so the task simply doesn't exist until it resurfaces in a meeting, which is the failure mode you were trying to avoid.
A verb that can complete. "Look into" cannot finish; there is no state of having sufficiently looked into something. "Draft", "send", "decide", "book", "publish" all can. If the verb has no completion state, the task has no completion state.
Rewriting the earlier list:
- Priya drafts three pricing options by Thursday
- Marco sends the vendor the revised scope by Fri 25th
- Amara decides whether we need a second environment by next Tuesday's sync
- Jonas publishes the onboarding flow changes by end of month
Same meeting, same intentions. The second list can be checked; the first can only be recalled.
Attach the item to what produced it
There's a second failure mode, subtler than the first. A task that arrives with no context gets deprioritised, because the person holding it can no longer reconstruct why it seemed to matter.
"Draft three pricing options" a week later, stripped of the conversation that generated it, reads as busywork. Attached to the two minutes of discussion where a customer's objection made it urgent, it reads as the obvious next thing. Same task, different survival odds.
Track them where they'll be seen
The last requirement is the most mundane: tasks have to live somewhere people look without being reminded.
This is why action items buried in a meeting document reliably fail. Nobody opens last Tuesday's notes to find out what they owe — the document is a record of a past event, and people don't browse the past. The task has to sit in a surface that answers "what's outstanding?", and it has to stay visible until it's genuinely done rather than until the meeting is over.
None of this requires a heavier process. It requires that the thing you write down at the end of a meeting is shaped like work instead of shaped like a summary.