From Meeting to Action: Stopping Decisions From Evaporating

A meeting management guide: decision logs, action items, owners and dates, follow-up cadence and the recurring agenda problem.

If the agenda of your next meeting contains the topics of the last one, the problem is not the meeting. Decisions were made; nobody turned them into work.

A decision and an action are different things

A decision

“We will move to the new price list.” It states a direction but creates work for nobody.

An action

“Ayşe will prepare the new price list and send it to dealers by 15 March.” It has an owner, a date and a defined outcome.

Most meeting notes belong to the first category. Notes are taken and even shared — but there is no work inside them. The rule is simple: a decision that did not become a task with an owner and a date was not made.

What to do as the meeting ends

  1. Write the actions during the meeting. Whoever says “I’ll write it up later” usually does not, and forgets the detail if they do.
  2. Give every action one name. “The marketing team” is not an owner. Work given to two people is work given to nobody.
  3. Put a date on it. “As soon as possible” is not a date. Even an estimate should be written as a day.
  4. Spend the last two minutes reading it back. Read the action list aloud; misunderstandings surface here.
  5. Attach it to the record. If the action concerns a customer, it belongs on that customer’s record, not in a separate meeting note.

A decision log: institutional memory

Actions get done and closed; decisions remain. Six months later nobody can answer “why do we price this way?” or “why did we make an exception for this customer?”. A searchable decision record solves it:

  • When was the decision made, in which meeting, with whom present?
  • What was the reasoning — which alternatives were considered?
  • Which customer, product or process does it belong to?
  • Has it been changed since? A change is also a decision and should be recorded.

This record is most valuable when the team changes. A new joiner can search for “why do things work this way here?” instead of asking someone.

The recurring agenda problem

If the same topic reaches the agenda a third time, there are three possibilities, each needing a different response:

  1. No action was created: it was discussed, not decided. The fix is meeting discipline.
  2. An action was created but not done: an owner or capacity problem. The fix is replanning or changing the owner.
  3. The action was done but the problem persists: the most valuable case — the diagnosis was wrong. The fix is redefining the problem.

Discussing the topic again without making this distinction is holding the same meeting for a fourth time.

Measurement

  • Decisions turned into actions: how many actions came out of each meeting?
  • On-time completion: how many actions finished on their date?
  • Repeat agenda items: the most honest indicator of meeting effectiveness.
  • Unowned actions: should be zero. Anything else means outputs are being captured incompletely.

Frequently asked questions

Should every meeting produce actions?

An information session may produce none, and that is fine. But if a decision meeting produces no actions, it did not need to happen.

Where should actions live?

In whatever your task system is, not in a separate meeting notes file. An action kept in two places stops being updated in one and loses trust.

Can an action be assigned to someone who was not there?

It can, but tell them first. Surprise work appearing for someone who was not in the meeting is the fastest way to break trust in the system.

Next step: to see how actions attach to customer records, request a demo.