把會議筆記變成概念圖：讓討論落到決策、負責人與下一步
用概念圖整理會議內容，把零散發言改寫為決策依據、風險、假設、行動項與負責人。
許多會議留下了筆記，卻沒有留下共同理解。會後每個人都看過重點，但不一定知道決策依據、風險邊界和下一步責任。會議概念圖把內容整理成關係，讓證據、假設、風險與行動項各自有位置。
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.
產品團隊討論 onboarding 時，不只記下「簡化流程」。把「第 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 聯絡我們.