It is Thursday, 6 pm in Lisbon. Aunt Edna has ordered a coffee. Across the table, a developer proudly announces that AI has summarised the meeting in ten points. Edna asks what they decided. The answer arrives without any help from a language model: another meeting.
This week's fictional scene is about a familiar distinction: recording a conversation is not the same as deciding what happens next. Automatic summaries can be useful. They cannot supply an agreement that nobody actually reached.
A real practice behind the joke
GitLab's public remote-work handbook recommends a shared agenda with a clear desired outcome, live documentation and captured action items. It also encourages cancelling recurring meetings whose purpose has been served. This is a documented operating practice, not scientific proof that every meeting should disappear.
Some conversations need synchronous attention: resolving an ambiguous problem, handling a sensitive disagreement or coordinating an urgent response. Others only need a clear question and enough context for someone to answer. The aim is to choose a useful format, not to turn “no meetings” into another rule nobody can explain.
Replace the vague invitation with a decision
Compare “Let's align on the import feature” with “Should the first release accept CSV only, or also XLSX? We need a decision because it changes the validation work.” The second invitation tells people what preparation matters and what the conversation should produce.
Before scheduling, write the question, the options and the information still missing. If a short written exchange resolves it, keep the decision where the work is tracked. If discussion is needed, bring the same document into the meeting. A video call should not require starting the context from zero.
A summary is a draft until someone checks it
When using AI notes, distinguish a suggestion from an accepted commitment. “We could test this on Friday” must not silently become “The team agreed to launch on Friday.” Check names, dates, conditions and unresolved objections against the actual discussion before distributing the result as a decision record.
Use an approved tool for the information involved, explain any recording to participants and follow the applicable organisational rules. A convenient transcription workflow is not a reason to circulate confidential details unnecessarily.
Our practical closing check has three questions: what was decided, who owns the next action and by when? Add a link to the evidence or task. If no decision was reached, say so and identify the missing information. A truthful “not decided” is more useful than a polished imaginary consensus.
Try it at the next meeting
- Write one sentence describing the desired outcome before inviting anyone.
- Separate context, open questions, decisions and actions in the notes.
- Ask each action owner to confirm the responsibility and date.
- Cancel the next recurring slot if it no longer has a purpose.
Edna does not object to technology. She objects to spending an hour producing a document that requires another hour to discover what it means. The coffee, at least, has a clear acceptance criterion: it arrives hot.
The comic
Original fictional satire, illustrated with AI and editorially reviewed. The characters do not depict a real client, employee or meeting.
Panel 1 — Developer: “AI summed up the meeting in ten points!” Panel 2 — Edna: “And what did you decide?” Developer: “To schedule another meeting.” Panel 3 — Developer: “But now we have a very thorough summary.” Panel 4 — Edna: “Then summarise this: who does what, by when?”
Source and next coffee
GitLab Handbook: All-Remote Meetings, consulted 17 October 2026. The examples and checklist are our editorial application, not claims about a new event on publication day. Happy Hour with Aunt Edna returns on Thursdays at 6 pm, Europe/Lisbon time.
