Meeting notes that never become tasks

1. Write decisions before discussion

Start the handoff with decisions that changed the plan. Use a complete sentence: “The launch moves to Thursday” is actionable; “launch timing” is a topic. If the group discussed something without deciding it, place it under open questions instead.

Record the condition attached to a decision when it matters. “Use the smaller plan if the import finishes by Tuesday” keeps the fallback from disappearing.

2. Give every action one owner

An action can involve several people, but one person should own the next visible result. “Design team” and “everyone” are difficult to follow up with. Name the person responsible for moving the item to its next checkpoint, even when someone else will review it.

Write the expected artifact beside the owner: a revised file, a yes-or-no answer, a scheduled call, or a working test. This makes completion observable without reconstructing the conversation.

3. Replace vague deadlines with checkpoints

“Soon” and “this week” age badly. Use a date, time zone when relevant, and what should be visible at that moment. If the final deadline is distant, add an earlier checkpoint that can reveal whether the work is drifting.

End with unresolved questions and the person who will resolve each one. Questions without owners become the hidden reasons tasks stall.

What usually goes wrong

• Publishing a transcript and assuming readers will extract their own actions.
• Mixing proposals, decisions, and tasks in one chronological paragraph.
• Assigning an action to a department instead of one accountable owner.
• Creating a task with a due date but no description of the expected result.