写作方法2020mcls.io编辑精选
培育书面沟通的文化
Encouraging a culture of written communication
导读
这篇文章讨论如何在团队里建立"用写作沟通"的文化：把信息尽量公开写下来，而不是靠私聊和口头传达。几位评论者进一步指出，写作文化还有两个常被忽略的前提——写作本身很难，以及必须同时培养"读"的文化；此外，读写能力在组织里常被当作权力的象征。对写作者来说，这些讨论能帮你理解：为什么好文档没人看，以及怎样让自己的写作真正被组织用起来。
可以直接用的写作要点
- 01
写下来的信息要发在公开渠道，而不是私聊或单发邮件，让未来的人也能检索到，否则等于把信息烧掉。
- 02
承认"写清楚"和"会写字"是两回事，刻意规避陈词滥调、含糊措辞和混乱结构，减少读者的理解成本。
- 03
只提倡写还不够，要同时创造读的场景（如会议开头集体静读十分钟），让读者意识到组织重视写作。
- 04
别把"没时间读"当成地位的展示，愿意认真读和写的人，才是在真正推动信息流通。
HN 评论精选
"不读不写"常被当作地位象征，这会扼杀写作文化。
要建立写作文化，得先消除一种现象：有人把"不读不写"当作权力的表达。在组织里，谁负责读材料、准备文档和演示，谁只需动嘴、被人汇报，往往就能看出两人的权力高低。人们喜欢把自己想象成能瞬间综合信息、实时发号施令的人，而"没时间读"成了身份象征；反过来，想让他人接受你的想法，你得先求见、扛住他即时的口头盘问。
nlawalker查看英文原文
I love this topic! A couple of unconnected thoughts on it: I think one thing that's needed to establish a culture of written communication is getting rid of any cultural elements that allow people to use the avoidance of reading and writing as an expression of power. You can frequently determine the balance of power between any two people in an organization by seeing which one has to read and prepare organized documents and presentations, and which one can simply speak and be spoken to. People want to paint pictures of themselves as being able to synthesize knowledge and ideas instantly, utter commands in real time and see them turned into action. In the other direction, they have no time for reading - you must request an audience with them and survive their real-time verbal sparring and probing questions to have your ideas received and considered. My other musing on this is that I've always wondered if there would be value in teams establishing an internship or low/mid level position for a technical writer to serve as a team librarian. "Easy to search" is good, but "search" itself is not sufficient for many situations - what you need is a person who can answer questions while taking context into account. If I was running a technical team, I'd love to experiment with hiring someone whose primary accountability is answering everyone else's questions, not generating output. In the same way that a good dev needs to organize their workspace and build tools/scripts to be successful, this person will end up organizing the team's information to better accomplish their job.
写作难是根本问题，"会写"与"写得清楚"差距巨大，且多数人带着坏习惯。
这类文章定期就会出现，正说明大多数团队写得不多或写得不好。但它们没触及根本原因：写作很难。为什么难？怎么才能写得更好？写作和写代码一样，产出和阅读都费时间，门槛高会劝退很多人。但与代码不同的是，几乎所有人都以为自己会写作，而"会写"和"写得清楚"差距巨大；也几乎所有人都被"教过"写作，可老师自己未必写得好、也未必有时间真教，于是留下大量坏习惯：依赖陈词滥调、用词含糊、结构混乱。陈词滥调让读者走神，含糊则拖长理解和反馈的周期。作者个人甚至认为，很多人永远学不好写作，组织不如指定专人来"抽取"信息、代为撰写。
blueyes查看英文原文
Posts like this are published with regularity. And like all things that must be said again and again ("stay off the grass", "we're in this together"), we can assume the opposite somehow true: Most teams do not write much or do not write well. What posts like this do not address is the root cause of the problem: Writing is hard. Why is it hard? And how can people learn to write better? Those would be worthy topics for a longer post, which are not addressed in this one. Writing, like code, takes time to produce and consume. Like a product with friction in its onboarding, this decreases the likelihood that many people will ever reach the goal of writing clearly. Unlike code, most people think they can write. But the difference between writing, and writing clearly, is large. Unlike code, almost everyone has been "taught" to write, often by teachers who themselves do not write well, or do not have time to truly teach them, so they have a lot of bad habits. These include a reliance on cliches, ambiguous diction, and poor organization. The first flaw makes the reader zone out, the second vastly increases the amount of time it takes to consume and respond to writing, since the feedback loop is delayed. Personally, I do not believe that many people will ever learn to write well; I also don't think it's worthwhile to make them try. I think that organizations, in order share information well internally, should make certain people "writers" who get extract information from their colleagues and convey it to the team. They would be like the secretary in a meeting, but more ubiquitous. This would be part of their job description and KPIs and compensation.
写作文化必须配套阅读文化，可用会议集体静读等机制保证有人读。
另一个相关挑战是：培养"读"的文化。我曾花很大力气写文档，结果发现极少有同事真的花时间读。有办法应对，最著名的是亚马逊的做法：每场会议开头先安静阅读十分钟，确保大家在同一页上。我想这其实是写作文化的一部分：一旦人们意识到组织重视写作，他们就会花时间去读。
simonw查看英文原文
Related challenge: encouraging a culture of reading. I've invested a great deal of effort in writing documents in the past only to realize that very few co-workers were taking the time to read what I'd written. There are workarounds for this. The most famous I can think of is the Amazon culture where each meeting starts with 10 minutes of quiet reading, to ensure everyone is on the same page. I imagine it's part of a writing culture though. Once people understand that an organization values writing, they'll take the time to read.
私聊等于销毁信息，公开渠道才能让未来的同事受益。
"尽可能鼓励大家把任何有意思的东西发到公共频道。注意是公共频道，不是私信，因为没必要就不打扰别人，我们只想让信息可获取。"说得太对了。每次你在 Slack 发私信、或只发给另一个人的邮件，都像把一张百元钞票点火烧掉。哪怕现在只有一个人需要这条信息，也不代表几年后某个新人不会因为搞不清状况，盯着屏幕六个月写不出一行代码。
Alex3917查看英文原文
> As much as possible, encourage people to post anything of interest to the public channels. Notice that I’m saying public channels, and not private messages, because we don’t ping anyone unless it’s necessary. We just want to make the information available. This. Every time you send a private message is Slack or send an email to just one other person, it's like taking a $100 bill and lighting it on fire. Just because only one other person needs that information right now doesn't mean that in a couple years some new hire won't spend six months just staring at their monitor and not writing code because they can't figure out wtf is going on.
同类还值得读
被低估的工程技能：把文章写好
Undervalued Engineering Skills: Writing Well
这篇文章讨论为什么“写得好”是被低估的工程能力，以及它如何在团队协作、系统设计和职业发展中持续带来回报。
写作方法2019 · 1,109 分 · 371 评4 条写作要点编辑精选每行只写一句话：让写作和修改都更轻松的排版法
Writing one sentence per line
这是 Derek Sivers 的一篇短文，主张写作时每行只放一个句子，而不是按段落排版。
写作方法2022 · 849 分 · 297 评4 条写作要点编辑精选书面沟通是远程工作的超级能力
Written communication is remote work super power
这篇文章讨论远程工作中书面沟通的价值，评论区则补充了异步与同步沟通的适用场景，并提醒读者：备忘录、结论先行、结构化命令格式等书面沟通传统早已有之。
写作方法2020 · 831 分 · 190 评4 条写作要点编辑精选如何写出有用的文字
How to Write Usefully
保罗·格雷厄姆在这篇文章里给"有用的写作"下了一个可操作的公式：有用≈重要×新颖×正确×清楚，任一项为零，整篇文章就等于零；他还主张敢下确定判断、删掉让自己心虚的句子。
写作方法2020 · 821 分 · 285 评4 条写作要点编辑精选如何写得更清楚、想得更清楚，并学会复杂材料（PDF）
How to write more clearly, think more clearly, and learn complex material [pdf]
这份 PDF 讨论如何把文章写清楚、把思路理清楚，并用写作来学习复杂材料。
写作方法2022 · 779 分 · 153 评4 条写作要点编辑精选