Operations
Meeting minutes that turn into actions
Think about where your last set of meeting minutes is now. Written up neatly, saved to a folder, emailed round - and never opened again. The meeting happened, the notes exist, and by the following week the three things everyone agreed to do have quietly evaporated. Then the next meeting spends its first fifteen minutes reconstructing what was decided last time. This is the single most common failure of meeting minutes, and it has nothing to do with how well the notes were written.
The problem is architectural. Most minutes are a dead end - a record of a conversation that finishes when the file is saved. What a meeting actually produces that matters is two things: decisions and actions. Both need to outlive the meeting, and a notes page is where they go to die.
Minutes are not the deliverable - the follow-through is
A meeting is expensive. Six people for an hour is the better part of a working day gone. The return on that cost is not the discussion; it is what changes as a result. And what changes is carried entirely by the decisions made and the actions assigned. If those do not survive to the next meeting, the hour bought you nothing but a nicely formatted document nobody reads.
So the right way to think about minutes is backwards from the output. The notes matter only insofar as they capture the decisions and hand the actions to named people with dates. Everything else - who said what, the texture of the debate - is context. Useful, but not the point.
The chain: agenda to minutes to action log
A meeting record that works is not one page, it is a short chain, and each link feeds the next.
The agenda comes first, and it does real work. Listing the items, an owner for each and a rough time-box before the meeting is what stops the meeting sprawling. It also sets up the minutes: the same header - title, date, chair, attendees, apologies - carries straight through, so you are not retyping it, and every agenda item has a place waiting for its outcome.
The minutes capture the outcome per item - the discussion in brief, the decision made, and any action raised. The discipline that makes minutes useful is separating those three. A decision is a conclusion the group is now committed to; write it plainly so nobody re-litigates it next month. An action is a task with an owner and a due date; the moment one is agreed, it needs to go somewhere it will be chased.
And that somewhere is a rolling action log - the link that changes everything.
The rolling action log is the difference-maker
Here is the shift. Instead of each meeting's actions living on that meeting's notes page - where they are forgotten the moment the next meeting starts a fresh page - every action from every meeting lands on one shared log that runs across all of them.
The effect is that an action promised three meetings ago and never done cannot hide. It is still sitting on the log, still open, still ageing, right next to the ones from yesterday. A single rolling list is what makes a series of meetings accountable rather than a sequence of amnesiac fresh starts.
And once actions are on one log, the log can do the tracking for you. Give each action a due date and a done date and let it work out its own status - Open, Overdue or Done - so nobody types it and nothing goes stale. Age each open action in days so the ones that have quietly run for weeks stand out. Roll up who is carrying the open load so a chair can see, at a glance, that one person is drowning in follow-ups. None of that is possible when actions are scattered across a dozen separate notes pages; all of it falls out naturally the moment they share a log.
Running the cycle
- Agenda before the meeting, always. Owner and time-box per item. It costs five minutes and saves the meeting from wandering.
- Capture the decision, not just the discussion. A decision written down once is a decision that is not re-opened next month.
- Log every action once, on the rolling log. Owner and due date, no exceptions. An action with neither is a wish.
- Open the action log first next time. The status and aging have already moved on their own, so you start the meeting by chasing what is overdue - not by reconstructing what you agreed.
A meeting is only worth its cost if the decisions and actions outlive it. Chain the agenda to the minutes to one rolling action log, and the follow-through stops depending on anyone's memory.
Good minutes are not about beautiful notes. They are about making sure the two things a meeting actually produces - the decisions and the actions - are still alive when you need them. Link the cycle, and the meeting finally starts paying for itself.
Minutes with a rolling action log built in
The agenda header carries through to the minutes, and every action agreed lands on one log that runs across all your meetings - status computes itself from the due and done dates, each action ages in days, and a summary shows who is carrying the open load.