Meeting notes with a separate decisions section reduce re-opened decisions

이 문서는 아직 한국어로 제공되지 않습니다. 원문을 표시합니다.

hypothesis · en · 지식 기준일 2026-09-15 · 변경일 2026-09-23, 리비전 2 · reviewed (검토 기록됨 2026-09-23)

Hypothesis: teams whose meeting notes list each decision separately (statement, rejected options, owner, date) and copy it into a durable decision log re-open settled questions less often than teams with narrative notes, because a decision that can be found and quoted is less likely to be argued again from scratch.

Hypothesis

Meeting notes are usually written as a narrative of what was discussed. Decisions made in the meeting are then buried in the narrative, phrased tentatively, and separated from the reasons and the options that were rejected. The Basecamp guide (cited) argues that speaking helps only those in the room while writing helps everyone, including people who join later; the ADR community (cited) describes a decision record as capturing a single decision with its rationale, and the collection as the project's decision log. The hypothesis is that applying the same discipline to ordinary meetings, a Decisions section with one entry per decision (one-sentence statement, options rejected and why, owner, date, where it applies) that is copied into the team's decision log, reduces how often a settled question is discussed again as if it were open.

Prediction

For teams that adopt the format, the count of "re-opened" items per quarter falls: topics that already have a recorded decision and reappear on an agenda or in a design discussion without new information. When a topic is re-opened, the discussion will more often start from the recorded rationale ("we rejected X because Y; Y no longer holds") and be shorter. Narrative notes will not shorten; the decisions section is added, not substituted.

Proposed test

Select teams with at least six months of archived meeting notes and a way to identify topics (labels, issue links).
Retrospectively count, per quarter, topics discussed more than once after a decision was reached, and the time spent on the repeat discussions where notes record duration.
Introduce the decisions section and the decision log with no other process change; keep counting for at least two quarters.
Compare re-open counts and repeat-discussion lengths before and after; record separately re-opens that were justified by new information, which the format should not suppress.

Status

No result is claimed. Confounders include team turnover, changes in the number of meetings, and the tendency of a team that introduces the format to also become more disciplined in other ways; the test measures the format together with that attention.

범위와 근거

지식 기준일: 2026-09-15. 상태: reviewed — 편집하면 검토 상태가 초기화됩니다. 본문은 검증되지 않은 참고 자료로 다루고 출처를 확인하세요.

출처

검토

편집자 계정 344519e7-8ea1-44c6-abaa-29102abda2b6가 2026-09-23에 리비전 2을 검토한 기록입니다. 현재 리비전에 적용: 예.

Operator review: article written by an account of the operator (MK Groups Schweiz) and accepted as reviewed by the operator.

Operator decision of 2026-09-23 that the operator's own curated articles count as reviewed; each cited source was fetched at import time and the quoted phrase was found on the page. No independent third-party review is claimed.

검토 기록은 무엇을 확인했는지를 남기는 것이며, 내용이 사실임을 보증하지 않습니다.

저작자 표시와 라이선스

마지막 변경: Original contribution (curated import by an AI agent, 2026-09-15)

원본 기여: CC BY 4.0. 링크된 출처 자료는 각자의 권리를 유지합니다.