约9分钟阅读
专业的写作,是能赢得信任的写作。它告诉读者,你有能力、考虑周到,并且能掌控自己要传达的信息。无论你是在给客户写电子邮件、起草季度报告,还是为一项新举措撰写提案,你文字的语气都会影响别人怎样看待你和你的想法。有力的职场语气并不意味着生硬、刻板或冷冰冰的语言。它意味着清楚、自信、适合商务语境的写作。
本节探讨职场写作区别于随意写作和学术写作的核心特征,并解释怎样表现出自信,又不至于流于自大。
在考察具体的技巧之前,先理解职场语气想要实现什么会很有帮助。在商务语境中,写作服务于实际的目标:
职场语气同时支撑着所有这些目标。当你的文字听起来很专业时,人们更有可能认真对待你的想法、及时作出回应,并把你看作值得合作的人。
职场写作唯一最重要的品质就是清晰。每个句子都应该在读第一遍时就传达出它的意思。如果读者必须回过头去重读一个句子才能理解它,这段文字就没有完成它的首要任务。
清晰来自:
不清楚: With regard to the situation that was discussed at the meeting that took place last Thursday, it would be appreciated if the relevant parties could provide their input on the matter at their earliest convenience.
清楚: Please share your feedback on the staffing proposal we discussed last Thursday by end of day Friday.
不清楚的版本用了 39 个词,来说清楚的版本用 18 个词就说完的内容。它把真正的请求藏在了含糊的语言背后("the situation"、"the relevant parties"、"the matter")。职场写作会剥掉这些填充物,直截了当地传达信息。
职场写作应该听起来胸有成竹。你在呈现信息、提出建议或请求对方采取行动——所有这些都要求读者信任你的判断。模糊限制用得太多,会削弱这种信任。
不过,自信必须与自大区分开来。过度自信的文字会无视其他视角,不拿出论据就提出主张,还会居高临下地对读者说话。目标是落在中间:坚定而又尊重对方。
信心不足(模糊限制太多): I was just wondering if maybe we could possibly consider looking into the option of perhaps restructuring the team, if that might be something people would be open to.
过度自信(不屑一顾): Obviously, the team structure is broken and anyone who has been paying attention can see that. We need to restructure immediately.
自信(平衡): Based on the productivity data from Q3, I recommend restructuring the marketing team into two focused units. This would allow each group to specialize and reduce the overlap we have been seeing in project assignments.
注意自信的版本做了什么:它援引了论据("productivity data from Q3"),提出了明确的建议("I recommend"),解释了理由("allow each group to specialize"),并且在承认问题的同时没有指责任何人。
要避免的信心不足的标志:
要避免的过度自信的标志:
职场写作是直接的,但绝不粗鲁。它说出需要说的话,不作不必要的软化,但也会考虑读者的视角和感受。
太间接: It has come to our attention that there may have been some instances where the guidelines were not entirely followed in every case, and we wanted to take this opportunity to gently remind everyone of the importance of adherence to established procedures.
太生硬: You are not following the guidelines. Follow them or there will be consequences.
得体的直接: We have noticed some inconsistencies in how the submission guidelines are being applied. To ensure quality and fairness, please review the updated guidelines document (attached) and apply them to all submissions going forward. If you have questions about any specific guideline, I am happy to discuss.
得体而直接的版本清楚地说明了问题,给出了具体的行动,并提供了支持——既不咄咄逼人,也不被动攻击。
职场语气存在于一条光谱上。就一件日常事务写给共事多年的同事的消息,可以比写给董事会的提案更亲切、更随意。关键在于让你的正式程度与情境相匹配。
提高正式程度的因素:
降低正式程度的因素(同时保持专业):
即使在最随意的时候,职场写作也要避免俚语、短信用语、过多的感叹号和过于情绪化的语言。即使在最正式的时候,它也要避免官僚化的行话、不必要的复杂句子,以及听起来像是由委员会写出来的语言。
职场写作把读者放在第一位。不要专注于你想说什么,而要专注于读者需要知道什么。这意味着:
以作者为中心: I have spent the last three weeks analyzing the data from Q3, and after going through all the reports and speaking with team leads, I have put together a comprehensive summary that I think covers all the key points.
以读者为中心: Attached is the Q3 analysis summary. Key finding: customer retention dropped 12% in the enterprise segment. I recommend we discuss this at Thursday's leadership meeting. The full data and methodology are in Appendix B if you want the details.
以读者为中心的版本立刻告诉读者:这份文件是什么、关键的结论是什么、建议采取什么行动,以及到哪里可以找到更多细节。以作者为中心的版本谈的是作者的工作过程,而这是读者不需要知道的。
职场写作会小心地处理情绪。它承认那些可能令人沮丧、失望或兴奋的情况,但不让情绪主导语言。在传达坏消息、处理冲突或回应批评时,这一点尤其重要。
情绪激动: I am extremely frustrated that the deadline was missed again. This is completely unacceptable and honestly I do not understand why this keeps happening.
情绪中立: The March 15 deadline was not met, which is the third consecutive delay on this project. I would like to schedule a meeting to identify the root causes and develop a plan to get back on track.
中立的版本以同样的严肃态度处理了同一个问题,但它关注的是事实和解决办法,而不是感受。这种做法更有可能换来建设性的回应。
情绪中立并不意味着冷漠。你可以在职场写作中表达感谢、热情和关切——关键在于适度。一封电子邮件里用一个感叹号没有问题。用五个,就显得不够沉稳了。
职场写作和学术写作有一些共同的品质(清晰、以论据为基础的推理、客观),但它们在一些重要的方面有所不同:
| 特征 | 学术写作 | 职场写作 |
|---|---|---|
| 首要目标 | 推进知识 | 推动决策和行动 |
| 第一人称 | 常常避免 | 普遍使用(尤其是 "we") |
| 句子长度 | 较长,较复杂 | 较短,较直接 |
| 模糊限制 | 大量使用(may, might, suggests) | 适度使用(recommend, propose) |
| 行话 | 学科专用,理所当然 | 行业专用,谨慎使用 |
| 语气 | 客观,审慎 | 自信,以行动为导向 |
| 结构 | 引言—正文—结论 | 先说关键信息,再说细节 |
| 读者 | 专业人士 | 混合(高管、客户、团队) |
如果你习惯了学术写作,那么转向职场语境时最主要的调整是:更直接,先说结论,为推动行动而写,而不是为展示学识而写。
归根结底,职场语气关乎可信度。你的文字告诉读者,你是不是一个思维清楚、沟通有效、可以托付责任的人。每一封电子邮件、每一份报告、每一次演讲展示,都在塑造这种印象。
好消息是,职场语气是一种技能,而不是一种性格特质。你不需要天生就正式,也不需要天生就自信。你只需要在每一篇文字中始终如一地运用这些原则——清晰、自信、直接、以读者为中心、控制情绪。接下来的几节将向你展示,怎样在不同的职场语境中运用这些原则。
约10分钟阅读
职场写作并不是在哪里听起来都一样。你写给团队成员的电子邮件所用的语气,与你在客户提案中所用的语气不同,而后者又与董事会演讲展示中的语气不同。娴熟的职场人士会调整语气以适应语境,同时保持那些定义了职场沟通的核心品质——清晰、自信和尊重。
本节考察职场语气怎样在最常见的几种商务写作形式之间调整,并解释怎样为每一种形式校准你的正式程度。
与一般的写作相比,职场写作所处的正式程度范围更窄。你永远不会是在给朋友发短信(第 1 级),也不会是在起草法律条文(第 5 级)。相反,在五级量表上,职场语境通常落在第 2.5 级到第 4 级之间。
| 级别 | 职场语境 | 例子 |
|---|---|---|
| 2.5 | 随意的职场沟通 | 发给团队的 Slack 消息、简短的内部进度更新 |
| 3 | 标准的职场沟通 | 大多数商务电子邮件、会议议程、内部报告 |
| 3.5 | 较高规格的职场沟通 | 面向客户的电子邮件、对外的演讲展示、新闻稿 |
| 4 | 正式的职场沟通 | 给高管的提案、与董事会的沟通、合同、正式的规章制度 |
难点不在于在「正式」和「非正式」之间作选择——而在于在这条光谱上找到适合每种情境的那个确切的点。
电子邮件是最常见的职场写作形式,它几乎横跨了职场正式程度的整个范围。
写给经常一起工作的同事的邮件,可以相对随意,同时仍然保持专业。对一个每天坐在你旁边的人,你不需要写 "Dear Ms. Chen"。
例子——日常进度更新: *Hi team,
Quick update on the website redesign: the design team delivered the homepage mockups today. They look solid. I have a few minor notes, but nothing that should delay the timeline.
I will share the mockups in tomorrow's standup. If you want a preview, they are in the shared drive under Projects > Website > V3 Mockups.
Thanks, Alex*
注意这里的语气:友好而又聚焦。它使用第一人称、简短的段落和交谈式的风格。没有不必要的正式,但也没有俚语、没有满屏的表情符号,关键信息也毫不含糊。
写给客户的邮件需要更加用心。你代表的是你的机构,语气会影响客户对你的专业程度和可靠程度的看法。
例子——项目进展更新: *Dear Ms. Nakamura,
Thank you for your patience as we finalized the Phase 2 deliverables. I am pleased to confirm that all items are now complete and ready for your review.
Attached you will find:
I would welcome the opportunity to walk you through the deliverables at your convenience. Would Thursday or Friday afternoon work for a 30-minute call?
Please do not hesitate to reach out if you have any questions in the meantime.
Best regards, Alex Chen Senior Project Manager*
这封邮件比法律文件更亲切,但比内部消息更有条理。它向客户致意,用项目符号组织信息,提出了一个具体的下一步,并以职务头衔落款。
在传达坏消息、处理投诉或应对冲突时,语气需要格外谨慎:有同理心但以事实为依据,直接但不咄咄逼人。
例子——处理一次错过的截止日期: *Dear Mr. Rodriguez,
I want to acknowledge that we did not meet the April 1 delivery date for the market research report. I understand that this delay affects your planning timeline, and I take full responsibility for the lapse.
The delay was caused by unexpected difficulties in securing interview participants for the qualitative research component. We have since resolved this issue and have completed all remaining interviews.
The revised delivery date is April 8. To ensure we meet this date, I have assigned an additional analyst to the project and will personally oversee the final review.
I appreciate your understanding and am committed to delivering a report that meets the high standard you expect.
Sincerely, Alex Chen*
这封邮件有几处做得很好:它立刻承认了问题(没有把坏消息藏起来),承担了责任而不找借口,简要地解释了原因,提供了具体的解决办法,并重申了承诺。
与电子邮件相比,报告和正式文件需要更有条理、更有权威的语气。它们常常会被多类读者阅读,还可能成为永久记录的一部分。
例子——月度业绩总结(开头段): March performance exceeded projections in three of four key metrics. Revenue reached $2.4M, surpassing the target of $2.1M by 14%. Customer acquisition increased by 8% month-over-month, and the average deal size grew from $18,500 to $21,200. The one area of concern is customer support response time, which averaged 4.2 hours against a target of 2 hours. Recommendations for addressing this gap are outlined in Section 3.
这一段先说关键发现,精确地呈现数据,承认不利的一点而不加掩饰,并把读者引向相关的部分。语气自信,以数据为依据。
面向客户、监管机构或公众的报告,需要更正式的语气,也需要更加注重精确。
例子——一份咨询报告的执行摘要: This report presents the findings of a six-week operational assessment of Meridian Healthcare's patient intake process. The assessment identified three primary areas for improvement: intake form digitization, staff training on the updated EHR system, and patient communication workflows. Implementation of the recommended changes is projected to reduce average intake time from 42 minutes to 18 minutes and improve patient satisfaction scores by an estimated 15-20%. A phased implementation plan with timeline and resource requirements is provided in Section 5.
提案是说服性的文件。它的语气必须在权威与热情之间取得平衡——你希望听起来能干,并对这个机会充满热情,但又不显得急不可耐或夸大其词。
例子——提议引入一个新工具: *I recommend that we adopt ProjectFlow as our project management platform, replacing the current spreadsheet-based tracking system.
The primary benefits are:
The annual cost is $12,000 for our team of 15. Based on the time our project managers currently spend on manual tracking (estimated at 6 hours per week across the team), the tool would pay for itself within four months.
I would be happy to arrange a demo for the leadership team if there is interest in moving forward.*
这份提案直接、有数据支撑、以行动为导向。它先说明建议,用论据呈现好处,主动交代成本,并提出了一个具体的下一步。
面向客户的提案需要更加精雕细琢的语气。它们需要展现出对客户需求的理解,建立可信度,并把你的方案呈现为最合适的选择。
例子——一份客户提案的开头: *Thank you for the opportunity to submit this proposal in response to your request for a comprehensive digital marketing strategy. We have reviewed your current positioning, competitive landscape, and growth objectives, and we believe there is a significant opportunity to strengthen Greenleaf's brand presence in the sustainable products market.
Our proposed approach focuses on three pillars: targeted content marketing to establish thought leadership, a redesigned social media strategy to increase engagement with environmentally conscious consumers, and a data-driven paid media campaign to drive measurable growth in online sales. Each pillar is detailed in the sections that follow, along with projected outcomes, timeline, and investment requirements.*
为演讲展示准备的书面内容(幻灯片文字、演讲者备注),需要采用与文件不同的写法。幻灯片是视觉辅助工具,不是文章。
幻灯片文字应该简洁、便于快速浏览,并且为产生冲击力而组织:
文字太多(读起来像一份报告): Our customer satisfaction survey, which was conducted in February and received responses from 1,247 customers across all segments, revealed that overall satisfaction has increased from 72% to 84% year-over-year, with the largest gains in the enterprise segment, which saw a 19-point increase.
有效的幻灯片文字: *Customer Satisfaction: 72% to 84% (YoY)
细节和细微之处属于你口头的讲解或一份单独的文件——而不属于幻灯片。
演讲者备注可以比幻灯片本身稍微不那么正式,因为它们是用来引导你的口头表达的:
Talk about the enterprise number first — that is the headline. Mention that we attribute the jump to the dedicated account management program we launched in Q3. Pause here and ask if there are questions before moving to the segment breakdown.
在决定把你的正式程度旋钮调到哪里时,考虑下面这些信号:
拿不准的时候,宁可稍微偏正式一些。随着时间的推移逐渐变得不那么正式、慢慢建立起融洽的关系,要比从一个太随意的第一印象中挽回局面容易。收到一封过于正式的邮件的客户,可能会觉得你周到而有礼貌。收到一封过于随意的邮件的客户,则可能会怀疑你是否够专业。
人们对职场语气的期待因文化而异。下面是一些需要留意的重要差异:
给来自不同文化背景的人写信时,最稳妥的策略是:在了解对方的沟通偏好之前,保持礼貌、清楚、适度正式。
和任何形式的写作一样,一致性很重要。如果你的邮件以 "Dear Ms. Patel" 开头,却以 "Cheers!" 结尾,你就造成了语气上的错位。如果一份报告开头以数据为依据、精确严谨,到了第五页却滑向了随意的评论,这就会损害这份文件的权威性。
在开头确定你的正式程度,并在全文中保持下去。如果你不确定某个短语是否符合你已经确立的语气,就把它放在前后句子的语境中读一读。如果它明显比周围更正式或更不正式,显得格格不入,就调整它。
约9分钟阅读
培养职场语感的最好方法,是研读真实的例子。本节呈现一组改写前后的对比,涵盖职场写作中最常见的语气错误。每个例子都会指出具体的问题,展示修改后的版本,并解释修改后的版本为什么更好。
职场写作中最常见的语气问题,是模糊限制过多——用了太多的限定语和缓和语,以至于信息听起来犹豫不决、满怀歉意,或者缺乏权威。
改写前: Sorry to bother you with this, but I was just wondering if maybe we could possibly discuss the timeline for the Henderson project? I know you're really busy, but if you get a chance, it would be great if we could maybe touch base at some point. No worries if you can't though!
改写后: I would like to discuss the Henderson project timeline with you. Could we schedule 15 minutes this week? Tuesday or Wednesday afternoon would work well on my end.
改变了什么: 修改后的版本去掉了五处模糊限制("sorry to bother you"、"just wondering"、"maybe"、"possibly"、"no worries if you can't"),删掉了不必要的道歉,并用一个具体的请求(15 分钟,周二或周三)取代了含糊的语言("touch base at some point")。语气从怯懦变成了礼貌而自信。
改写前: This might not be the best idea, and I could be totally wrong about this, but I was thinking that maybe we should consider looking at our pricing structure? I'm not an expert or anything, but it seems like some of our competitors are doing things differently. I don't know, it was just a thought.
改写后: I recommend we review our pricing structure. A preliminary analysis of three key competitors shows that their entry-level pricing is 15-20% below ours, while their premium tiers offer more flexible options. I have outlined a comparison in the attached document and would welcome a discussion about whether adjustments are warranted.
改变了什么: 原文在读者还没读到实质内容之前,就四次拆了自己想法的台。修改后的版本以一个明确的建议开头,用数据来支撑它,并邀请对方讨论——全程没有先发制人的道歉。
改写前: I hope it's okay to share some thoughts on the Q2 marketing plan. I know the team has already put a lot of work into it, and I don't want to step on anyone's toes, but I had a few small observations that I thought might possibly be worth mentioning, if that's alright.
改写后: *I have reviewed the Q2 marketing plan and have three observations that I believe could strengthen the campaign:
I am happy to discuss these in more detail if useful.*
改变了什么: 原文花了 50 个词来请求允许发表意见。修改后的版本立刻就以具体、可操作的观察提供了价值。结尾依然留有余地,却没有削弱这些想法。
另一个极端——听起来自大、不屑一顾或针锋相对的文字——对职场关系的伤害也同样大。
改写前: I have told you multiple times that the current process is broken. It is obvious to anyone who actually looks at the data that we are losing money every single month because of this outdated system. I do not understand why this has not been fixed yet. This needs to happen immediately.
改写后: *The data from the past six months consistently shows that the current invoicing process is contributing to an average monthly revenue loss of $23,000 through delayed payments and processing errors. I have documented the three primary failure points in the attached analysis.
I recommend we prioritize updating the system in Q2. I have also included a preliminary cost-benefit comparison of three vendor solutions for your review. Could we discuss this at next week's operations meeting?*
改变了什么: 原文在攻击和指责("I have told you multiple times"、"obvious to anyone")。修改后的版本通过数据而不是沮丧的情绪来表达同样的紧迫性。它提供的是解决办法而不是抱怨,并提议了一个具体的讨论场合。
改写前: As I already explained in my previous email (which you apparently did not read), the approach you are suggesting will not work. I have been in this industry for 15 years and I can assure you that this has been tried before and it always fails. We need to go with my recommendation.
改写后: *Thank you for your suggestion. I want to share some context that may be relevant: this approach was attempted in our industry by several firms between 2019 and 2022, with limited success. The main challenges were customer adoption rates and integration costs, which typically exceeded initial projections by 40-60%.
That said, market conditions have changed since then. If you believe there are factors that make this approach more viable now, I would be interested in hearing your reasoning. Alternatively, I have outlined a modified approach in the attached document that addresses some of the historical challenges while preserving the core idea.*
改变了什么: 原文在摆资历("15 years"),轻视读者("which you apparently did not read"),并要求对方服从。修改后的版本提供了来自行业历史的论据,承认情况可能已经改变,邀请对方进一步讨论,并提出了一个建设性的替代方案。它自信,却不轻视对方。
改写前: Per my last email (sent March 1, which I am re-attaching for your convenience), the deadline was clearly stated as March 15. As previously communicated, failure to submit by the deadline would result in the consequences outlined in the project charter. I trust this will not be an issue going forward.
改写后: *I wanted to follow up on the March 15 deadline for the Phase 2 deliverables. My records show that we have not yet received your submission. Could you provide an update on the status and an estimated completion date?
If there are obstacles preventing timely delivery, I would like to discuss them so we can find a workable path forward.*
改变了什么: "Per my last email" 和 "as previously communicated" 被普遍认为是被动攻击的标志。原文以后果相威胁,字里行间满是讽刺("for your convenience"、"I trust this will not be an issue")。修改后的版本处理的是同一个情况——错过了截止日期——但重点在于解决问题,而不是惩罚人。
当职场写作塞满了含糊的语言、不必要的词语,以及只增加篇幅而不增加意义的空洞短语时,它就失去了力量。
改写前: Going forward, we need to make sure that we are all on the same page with regard to the various different aspects of the project, especially in terms of how we handle the different things that come up on a day-to-day basis. It would be great if everyone could kind of keep an eye on the big picture while also being mindful of the little details.
改写后: *To keep the project on track, I am implementing two changes:
These changes take effect next Monday. Let me know if you have questions.*
改变了什么: 原文用了 68 个词,却什么具体的内容也没有说。"on the same page"、"various different aspects"、"the different things that come up" 和 "kind of keep an eye on" 这样的短语都是含糊的填充语。修改后的版本找出了真正的问题(缺乏协调),并提供了带有具体细节的实际解决办法。
改写前: I wanted to take a moment to reach out to you regarding something that has been on my mind for a while now. As you may or may not be aware, there have been some recent developments in our industry that I think are worth paying attention to. With that in mind, I thought it would be a good idea to share some thoughts with you on this topic.
改写后: *Three regulatory changes announced last month will directly affect our compliance requirements:
I recommend we schedule a compliance review session before April 15 to assess our readiness. I can prepare a gap analysis if that would be helpful.*
改变了什么: 原文用了 77 个词,才开始涉及任何内容。职场读者都很忙——他们不需要热身。修改后的版本先说重要的信息,接着给出具体的待办事项。
改写前: We need to leverage our core competencies to drive synergistic outcomes across verticals. By aligning our value proposition with key stakeholder expectations and optimizing our go-to-market strategy, we can unlock new revenue streams and create a sustainable competitive advantage in the marketplace.
改写后: *Our strongest capabilities are data analytics and customer onboarding. I recommend we focus these strengths on two high-potential markets: healthcare and financial services.
Specifically:
Expected revenue impact: $1.2M in new contracts within 12 months.*
改变了什么: "leverage core competencies"、"synergistic outcomes" 和 "unlock revenue streams" 这样的商务行话听起来很了不起,传达的信息却少得可怜。修改后的版本用具体的能力、市场和预期结果取代了时髦词。读完修改后的版本,读者确切地知道提议的是什么、为什么提议。
有些职场写作的失败,问题不在于个别的词,而在于误判了情境中的情绪氛围。
改写前: Hi everyone! Exciting news — we are restructuring the department! Some roles will be changing and a few positions will be eliminated. But this is a great opportunity for the company to become more efficient and competitive. Let me know if you have questions!
改写后: *Team,
I want to share some important organizational changes that will take effect on May 1.
After a thorough review of our departmental structure, leadership has decided to consolidate several roles to better align with our current business priorities. This means that some positions will be restructured and, unfortunately, a small number of roles will be eliminated.
I understand this news may be concerning. Here is what I can share at this point:
I am committed to making this transition as transparent and supportive as possible.*
改变了什么: 原文不合时宜到了令人吃惊的地步——用感叹号和「好消息」的框架来宣布裁撤岗位。修改后的版本承认了情况的严重性,提供了关于后续步骤的具体信息,并在保持专业的同时表现出了同理心。
改写前: I'm not sure what you're referring to. We followed all the procedures correctly on our end. Maybe the issue is on your side? You should check with your IT department. Let us know if the problem persists.
改写后: *Thank you for bringing this to our attention. I understand the frustration this issue is causing, and I want to ensure we resolve it promptly.
I have reviewed our logs and confirmed that our systems processed the request correctly on March 10. However, I recognize that the issue you are experiencing is real regardless of where it originated. To help diagnose the problem, could you provide the following:
Once I have this information, I will coordinate with our technical team to identify the root cause. I will follow up with you by end of day Thursday with an update.*
改变了什么: 原文推卸责任,让客户独自去解决问题。修改后的版本承认了客户的遭遇,说明了已经检查过的内容,询问了具体的诊断信息,并承诺了跟进的时间。即使问题出在客户那边,专业的做法也是帮忙找到答案,而不是指指点点。
纵观这些改写前后的对比,可以看出几条一致的模式:
约7分钟阅读
本节供快速查阅之用。当你在起草或修改职场文字、需要确认语气是否到位时,就可以用它。它包括该做与不该做的事、常见的软弱或有问题的表达的替换短语,以及一份循序渐进的自我修改指南。
这张表为常见的软弱、含糊或不专业的短语提供了直接的替换。左栏是要避免的短语;右栏是专业的替代说法。
| 避免 | 改用 |
|---|---|
| I just wanted to... | I wanted to... / I am writing to... |
| Sorry to bother you, but... | [删掉——直接说出你的信息] |
| I was wondering if maybe... | Could we... / I would like to... |
| This might not be a good idea, but... | I recommend... / I suggest... |
| I'm not sure, but I think... | Based on [evidence], I believe... |
| I could be wrong, but... | The data suggests... / My assessment is... |
| I hope that's okay | [删掉——或者直接问:"Does this work for you?"] |
| No worries if not | Please let me know either way |
| Does that make sense? | Let me know if you have questions |
| Kind of / sort of | [删掉,或换成一个精确的限定语] |
| I feel like... | I believe... / The evidence indicates... |
| Basically... | [删掉——直接说出要点] |
| 避免 | 改用 |
|---|---|
| things / stuff | [说出具体的项目] |
| soon / in the near future | by [specific date] |
| a lot / a bunch | [具体的数字或数量] |
| some issues | [说出具体的问题] |
| going forward | starting [date] / from now on |
| various stakeholders | [说出具体的利益相关方或群体] |
| the situation | [描述具体的情况] |
| at this point in time | now / currently |
| in terms of | regarding / concerning |
| with regard to | about / regarding |
| in the event that | if |
| at the end of the day | ultimately |
| touch base | meet / discuss / follow up |
| circle back | follow up / revisit |
| take it offline | discuss separately / discuss in a meeting |
| 避免 | 改用 |
|---|---|
| Per my last email... | Following up on my March 5 message... |
| As I already explained... | To clarify... / To provide additional context... |
| Obviously... / Clearly... | The data shows... / As the report indicates... |
| You failed to... | The [task] was not completed... |
| You need to... | I recommend... / Please [action]... |
| I don't understand why... | Could you help me understand... |
| This is unacceptable | This does not meet the agreed-upon standard |
| That is wrong | I see it differently — here is my perspective... |
| Anyone can see that... | The evidence supports the conclusion that... |
| I told you so | As the earlier analysis indicated... |
| 较不正式 | 较正式 |
|---|---|
| Thanks | Thank you |
| ASAP | at your earliest convenience / by [date] |
| FYI | For your information / I wanted to share |
| Heads up | I wanted to let you know |
| Get back to me | Please respond by [date] |
| Sounds good | That works well / I agree with this approach |
| No problem | You are welcome / I am happy to help |
| My bad | I apologize for the oversight |
| Awesome / Great | Excellent / That is a strong result |
| Works for me | That is acceptable / I agree |
职场邮件的开头一句,为整封邮件定下了基调。下面是常见情境的模板:
以一个明确的下一步或一句专业的落款来结束:
| 正式程度 | 落款 |
|---|---|
| 标准 | Best regards, / Kind regards, |
| 稍显正式 | Sincerely, / Respectfully, |
| 亲切而专业 | Best, / Warm regards, |
| 随意的职场风格 | Thanks, / Thank you, |
起草完任何一份职场文件后,都用这份清单过一遍,确保你的语气到位。
找出下面这些词,把它们删掉或替换掉:
找出可能读起来带有敌意或被动攻击的短语:
如果找到了,就改写成聚焦于问题而不是聚焦于人的表达。
如果你不确定自己的职场文字语气是否恰当,问自己下面这五个问题:
我会乐意在会议上把它大声读出来吗? 如果它在会议上听起来太随意,那么用在正式的邮件或报告里很可能也太随意了。
如果它被转发给一个我从未见过的人,我会觉得无所谓吗? 职场写作即使脱离了上下文,也应该能够自立。
每个段落都有它存在的价值吗? 如果删掉一个段落,读者也不会错过任何重要的东西,那就删掉它。
我写的是问题还是解决办法? 职场写作关注的是向前推进。指出问题,然后迅速转向能为此做些什么。
我会想收到这样一条信息吗? 把自己放在读者的位置上。这条信息清楚、礼貌、可操作吗?这就是一位职场读者全部的要求。