技术写作与文档2017meetnotes.co
撰写高效会议纪要的入门指南
A Starter's Guide to Writing Effective Meeting Notes
导读
这篇指南讲的是如何写出真正有用的会议笔记：重点不在逐字记录，而在于把讨论转化为清晰的行动项和决定。对写作者来说，它提醒我们“记录”是一种有对象的写作——读者是未来的自己和同事，措辞准确性、责任归属和可追溯性都比文采重要。
可以直接用的写作要点
- 01
会议笔记的落点应是行动项：结尾列出“谁、做什么、何时前完成”，并当场问一句“有遗漏吗”。
- 02
把讨论收敛成“决定了什么、待办什么”，而不是复述谁说了什么；没有导向行动的讨论等于没开。
- 03
引用他人观点时，先单独把相关段落发给本人确认措辞，再对外分发，避免“这不是我的意思”造成的返工与矛盾。
- 04
笔记会被长期保存、被他人引用甚至用于法律场景，因此日期、发言人、结论要写准，避免模糊表述。
HN 评论精选
会议笔记的核心产物是行动项，并在结尾当场确认。
会议唯一重要的是行动项。做咨询时，议程写的是 X，但往往大半时间都在谈突发的 Y（这常常正是开会的原因）。议程仍要有，但客户最认可的是我把行动项敲定下来。这也让收尾变得容易：临近结束时说“时间不多了，我记录的行动项是 x、y、z，有遗漏吗？”——光讨论而不落到行动，毫无意义。
peterlk查看英文原文
I'm not really sure why this is on the front page of HN, but I'll add my thoughts because it is. > To make your meetings successful, follow up on action items This is it. Back when I was doing consulting, the only thing that mattered when I came out of the meeting was action items. Often, even if the agenda is X, something unexpected will have happened (often the reason why the meeting was called), and you'll actually spend the bulk of the time talking about Y. You should still have an agenda, but I found that clients appreciated most when I drilled at the action items. This also makes it really easy to wrap up meetings. When you get toward the end, you say something like: "We're starting to get short on time, here are the action items that I have from this meeting; x, y, z. Did I miss anything?" Talking about stuff is pointless unless it leads to some action.
记笔记能积累影响力与记忆，但引用他人观点前要先经本人核对。
Richard Branson 在书里强调详细记录会议，认为这个习惯让他受益终身。这确实是被低估的习惯，对新人尤其如此：你会成为信息流的守门人；记录的过程迫使你专注，也加深记忆，便于日后构思；它还给你影响未来决策的依据——“根据我的笔记，某月某日我们说要做 X，所以现在应该做 Y”。另外建议：把笔记中涉及某人观点的部分先单独发给本人核对，“我在整理会议记录，关于 Y 我是这样记你说的，能否看一下是否准确？”——否则一句“这不是我说的”或更常见的“我不是这个意思”，就会制造本可避免的矛盾。
pitt1980查看英文原文
In Richard Branson's book he makes a big deal about keeping detailed notes of meetings, and how useful he's found the practice to be over his career its really probably a very underrated habit, especially as a new, low on the totem pole person it probably makes you a very useful gatekeeper of the information flow the process of doing it probably reinforces the information flow into your brain for useful future brainstorming (it forces you to pay attention) also it gives you the basis for which you can influence future decisions "On (so and so date), according to my notes we said we wanted to do X, so now we should do Y" ----------- a suggestion, run how people's ideas are presented in your notes to them directly, before you distributed them to the wider audience "I'm trying to get the meeting notes together, this is how I have what you said about Y, do you mind looking at to make sure it accurately captures what you were saying?" "That's not what I said" or, more likely, "That's not what I meant" is a good way to create dysfunction where none needs to exist
记笔记的位置本身也是一种可见的职业姿态。
最近一条很棒的推文还提到：坐在房间最前面记笔记。这不只是为了避开刻板印象的陷阱，对任何人都是一条有用的职业建议。
Harkins查看英文原文
And, as an excellent Twitter thread recently noted: take notes at the front of the room. https://twitter.com/Delafina777/status/846086667790311424 This is not solely valuable for avoiding stereotype traps, it's a useful career tip for anybody.
会议纪要可能成为法律文件，措辞要经得起日后被引用。
律师在诉讼中常会索取相关会议、电话的纪要作为证据。几年前我写过几条记笔记的习惯，是“你的律师会感谢你”的那种（当然是自引）。
dctoedt查看英文原文
Lawyers often seek to get copies of minutes of relevant meetings, phone calls, etc., for use in litigation. A few years ago I posted some note-taking tips that your lawyer will love you for: http://www.oncontracts.com/note-taking-in-meetings-and-phone-calls-three-easy-habits-your-lawyer-will-love/ (self-cite, obviously).
同类还值得读
编写更好文档的框架
A Framework for Writing Better Documentation
这是 Divio 的文档写作框架，把技术文档按「读者的目标」分成四类：教程（学习导向）、操作指南（问题导向）、参考（信息导向）、解释（理解导向）。
技术写作与文档2021 · 637 分 · 76 评4 条写作要点编辑精选写好一份设计文档
Writing a good design document
这篇 HN 帖子标题为《Writing a good design document》，主题是如何写好一份设计文档；对写作者来说，它值得作为技术写作和结构化说明文的参照。
技术写作与文档2025 · 581 分 · 147 评3 条写作要点编辑精选技术写作课程
Technical Writing Courses
这是 Google 官方免费技术写作课程（两门），讲受众定义、主动语态、短句、文档结构等基础方法。
技术写作与文档2020 · 571 分 · 73 评4 条写作要点编辑精选写出更好的错误信息
Write better error messages
这篇帖子讨论如何写出更好的错误信息，评论补充了开发者场景下的具体做法和真实反面案例。
技术写作与文档2022 · 566 分 · 253 评4 条写作要点编辑精选写一本技术书的经济账
The Economics of Writing a Technical Book
一位技术书作者拆解写书的真实经济账：版税收入往往远低于投入的时间成本。
技术写作与文档2018 · 519 分 · 149 评4 条写作要点编辑精选