Turn a meeting into a task list: a simple method

Most meeting notes describe what people said. That’s useful for a week or so. What you actually need afterwards is shorter: what has to happen next, who is doing it, and by when.

Those answers are usually in the notes somewhere, buried in a paragraph that starts “We talked about pricing and…”. Nobody rereads that paragraph, so the task quietly disappears.

The method below fixes this. It takes no special tools, adds about five minutes to a meeting, and works for one-on-ones as well as larger calls.

The format: one line per task

Every task gets written the same way:

Owner: what they’ll do, by when.

For example:

Ayşe: send the two pricing options to the team, by Thursday.
Me: write the beta release notes, by Friday.
Mikko: book the Wednesday call with support, today.

Three parts, every time. If one is missing, it isn’t a task yet. “Look into pricing” has no owner and no date, and it doesn’t say what “look into” means. It’s a topic, and topics don’t get done.

Step 1: Put “Tasks” at the top of the page

Before the meeting starts, open a page and write a heading called Tasks at the very top. Under it, leave some space. Then write Decisions, then Notes.

This feels backwards, since tasks come at the end of a meeting. But the order of the page decides what you read later. If tasks are at the top, you see them first every time you open the page. If they’re at the bottom, below two screens of notes, you’ll skip them.

Step 2: Listen for commitments

Tasks rarely get announced as tasks. They hide in ordinary sentences:

“I’ll take a look at that.”
“Can you send me the numbers?”
“Let’s have something ready for next week.”
“Someone should check with legal.”

When you hear one, write it under Tasks straight away, even half-finished. Don’t wait until the end of the meeting. By then you’ll have forgotten two of them.

The last example is the most common and the most dangerous. “Someone should” means no one will.

Step 3: Ask the two questions

When a commitment is vague, ask two short questions before the meeting moves on:

Who’s taking that?
When do you need it by?

That’s it. It can feel a little pushy the first few times. In practice people are grateful, because it saves a “who was doing this?” message three days later.

If a date really can’t be set yet, write down when it will be set: “Elif: confirm the launch date, at Monday’s check-in.”

Step 4: Read the list back

Keep the last five minutes for this. Read the Tasks list aloud, one line at a time. For each line, the owner says “yes” or corrects it.

This catches most problems:

Two people think they own the same task.
Nobody thinks they own it.
The date was “Friday” for one person and “end of next week” for the other.

Anything that has no owner by the end of the read-back goes into a separate list called Open questions. It’s honest about the state of things, and it stops a half-agreed idea from looking like a commitment.

Step 5: Send it within the hour

After the meeting, clean up the list and send it to everyone who was there. Keep the message short:

Thanks, all. Tasks from today:

Ayşe: two pricing options to the team, by Thursday.
Me: beta release notes, by Friday.
Mikko: Wednesday call with support, booked today.

Decided: the beta opens on 14 November.
Open: who reviews the release notes?

Within the hour matters. People still remember the conversation, so corrections come quickly. A day later, the list starts to feel like a surprise.

Then move your own tasks into wherever you keep your to-do list, with their dates. The meeting page is a record, not a place you check every morning.

Keep decisions apart from tasks

Decisions are things that are now settled: “The beta opens on 14 November.” Tasks are things someone has to do: “Write the release notes by Friday.”

Mixing them causes two problems. Decisions get treated as tasks, and nobody knows what to do with them. Tasks get treated as decisions, and everyone assumes they’re already done.

A separate Decisions heading takes ten seconds and avoids both.

Common mistakes

Writing the discussion instead of the outcome. “We discussed whether the beta should slip” is a note. “Decided: the beta opens on 14 November” is useful.

Owners that are teams. “Design: update the mockups” usually means nobody. Pick one person, even if they’ll share the work.

Dates like “soon” or “ASAP”. Turn them into a day. If it’s genuinely urgent, “today” works.

Too many tasks. If a 30-minute meeting produces fifteen tasks, some of them are wishes. Ask which three matter most this week.

Forgetting your own tasks. When you’re the one taking notes, it’s easy to write down everyone’s commitments except yours. Read your own lines twice.

A template you can copy

Meeting: Product weekly, 29 October

Tasks
- [Owner]: [what], by [when]

Decisions
-

Open questions
-

Notes
-

Paste it into a doc or your notes app before each meeting, and the method mostly runs itself.

Doing it with an app

If you’d rather stay in the conversation than type, a meeting notes app can do the first pass for you. Gistsmith, the Mac app we make, writes the note when the meeting ends and puts your own tasks at the top, with owners and due dates when they were mentioned.

Whatever produces the first draft, do the read-back and the follow-up yourself. Owners and dates only stick when the people involved have agreed to them, and that’s the part of the method no tool can do for you.