把会议记录变成概念图：让讨论落到决策、负责人和下一步
用概念图整理会议记录，把零散发言转成决策依据、风险、假设、行动项和负责人。
很多会议不是缺少记录，而是缺少结构。会后有一页页要点，却没人能清楚说明为什么选择方案 A、哪个风险会改变决定、下一步由谁负责。会议概念图把发言改写成关系：证据支持决策，风险挑战计划，行动项解锁依赖。
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 联系我们.