Work, with fewer headaches · 4-minute read
The meeting is over. The AI summary is immaculate. There are headings, bullet points and a confident paragraph about “strong alignment.”
By Thursday, nobody knows who was supposed to call the vendor.
But we do have a beautiful record of everyone being concerned about the vendor. Future historians will be delighted.
This is where AI meeting notes can become expensive stationery. They capture the conversation, everyone gets copied, and the actual work quietly waits for a volunteer.
Being on the email is not the same as owning the next step. Anyone who has ever been CC’d into a problem three departments away already knows this.
Separate the discussion from the agreement
A useful recap should make three things easy to find: decisions, actions and open questions. Those are different categories, even when the meeting enthusiastically mixes them together.
“We discussed changing vendors” records a topic. “We agreed to request a comparison quote” records a decision. “Priya will request that quote by Friday at noon” records an action—provided Priya actually agreed to it.
Consider this fictional exchange:
“Someone should check the renewal terms.”
“Yes, before we commit.”
“Great. Let’s keep moving.”
That is an unresolved task. It has no owner and no agreed deadline. A useful AI summary preserves those gaps. An overly helpful one might fill them in, creating a remarkably efficient way to give someone a job they never accepted.
Office politics already has a department for that.
Leave the blanks visible
For each action, capture the work, the owner, the agreed due date and what completion means. If a detail wasn’t settled, write “Not assigned” or “Not agreed.” You can’t fix a gap you’ve politely formatted out of existence.
Once the people involved confirm the details, an action might read:
Action: Request the vendor’s written renewal terms.
Owner: Priya.
Due: Friday, November 13, noon Pacific.
Done means: The vendor’s response is attached to the renewal task.
Status: Priya confirmed the assignment.
That’s a fictional example, but the distinction matters: attaching the terms is observable. “Circle back on vendor alignment” is a phrase that can live forever without inconveniencing anyone by becoming finished.
Put the confirmed action in the place your team actually tracks work. A task buried in a recap still needs a rescue operation.
Ask AI to show its work
Use an approved tool and meeting material you’re permitted to process. Follow your organization’s rules for recording, notice, access and retention. Then try:
Turn these meeting notes into Decisions, Actions and Open questions. Include only what the notes support. For each action, list the task, owner, agreed due date and completion condition. If any field is missing, label it Not assigned or Not agreed. Include a supporting quote or note reference. Do not infer agreement from silence or turn a suggestion into a commitment.
Review the output against the original notes. AI can confidently produce incorrect content; NIST calls this confabulation. An instruction to be careful does not eliminate that risk.
Before circulating the final recap, resolve unclear assignments with the people involved. Nobody should discover a new deadline because a summary decided they looked available.
Better still, spend the last two minutes of the meeting confirming who will do what, by when. Let AI help organize the record of that agreement.
Keep the lovely summary. Give the next step a person.
Otherwise, put it under glass. It’s a souvenir.
Try it at your next meeting: Before everyone leaves, ask, “Which of these actions still has no owner?” The awkward pause is considerably cheaper than another meeting.
Source: NIST, Generative Artificial Intelligence Profile (July 2024), section 2.2, on confabulation. The workflow and fictional examples above are the author’s.
