Day 9: Turn Meetings Into Momentum

The Concept

Meetings create value through decisions, shared understanding, and coordinated action. Notes alone do not create any of those things. A follow-up has to make the important parts easy to find and easy to act on.

AI is well suited to the first pass because meeting notes are often messy. It can group repeated points, extract possible actions, and create different versions for the team and leadership. It can also make a dangerous mistake: turning a possibility into a decision or assigning ownership that was never agreed.

Preserve the difference

Keep these categories separate: decisions, actions, discussion, risks, and questions. “We could ask the vendor” is not the same as “the project manager will ask the vendor by Friday.” A clear summary protects the team from false agreement.

Review before sending

Check names, dates, commitments, and words such as approved, agreed, blocked, and complete. If the notes are ambiguous, write "needs confirmation" rather than choosing the most plausible interpretation. The fastest summary is not the one that creates a correction thread afterward.

Example: separate a decision from a discussion

Imagine the notes say: “The team prefers the shorter rollout. Operations will check whether the training team can support it. We may be able to start in September.” An automated summary might incorrectly write: “The team agreed to launch the shorter rollout in September.” That sentence sounds clear, but it invents both a decision and a date.

A reliable follow-up would say:

• Discussion: the shorter rollout was viewed positively.
• Open question: can the training team support the proposed approach?
• Action: operations to confirm training capacity; owner and due date not specified.
• Decision status: no launch date agreed.

This may look less polished, but it is more useful. It tells the team exactly what still needs to happen and avoids creating false confidence in the project record.

Use two passes

In the first pass, ask AI to extract possible decisions, actions, risks, and questions without rewriting them too confidently. In the second pass, compare each item with the source notes. Mark it as confirmed, inferred, unclear, or missing. Only confirmed information should appear as a commitment in the final update.

If the notes come from a transcript, review names and speaker attribution carefully. Transcription errors can change the meaning of a commitment. Remove unnecessary personal or sensitive information before sending notes to an external model, and follow the organisation's rules for meeting data.

Write for different readers

The project team needs actions and unresolved questions. A sponsor may need decisions, changes to outcome or timing, and requests for help. A wider stakeholder group may need a short status note without every detail of the conversation. One source record can support these versions, but do not let the short version become the only record.

Close the loop

Give attendees a correction window, then update the action tracker and decision log. At the next meeting, begin with overdue actions and unresolved decisions rather than rereading the previous summary. A meeting follow-up creates momentum only when it changes what the team does next.

A final check before sharing

Read the summary as someone who was not in the room. Can they distinguish what happened, what was decided, what remains open, and who acts next? If not, simplify the structure and label uncertainty plainly. Clear records reduce repeat conversations and protect trust.

Make the record searchable

Use consistent labels for decisions, actions, risks, and questions. Include the project name, meeting date, and a link to the source notes where appropriate. Consistency helps the team find the history later and makes it easier to ask AI for a focused summary without losing context.

If an action has no owner or date, do not quietly fill the gap. Put it in an “owner to confirm” section and make that confirmation the next action. A visible gap creates a better conversation than an invented commitment that fails silently.

Keep the record short enough that people will read it, but complete enough that the next meeting can begin with progress rather than reconstruction.

Where the team uses a decision log or task tracker, link the follow-up to those records. The email can start the conversation, but the shared project record should carry the commitment forward.

If the meeting produced no decision, say so. “No decision made” is a valid project outcome when it is paired with the question, owner, and date that will move the issue forward. This keeps the record honest and gives the next conversation a clear starting point.

Use this today

Send a short follow-up with three priorities at the top: decisions, actions, and questions. Put background discussion below them. Invite corrections by a specific time, then update the project record once the window closes.

Remember this

• A meeting summary should make action easier, not simply make notes shorter.
• Never let fluent wording create a decision that the team did not make.
• Ownership and dates must come from the meeting or be marked as missing.