회의 메모를 개념도로 바꾸기: 토론을 결정, 담당자, 다음 단계로 정리하는 방법
회의 내용을 결정 근거, 위험, 가정, 실행 항목, 담당자로 구조화하는 실무형 개념도 작성법.
회의 기록은 많지만 공동 이해는 부족한 경우가 많습니다. 무엇을 결정했는지보다 왜 그렇게 결정했는지, 어떤 위험이 남았는지, 누가 다음 행동을 맡는지가 더 중요합니다. 회의 개념도는 발언을 결정, 근거, 가정, 위험, 실행 항목의 관계로 바꿉니다.
Authority references: concept map, meeting minutes, cognitive load.
요약
- D = decision, A = action, R = risk, Q = open question, E = evidence.
- First draft target: within 24 hours.
- Practical size: 12 to 25 nodes for a 30 to 60 minute meeting.
- Useful link verbs: supports, blocks, requires, validates, changes, owns.
“A meeting map is useful when a person who missed the discussion can see the decision, the evidence, and the next owner in 5 minutes.”
— Hommer Zhao, Knowledge Systems Researcher
Workflow
- Capture raw notes first; do not polish layout during the meeting.
- Choose one focus question, such as: What did we decide and why?
- Keep only decisions, evidence, risks, assumptions, actions, and unresolved questions.
- Label every connection with a verb. Avoid vague lines that only mean related.
- Separate facts from assumptions so follow-up work is clear.
- Add one owner and one date to each action node.
온보딩 개선 회의라면 “단계를 줄인다”가 아니라 6단계 이후 이탈, 지원 티켓 18% 증가, 영업팀의 데이터 요구를 하나의 결정 노드에 연결합니다.
| Node | Review question | Common failure | Fast correction |
|---|---|---|---|
| Decision | What changed after the meeting? | choice without reason | connect 2 evidence nodes |
| Evidence | What supports the choice? | opinion treated as fact | add source or metric |
| Risk | What could change the plan? | no owner | create mitigation action |
| Assumption | What still needs testing? | hidden belief | define a simple test |
| Action | Who does what by when? | task without dependency | connect to decision or risk |
“When a meeting map grows past 30 nodes, split it into a decision map and an execution map.”
— Hommer Zhao, Knowledge Systems Researcher
Templates
Decision map: options, evidence, selected path, risks, and owners.
Risk map: known facts, assumptions, tests, mitigations, and review date.
Stakeholder map: goals, concerns, constraints, trade-offs, agreements, and conflicts.
FAQ
When should the map be created?
Within 24 hours. After 48 hours, small context details become harder to recover.
How many nodes are enough?
Use 12 to 25 nodes for a normal meeting. Split the map after about 30 nodes.
Does this replace formal minutes?
No. Minutes preserve the record; the concept map explains relationships among decisions, evidence, risks, and actions.
Which relationship labels work best?
Use short verbs: supports, blocks, requires, challenges, validates, owns, and changes metric.
How should disagreement be handled?
Create a conflict node, connect it to the affected decision, and assign one person to bring evidence before the next meeting.
“An action is clear only when the map shows which decision it unlocks or which risk it reduces.”
— Hommer Zhao, Knowledge Systems Researcher
Try one meeting this week in the 편집기. For a team, class, or research workflow, use 문의하기.