Minutes are not the work

Article Coordination & decisions ~8 minutes

A polished PDF of minutes can still leave a programme stuck. If actions die in the appendix, the meeting was a performance. Beauty of formatting is not progress. Owned work is progress.

Teams often invest heavily in recording what was said and lightly in ensuring anything happens next. That imbalance is how coordination theatre grows: everyone can prove they attended; nobody can prove the interface moved.

What good practice looks like

Minutes support accountability — they are not a substitute for it.

In practice:

• Decisions are explicit — labelled clearly enough that a stranger knows what was settled.
• Actions become tracked work with owners and dates outside the PDF.
• Follow-up starts from the task list, not from rereading last month’s minutes.
• Attendance and agenda are part of the record when accountability matters.
• Updates to action status live where work lives — minutes may summarise, they should not be the only system.
• Recurring meetings open with open tasks, not with archaeology of old appendices.

Governance guides treat minutes as evidence of process. Site translation: evidence of talking is cheaper than evidence of doing — do not confuse them.

Where projects slip

• Action lists that nobody updates after the email goes out.
• “Noted” as a substitute for ownership.
• Duplicate actions across email and minutes that disagree.
• Owners named as companies or rooms (“structural to advise”) instead of people.
• Status theatre in the next meeting without any system showing intervening work.
• Minutes issued so late that the work stream already moved on a different verbal plan.

The cost is re-litigation. Topics return. Goodwill thins. Programme dates absorb the tax of meetings that produced text instead of tasks.

How Cynilo supports the practice

Cynilo meetings capture agenda, attendees, decisions, and minutes — and turn actions into tracked tasks so the work leaves the room with a trail.

How-tos cover the steps. Learn’s reminder sits beside Meetings that leave a trail of work: the PDF is the witness; the task is the work.

What good looks like in a week

On a job that separates minutes from work:

• Same-day action capture into tracked queues is normal.
• Next recurrence opens with open tasks, not with “remind me what we said.”
• PAs and PMs argue less about who owns a line because ownership is a field, not a paragraph.
• Closed tasks leave a short completion note the minutes can later summarise if needed.
• Late minutes never become the excuse for late action — tasks already existed.

The weekly test: from last coordination meeting, how many material actions exist as living tasks with owners? If the answer is “they’re in the PDF,” minutes are still pretending to be the system.

A short story from a weekly design coordination

A weekly design coordination issued elegant minutes within 48 hours — a point of pride. Actions numbered neatly in Appendix A. Three weeks running, Appendix A grew. Nobody owned a shared task board. When an IFC package slipped, the inquiry found decisions half-clear and actions that had never left the appendix.

They kept the minutes habit and added one rule: no action line without a task created before the meeting closes (or within an hour for dial-in clean-up). Appendix A stopped being a graveyard. The minutes got shorter because status lived elsewhere. Design movement improved without longer meetings.

Closing

Minutes matter as a record of who was present and what was decided. They fail when they try to be the work system. Decisions that bind the job need an even clearer home — next in the series.

Previous: Meetings that leave a trail of work