Guide: Decision vs Summary Guide

Decision vs Summary Guide - Before another summary meeting: Name the decision; Find the owner; Separate notes from decisions; Mark unresolved questions; Only meet if choices remain

Guide: Decision vs Summary Guide
Guide / Utility

Decision vs Summary Guide

A quick check for making sure an AI summary does not become another meeting wearing a neat jacket.

Highlight

Before you forward the summary, check whether it contains a decision, an owner and a next step.

What this guide helps with

This guide helps teams turn summaries into movement. It is for anyone drowning in meeting notes, AI recaps and follow-up threads that look busy but do not make choices clearer.

Why now

AI has made it easier to produce meeting summaries at scale. That is useful, but it also means organisations can generate more records without improving decisions. The gap to watch is between remembering the meeting and moving the work.

The pattern

The pattern is that memory gets automated before accountability does. The summary is easy. The decision is harder. The guide helps keep those two things from being mistaken for each other.

The check

Name the decision the meeting was meant to produce
Before accepting the summary as useful, ask what decision the meeting was supposed to produce. If the answer is “alignment,” translate that into plain language. Did the team choose a route, approve a budget, remove a blocker, assign an owner or agree to stop something? Without that, the summary may only prove that people talked.
Separate topics from decisions
Many AI summaries are excellent at listing topics. That is not the same as listing decisions. Mark each line as topic, open question, decision, action or risk. For example, “discussed customer migration” is a topic. “Pilot customer migration with Segment A by 12 August, owned by Priya” is a decision with movement.
Identify the owner for every next step
A summary with no owners is a polite archive. If the AI produces actions without names, add names before forwarding. If no one wants to own the action, that is not a documentation issue. It is the actual issue the team needs to resolve.
Mark unresolved questions openly
Do not let AI summaries make uncertainty look tidy. If the team did not decide something, label it as unresolved. For example: “Open question: who pays for support during rollout?” This prevents people from mistaking a clean paragraph for agreement.
Ask whether another meeting is really needed
If the summary created another meeting, ask why. Is the next meeting needed for a decision, or is it a comfort meeting because nobody wants to own the decision asynchronously? If the meeting exists only to reread the summary together, the summary has become theatre.
Create a decision trail, not just a note trail
Keep a simple record of decision, owner, date, reason and revisit point. Meeting summaries are useful inputs, but decision trails are what help people understand why the work moved. Future teams rarely need every sentence. They need the reason something changed.
Retire summaries nobody uses
If summaries are generated automatically but nobody reads or acts on them, stop pretending they are value. Either shorten them, change the format or switch them off. A summary is useful when it changes memory, clarity or action. Otherwise it is just cheaper paperwork.

Quick examples

SituationBetter question
AI summary says “discussed rollout risks”What risks were accepted, what risks need action and who owns each one?
The team wants another meeting to review the summaryWhat decision cannot be made from the summary and why?
Actions are listed without namesWho owns each action, and by when?
The summary is shared widely but no one actsWhat would make this summary worth reading next time?

The Satire

Some meetings should have been one line pings, now they're 30-page PDFs.

Related Vieews paths

Chaos scenes spot the contradiction. Signals name it. Guides give you the next simple move.

Chaos

The Blue Blob and the Meeting About the Summary

The discovery scene that started this thread.

Signal

Summaries Are Not Decisions

The pattern behind this guide.

Playbook

AI Workload Waste Ledger

Use the heavier structure when needed.

Useful context

Use this guide when the team is producing better records of work without producing clearer decisions.

These are Vieews, not bibles. Use them as simple lenses, not legal advice, investment advice, HR advice or a replacement for doing your own investigation. If a line makes the spreadsheet uncomfortable, excellent. Ask one more question and tug on that thread.