
The four parts
- Decisions. One sentence each, stated as settled: "Idempotency is handled before retries are added."
- Open questions. Each with one owner, or it will stay open.
- Action items. Verb first, one owner, a date.
- Files. Where the work lands. This is the part most notes leave out.
A template you can copy
Payment retries, 20 November
Decisions
- Idempotency is handled before retries are added.
- We meet again on Friday.
Open questions
- Does the refunds endpoint have the same double-processing risk? (Sam)
Action items
- Save a unique key per order before calling the payment provider,
and reuse it on every retry. Dana, by Friday.
Files: src/payments/charge.ts, src/queue/consumer.tsWhy the files matter
"Fix retries" decays within a week, because nobody remembers what it meant. "src/queue/consumer.ts: add a retry with backoff" is half a ticket already. When the next meeting starts from notes like that, "what did we decide?" has an answer.
Write them in the last five minutes
Read the decisions and action items out loud before people leave. Someone will correct one of them, and that correction is the most valuable minute of the meeting. Notes written an hour later record what one person remembers.
Send one follow-up message
Five lines: the decisions and the action items. Leave the discussion out. People who were there do not need it, and people who were not will ask.