The Minutes Are Not the Meeting

Someone always volunteers: "I'll take the minutes."

An hour later a tidy document appears. Three bullets. Two action items. A polite "we discussed." The meeting has been turned into a story small enough to email.

That story is useful. It is also not the meeting.

What minutes actually are

Meeting minutes are a compression job. One person sits with half-finished notes, a fading memory of who said what, and a deadline to send something "official."

They keep:

• Decisions that felt settled
• Names that felt assigned
• Topics that fit on one page

They quietly drop:

• The objection that softened the decision
• The hedge that made the deadline soft
• The aside that explained why the number changed
• The exact wording people will later argue about

None of this requires bad faith. Compression always loses detail. The problem is treating the compressed version as if it were the original.

Why "I'll write it up" feels responsible

Writing minutes feels like leadership. You are closing the loop. You are creating a paper trail. The calendar invite can die; the doc lives.

What you are often doing:

• Replacing a multi-voice conversation with a single narrator
• Choosing which threads survive the cut
• Turning spoken ambiguity into written certainty because ambiguity looks unfinished

The team then treats that document as the source of truth. Tickets get filed from it. Follow-ups quote it. Disputes settle against it. The meeting itself — the messy, real one — evaporates.

The expensive version of "as discussed"

Without a transcript, organizations pay a quiet tax:

• Rewrites of rewrites. The minutes become the input to the follow-up email, which becomes the input to the ticket. Each layer drifts further from what was said.
• Ownership by authorship. The person who wrote the minutes becomes the unofficial historian. Challenging a line feels like challenging them.
• Fake consensus. Silence in the room becomes "we agreed" on the page because nobody wrote the dissent.
• Re-litigation. Two weeks later someone says, "That is not what we decided," and there is nothing to open except confidence.

A transcript does not fix politics. It removes the need to reconstruct speech from memory under pressure.

Minutes can be honest — after the words exist

This is not an argument against summaries. Summaries are how humans work. The order matters.

Wrong order: listen → invent a short story → treat the story as the record.

Better order: capture the words → skim the page → write a short summary that points back to the source.

When the meeting exists as text, minutes become an editorial layer instead of a substitute. You can quote the exact sentence. You can link the action item to the moment it was spoken. You can disagree with a paraphrase without accusing someone of lying — you can point at the line.

That is the difference between documentation and folklore.

What to keep instead of folklore

After a call, lecture, or recorded sync:

1. Get a transcript of the recording — searchable, pasteable, editable.
2. Highlight the decision sentences and the commitments, not the whole hour.
3. Write minutes from the highlights if your team still wants a one-pager.
4. File the transcript where the work lives: the ticket, the doc, the vault.

Playback is optional after that. The words are already on a page.

Soft close

If your team's "record" of important conversations is always one person's rewrite, you are not documenting meetings. You are publishing short stories about them.

To The Text turns recordings on your iPhone into clean text you can skim, quote, and hand to whoever still has to write the minutes — this time with the meeting still in the room.