{ "archive_path": "archive/1752726443.501588", "base_url": "refactoringenglish.com/chapters/techniques-for-writing-emails/#whats-an-effective-email", "basename": "", "bookmarked_date": "2025-07-17 04:27", "canonical": { "archive_org_path": "https://web.archive.org/web/refactoringenglish.com/chapters/techniques-for-writing-emails/#whats-an-effective-email", "dom_path": "output.html", "favicon_path": "favicon.ico", "git_path": "git/", "google_favicon_path": "https://www.google.com/s2/favicons?domain=refactoringenglish.com", "headers_path": "headers.json", "htmltotext_path": "htmltotext.txt", "index_path": "index.html", "media_path": "media/", "mercury_path": "mercury/content.html", "pdf_path": "output.pdf", "readability_path": "readability/content.html", "screenshot_path": "screenshot.png", "singlefile_path": "singlefile.html", "warc_path": "warc/", "wget_path": null }, "domain": "refactoringenglish.com", "downloaded_at": "2025-07-17T04:27:30.149591+00:00", "downloaded_datestr": "2025-07-17 04:27", "extension": "", "hash": "1P96MJ1JNZMM0B1TRE50", "history": { "archive_org": [ { "cmd": [ "/usr/bin/curl", "--silent", "--location", "--compressed", "--proxy", "socks5://tor-socks-proxy:9150", "--head", "--max-time", "60", "--user-agent", "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36 ArchiveBox/{VERSION} (+https://github.com/ArchiveBox/ArchiveBox/)", "https://web.archive.org/save/https://refactoringenglish.com/chapters/techniques-for-writing-emails/#whats-an-effective-email" ], "cmd_version": "8.10.1", "end_ts": "2025-07-17T04:28:51.266975+00:00", "index_texts": null, "output": "https://web.archive.org/web/20250717042817/https://refactoringenglish.com/chapters/techniques-for-writing-emails/", "pwd": "/data/archive/1752726443.501588", "schema": "ArchiveResult", "start_ts": "2025-07-17T04:28:12.918959+00:00", "status": "succeeded" } ], "dom": [ { "cmd": [ "/usr/bin/chromium-browser", "--proxy-server=socks5://tor-socks-proxy:9150", "--disable-features=DarkMode", "--run-all-compositor-stages-before-draw", "--hide-scrollbars", "--autoplay-policy=no-user-gesture-required", "--no-first-run", "--use-fake-ui-for-media-stream", "--use-fake-device-for-media-stream", "--simulate-outdated-no-au='Tue, 31 Dec 2099 23:59:59 GMT'", "--headless=new", "--no-sandbox", "--no-zygote", "--disable-dev-shm-usage", "--disable-software-rasterizer", "--disable-sync", "--window-size=1440,2000", "--user-agent=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36 ArchiveBox/{VERSION} (+https://github.com/ArchiveBox/ArchiveBox/)", "--user-data-dir=/data/personas/Default/chrome_profile", "--profile-directory=Default", "--dump-dom", "https://refactoringenglish.com/chapters/techniques-for-writing-emails/#whats-an-effective-email" ], "cmd_version": "131.0.6778", "end_ts": "2025-07-17T04:27:47.546159+00:00", "index_texts": null, "output": "output.html", "pwd": "/data/archive/1752726443.501588", "schema": "ArchiveResult", "start_ts": "2025-07-17T04:27:39.647001+00:00", "status": "succeeded" } ], "favicon": [ { "cmd": [ "/usr/bin/curl", "--silent", "--location", "--compressed", "--proxy", "socks5://tor-socks-proxy:9150", "--max-time", "60", "--output", "favicon.ico", "--user-agent", "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36 ArchiveBox/{VERSION} (+https://github.com/ArchiveBox/ArchiveBox/)", "https://www.google.com/s2/favicons?domain=refactoringenglish.com" ], "cmd_version": "8.10.1", "end_ts": "2025-07-17T04:27:33.553297+00:00", "index_texts": null, "output": "favicon.ico", "pwd": "/data/archive/1752726443.501588", "schema": "ArchiveResult", "start_ts": "2025-07-17T04:27:30.382243+00:00", "status": "succeeded" } ], "git": [], "headers": [ { "cmd": [ "/usr/bin/curl", "--silent", "--location", "--compressed", "--proxy", "socks5://tor-socks-proxy:9150", "--head", "--max-time", "60", "--user-agent", "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36 ArchiveBox/{VERSION} (+https://github.com/ArchiveBox/ArchiveBox/)", "https://refactoringenglish.com/chapters/techniques-for-writing-emails/#whats-an-effective-email" ], "cmd_version": "8.10.1", "end_ts": "2025-07-17T04:27:33.659261+00:00", "index_texts": null, "output": "headers.json", "pwd": "/data/archive/1752726443.501588", "schema": "ArchiveResult", "start_ts": "2025-07-17T04:27:33.592518+00:00", "status": "succeeded" } ], "htmltotext": [ { "cmd": [ "(internal) archivebox.extractors.htmltotext", "./{singlefile,dom}.html" ], "cmd_version": "0.8.5rc51", "end_ts": "2025-07-17T04:28:06.500703+00:00", "index_texts": [ "Underused Techniques for Effective Emails \u00b7 Refactoring English (/favicon.ico) (/favicon/favicon-96x96.png) (/favicon/favicon.svg) (/favicon/apple-touch-icon.png) (/favicon/site.webmanifest) (https://refactoringenglish.com/chapters/techniques-for-writing-emails/) (https://refactoringenglish.com/chapters/techniques-for-writing-emails/) (/third-party/bootstrap/5.3.3/bootstrap.min.css) (/third-party/font-awesome/v6.7.1/css/fontawesome.min.css) (/third-party/font-awesome/v6.7.1/css/brands.min.css) (/third-party/font-awesome/v6.7.1/css/solid.min.css) (/assets/css/bundle.min.5b29e784cb8f40f3cdc227162c3c2a0961382e67af569cf5175076dae4c66323.css) (/) Refactoring English (/author) Author (/chapters) Sample Chapters (/tools) Tools Services (/services/blog-editing) Blog Editing (/services/blog-review) High-Level Blog Review (/early-access) Early Access Underused Techniques for Effective Emails by (/author) Michael Lynch , published July 16, 2025 For software developers, there\u2019s tremendous value in writing effective emails. Good emails save time, reduce misunderstandings, and earn you recognition within your company. You can drastically improve your emails with a few simple techniques, but too few developers know about them. What\u2019s an effective email? Deliver the most important information first Use the Markdown Here browser extension Write complete replies rather than quick ones Split threads and curate recipients Create structure with headings and paragraph breaks What\u2019s an effective email?\ud83d\udd17 An effective email has five key qualities: Clear : Recipients understand what the email is telling them without additional clarification. Action-oriented : The email makes it clear what actions you expect of the email\u2019s recipients. Relevant : Recipients quickly recognize why the information is relevant to them. Efficient : You and your recipients achieve your goals while minimizing everyone\u2019s time reading and responding to the email thread. Succinct : The email maintains a high signal-to-noise ratio. Deliver the most important information first\ud83d\udd17 When you see a co-worker in person, you typically don\u2019t blurt out your most important thought before even saying hello, but that\u2019s the right thing to do in email. Your co-workers receive hundreds of emails per day. They don\u2019t have time to read every email in full, so they skim their inbox to find what\u2019s relevant to them. To ensure that your recipients see the information they need, present the most important information in your email first. As an exercise, here\u2019s an intentionally boring and long-winded email. Give it a quick skim to see if you can spot anything worth reading: Subject: A surprise discoveryTo: hamsterchat-team@\u200bexample.com, devops@\u200bexample.com Hi All, I was playing checkers with my dog, Sgt. Francisco, when I noticed that his ID tag had fallen off his collar. It may have been gone for months. It made me wonder about other safety measures that I might be taking for granted. So, I started thinking about HamsterChat\u2019s data backups. On a hunch, I went to our data center last night at around 8 PM to test my theory. I talked to Tony, the admin there, and he set me up with a crash cart at our server. Sure enough, every backup snapshot I tested was corrupt and unrecoverable. I was able to isolate the problem to a faulty RAM stick. Boy, was that a surprise! Tony had never seen anything like it. Goes to show that thinking about adjacent problems is worthwhile! Sincerely,William Hamsterton-Chatsworth Unless you read the above email in full, you probably missed the most important detail: all the backups are gone . For important emails, start with a one-line summary or a short list of bullet points before you even get to \u201cHello.\u201d After the summary, present the supporting details in descending order of importance. Here\u2019s the previous email, rewritten to present the most important information first: Subject: Failure in HamsterChat backups - all backups lostTo: hamsterchat-team@\u200bexample.com, devops@\u200bexample.com tl;dr: All historical HamsterChat backups are corrupt and unusable. Backups are healthy again starting today. Hi All, Due to a hardware failure in our storage server, all of our HamsterChat backups are corrupt. I\u2019ve replaced the faulty hardware and verified that backup and restore operations are healthy. I\u2019m working with our DevOps team to automate a weekly backup and restore test. If anything corrupts our backups in the future, we\u2019ll catch it within a week rather than stumbling across the issue months later by chance. From digging into the logs and running diagnostics, I isolated the cause to a faulty RAM stick in our storage server. It appears that it was silently flipping bits on disk writes, so the filesystem thought the write succeeded, but the data that landed on the disk was corrupt. After replacing the RAM stick, I took a backup and successfully restored it to a fresh disk. This strongly supports my hypothesis that the faulty RAM stick was to blame. Sincerely,William Hamsterton-Chatsworth Some organizations call this style of writing (https://en.wikipedia.org/wiki/BLUF_(communication)) bottom-line, up front (BLUF) . Journalists call this (https://en.wikipedia.org/wiki/Inverted_pyramid_(journalism)) \u201cthe inverted pyramid\u201d because the information becomes relevant to a smaller and smaller audience as you get deeper into the text. (An inverted pyramid) Journalists structure news reports in an inverted pyramid, where the information relevant to the most people is at the top. Note how the information in the email above matches the inverted pyramid style: (An inverted pyramid) Details from the original email about the dog and the data center admin no longer appear in the revised email. Those details were irrelevant, so cutting them maintains a high signal-to-noise ratio, making it easier for recipients to capture important details. Use the (https://markdown-here.com/) Markdown Here browser extension\ud83d\udd17 Markdown Here is (https://markdown-here.com/) a free, open-source browser extension that lets you write emails in Markdown. As a software developer, my emails frequently contain code snippets and inline code. Markdown Here makes it easy to format code clearly and add simple formatting right from the keyboard. I compose emails in Markdown like this: (/chapters/techniques-for-writing-emails/markdown-here-before.webp) () Then, I hit Ctrl+Alt+M , and Markdown Here turns my email into this: (/chapters/techniques-for-writing-emails/markdown-here-after.webp) () I\u2019m baffled that Markdown Here isn\u2019t a thousand times more popular. I\u2019ve been recommending it for a decade, and whenever I tell people about it, I feel like I\u2019m in (https://en.wikipedia.org/wiki/Yesterday_(2019_film)) that movie where the guy wakes up one day, and nobody else knows who The Beatles are. Write complete replies rather than quick ones\ud83d\udd17 When an email is sitting in your inbox, a part of you just wants to get rid of it as quickly as possible. The email represents work, and the sooner you reply, the sooner you can stop thinking about that work. Sending a quick reply feels like completing a work task, but you\u2019re actually creating more work for yourself and your teammates. To show what I mean, here\u2019s an email thread where everyone responds quickly: Subject: Custom build for OptimojiTo: pm-team@\u200bexample.com; dev-team@\u200bexample.com Optimoji agreed to participate in our HamsterChat beta, but they only have ARM servers. Can you compile an out-of-band ARM build for them? Subject: Custom build for OptimojiTo: pm-team@\u200bexample.com; dev-team@\u200bexample.com Which version of ARM? Subject: Custom build for OptimojiTo: pm-team@\u200bexample.com; dev-team@\u200bexample.com I\u2019m not sure. They\u2019re running Ampere Altra Max machines. Subject: Custom build for OptimojiTo: pm-team@\u200bexample.com; dev-team@\u200bexample.com Okay, Ampere Altra Max is ARM v8.2a. Do you want the Pro or Enterprise version for them? Subject: Custom build for OptimojiTo: pm-team@\u200bexample.com; dev-team@\u200bexample.com Enterprise. Subject: Custom build for OptimojiTo: pm-team@\u200bexample.com; dev-team@\u200bexample.com Do they need the multi-language extension, or is it just en-US ? Subject: Custom build for OptimojiTo: pm-team@\u200bexample.com; dev-team@\u200bexample.com English only. Subject: Custom build for OptimojiTo: pm-team@\u200bexample.com; dev-team@\u200bexample.com Okay, here you go. Had either participant in the thread put more care into their emails, they would have recognized that they were omitting critical details or failing to solicit them. The thread above is eight emails, but let\u2019s assume that there were 10 people on the thread. That\u2019s now 80 emails, meaning this trivial thread caused 80 collective context switches for employees across this company. Had the participants instead optimized for complete replies, they could have resolved this thread in two emails: Subject: Custom build for OptimojiTo: pm-team@\u200bexample.com; dev-team@\u200bexample.com Optimoji agreed to participate in our HamsterChat beta, but they only have ARM servers (Ampere Altra Max). Can you do a custom build for them with these properties? Architecture: ARM Tier: Enterprise Language: en-US only Subject: Custom build for OptimojiTo: pm-team@\u200bexample.com; dev-team@\u200bexample.com Sure, see attached. Ampere Altra Max is ARMv8, so I added that to our build matrix for the next release. If they need updates in the future, they can download our standard release builds as long as they choose ARMv8 flavor. Cal Newport describes this style of managing email as (https://calnewport.com/write-longer-emails/) process-centric email . Newport recommends treating every email thread as a problem the recipients must solve. The goal is to create a process for solving that problem in as few emails as possible. Split threads and curate recipients\ud83d\udd17 Sometimes an email thread drifts beyond its original scope. The subject line no longer represents the conversation accurately, and the recipients are no longer be the right participants for the discussion. When an email\u2019s scope changes, actively split the thread to eliminate noise by doing the following: Update the subject line to match the new scope of the discussion. Move any recipients to bcc if the thread is no longer relevant to them. Add any new recipients for whom the thread is relevant. Briefly explain the context of the thread for the people you added. As a concrete example, imagine that you start an email thread to review a design document: Subject: HamsterChat v2 design reviewTo: architecture-astronauts@\u200bexample.com; hamsterchat-dev@\u200bexample.com Hi All, The HamsterChat v2 design document is now ready for review: https://\u200bexample.com/docs/hamsterchat-v2-spec/edit -William Everyone signs off on the design, but someone suggests looping in the infrastructure team to coordinate hardware resources. The anti-pattern at this stage would be to add the infrastructure team to the thread and ask them a vague question: Subject: HamsterChat v2 design reviewTo: infrastructure@\u200bexample.com Cc: hamsterchat-dev@\u200bexample.com; architecture-astronauts@\u200bexample.com Infrastructure folks - can you weigh in here? What\u2019s wrong with that email? A lot, actually: You\u2019re forcing the infrastructure team to dig through the thread to understand what you\u2019re asking them. The subject line is still \u201cHamsterChat design review,\u201d even though it\u2019s no longer a design review. You\u2019re dragging along a bunch of people from the design review who don\u2019t care about coordinating hardware resources, so the email is now pure distraction for them. You can solve all of those problems by splitting the thread: Subject: HamsterChat Q3 infra resources WAS: HamsterChat v2 design reviewTo: infrastructure@\u200bexample.comCc: hamsterchat-dev@\u200bexample.comBcc: architecture-astronauts@\u200bexample.com [adding infrastructure@, moving architecture-astronauts@ to bcc] Hi Infrastructure Folks, We\u2019re planning to introduce a new version of HamsterChat in Q3 (see thread below). The new service will require at least two 4-vCPU application servers and one 2-vCPU database server for testing. Will the infrastructure team be able to provide that by Q3? -William Create structure with headings and paragraph breaks\ud83d\udd17 When talented speakers give presentations, they write every slide with care. They break up their talking points into small, digestable chunks, and they choose descriptive yet succinct headings. When you\u2019re writing a long email, think about it the same way you\u2019d present a slide deck. Focus each paragraph around a single idea. When in doubt, err on the side of shorter sentences and paragraphs. If your emails begin to look like LinkedIn clickbait, that\u2019s too short. Subject: Severe HamsterChat outage - all regions affectedTo: all-staff@\u200bexample.com Have you ever noticed that our website is unreachable? I noticed. And once I saw it, I couldn\u2019t unsee it. The cause? A stray curly brace in our nginx config. Click below\ud83d\udc47 for five unbeatable strategies to prevent outages. For emails longer than about five paragraphs, use headings to help your readers recognize the structure of your email. Subject: HamsterChat rollout planTo: all-staff@\u200bexample.com We are still on track for the HamsterChat global release on Wednesday, July 16 . There are many delicate pieces to this launch, so I\u2019ve summarized them all to ensure that we\u2019re all on the same page. Release announcement\ud83d\udd17 We\u2019ll publish the release announcement to our blog on Wednesday at 12:01am ET. We got a lot of great tips from (/chapters/release-announcements/) the release announcements chapter in Refactoring English , so we anticipate 10+ million visitors within the first few minutes. Product Hunt launch\ud83d\udd17 HamsterChat will launch on Product Hunt on Wednesday at 3:01am ET. We purchased Product Hunt\u2019s Authentic Indie Platinum package, which guarantees that HamsterChat finishes the day in the #1 spot from organic votes. We anticipate the visibility on PH to bring in as many as four (4) unique visitors. TechCrunch interview\ud83d\udd17 \u2026 Section headings are also helpful when your email has multiple audiences who care about different subsets of your email. When you\u2019re emailing multiple teams, headings allow readers to zero in on the parts of your email that matter to them. Summary\ud83d\udd17 Effective emails are clear, action-oriented, relevant, efficient, and succinct. Structure emails to deliver the most important information first, potentially with one-line summaries or bullet points. Use the Markdown Here browser extension to format your emails beautifully. Replying quickly is less important than minimizing the number of emails in a thread. Update the subject line and recipients when a thread\u2019s scope drifts from its original purpose. Use headings and paragraph breaks to help recipients understand the structure of your emails. Read the full book This is an excerpt from my upcoming book, (/) Refactoring English: Effective Writing for Software Developers . (/) To improve your writing and further your career, (/early-access) purchase early access for the latest ebook draft\nand new chapters every month. (/early-access) Early Access Please enable Javascript to view comments. (Talkyard comments helper iframe) " ], "output": "htmltotext.txt", "pwd": "/data/archive/1752726443.501588", "schema": "ArchiveResult", "start_ts": "2025-07-17T04:28:06.472393+00:00", "status": "succeeded" } ], "media": [ { "cmd": [ "/usr/local/bin/yt-dlp", "--restrict-filenames", "--trim-filenames", "128", "--write-description", "--write-info-json", "--write-annotations", "--write-thumbnail", "--no-call-home", "--write-sub", "--write-auto-subs", "--convert-subs=srt", "--yes-playlist", "--continue", "--no-abort-on-error", "--ignore-errors", "--geo-bypass", "--add-metadata", "--format=(bv*+ba/b)[filesize<=750m][filesize_approx<=?750m]/(bv*+ba/b)", "--skip-download", "--cache-dir=/data/yt-dlp-cache/", "--cookies=/data/yt-dlp-cache/cookies.txt", "--proxy=socks5://tor-socks-proxy:9150", "--no-playlist", "https://refactoringenglish.com/chapters/techniques-for-writing-emails/#whats-an-effective-email" ], "cmd_version": "2024.10.7", "end_ts": "2025-07-17T04:28:12.888672+00:00", "index_texts": [], "output": "media/", "pwd": "/data/archive/1752726443.501588", "schema": "ArchiveResult", "start_ts": "2025-07-17T04:28:08.533998+00:00", "status": "succeeded" } ], "mercury": [ { "cmd": [ "/home/archivebox/.npm/bin/postlight-parser", "https://refactoringenglish.com/chapters/techniques-for-writing-emails/#whats-an-effective-email" ], "cmd_version": "2.2.3", "end_ts": "2025-07-17T04:28:06.428340+00:00", "index_texts": null, "output": "mercury/", "pwd": "/data/archive/1752726443.501588", "schema": "ArchiveResult", "start_ts": "2025-07-17T04:28:02.778998+00:00", "status": "succeeded" } ], "pdf": [], "readability": [ { "cmd": [ "/home/archivebox/.npm/bin/readability-extractor", "/tmp/tmpx7pgi7vy", "https://refactoringenglish.com/chapters/techniques-for-writing-emails/#whats-an-effective-email" ], "cmd_version": "0.0.11", "end_ts": "2025-07-17T04:27:51.580172+00:00", "index_texts": [ "For software developers, there\u2019s tremendous value in writing effective emails. Good emails save time, reduce misunderstandings, and earn you recognition within your company.You can drastically improve your emails with a few simple techniques, but too few developers know about them.What\u2019s an effective email?Deliver the most important information firstUse the Markdown Here browser extensionWrite complete replies rather than quick onesSplit threads and curate recipientsCreate structure with headings and paragraph breaksWhat\u2019s an effective email?\ud83d\udd17An effective email has five key qualities:Clear: Recipients understand what the email is telling them without additional clarification.Action-oriented: The email makes it clear what actions you expect of the email\u2019s recipients.Relevant: Recipients quickly recognize why the information is relevant to them.Efficient: You and your recipients achieve your goals while minimizing everyone\u2019s time reading and responding to the email thread.Succinct: The email maintains a high signal-to-noise ratio.Deliver the most important information first\ud83d\udd17When you see a co-worker in person, you typically don\u2019t blurt out your most important thought before even saying hello, but that\u2019s the right thing to do in email.Your co-workers receive hundreds of emails per day. They don\u2019t have time to read every email in full, so they skim their inbox to find what\u2019s relevant to them.To ensure that your recipients see the information they need, present the most important information in your email first.As an exercise, here\u2019s an intentionally boring and long-winded email. Give it a quick skim to see if you can spot anything worth reading:Subject: A surprise discoveryTo: hamsterchat-team@\u200bexample.com, devops@\u200bexample.comHi All,I was playing checkers with my dog, Sgt. Francisco, when I noticed that his ID tag had fallen off his collar. It may have been gone for months.It made me wonder about other safety measures that I might be taking for granted. So, I started thinking about HamsterChat\u2019s data backups.On a hunch, I went to our data center last night at around 8 PM to test my theory. I talked to Tony, the admin there, and he set me up with a crash cart at our server. Sure enough, every backup snapshot I tested was corrupt and unrecoverable. I was able to isolate the problem to a faulty RAM stick. Boy, was that a surprise! Tony had never seen anything like it.Goes to show that thinking about adjacent problems is worthwhile!Sincerely,William Hamsterton-ChatsworthUnless you read the above email in full, you probably missed the most important detail: all the backups are gone.For important emails, start with a one-line summary or a short list of bullet points before you even get to \u201cHello.\u201d After the summary, present the supporting details in descending order of importance.Here\u2019s the previous email, rewritten to present the most important information first:Subject: Failure in HamsterChat backups - all backups lostTo: hamsterchat-team@\u200bexample.com, devops@\u200bexample.comtl;dr: All historical HamsterChat backups are corrupt and unusable. Backups are healthy again starting today.Hi All,Due to a hardware failure in our storage server, all of our HamsterChat backups are corrupt. I\u2019ve replaced the faulty hardware and verified that backup and restore operations are healthy.I\u2019m working with our DevOps team to automate a weekly backup and restore test. If anything corrupts our backups in the future, we\u2019ll catch it within a week rather than stumbling across the issue months later by chance.From digging into the logs and running diagnostics, I isolated the cause to a faulty RAM stick in our storage server. It appears that it was silently flipping bits on disk writes, so the filesystem thought the write succeeded, but the data that landed on the disk was corrupt.After replacing the RAM stick, I took a backup and successfully restored it to a fresh disk. This strongly supports my hypothesis that the faulty RAM stick was to blame.Sincerely,William Hamsterton-ChatsworthSome organizations call this style of writing bottom-line, up front (BLUF). Journalists call this \u201cthe inverted pyramid\u201d because the information becomes relevant to a smaller and smaller audience as you get deeper into the text.Journalists structure news reports in an inverted pyramid, where the information relevant to the most people is at the top.Note how the information in the email above matches the inverted pyramid style:Details from the original email about the dog and the data center admin no longer appear in the revised email. Those details were irrelevant, so cutting them maintains a high signal-to-noise ratio, making it easier for recipients to capture important details.Use the Markdown Here browser extension\ud83d\udd17Markdown Here is a free, open-source browser extension that lets you write emails in Markdown.As a software developer, my emails frequently contain code snippets and inline code. Markdown Here makes it easy to format code clearly and add simple formatting right from the keyboard.I compose emails in Markdown like this:Then, I hit Ctrl+Alt+M, and Markdown Here turns my email into this:I\u2019m baffled that Markdown Here isn\u2019t a thousand times more popular. I\u2019ve been recommending it for a decade, and whenever I tell people about it, I feel like I\u2019m in that movie where the guy wakes up one day, and nobody else knows who The Beatles are.When an email is sitting in your inbox, a part of you just wants to get rid of it as quickly as possible. The email represents work, and the sooner you reply, the sooner you can stop thinking about that work.Sending a quick reply feels like completing a work task, but you\u2019re actually creating more work for yourself and your teammates.To show what I mean, here\u2019s an email thread where everyone responds quickly:Subject: Custom build for OptimojiTo: pm-team@\u200bexample.com; dev-team@\u200bexample.comOptimoji agreed to participate in our HamsterChat beta, but they only have ARM servers.Can you compile an out-of-band ARM build for them?Subject: Custom build for OptimojiTo: pm-team@\u200bexample.com; dev-team@\u200bexample.comWhich version of ARM?Subject: Custom build for OptimojiTo: pm-team@\u200bexample.com; dev-team@\u200bexample.comI\u2019m not sure. They\u2019re running Ampere Altra Max machines.Subject: Custom build for OptimojiTo: pm-team@\u200bexample.com; dev-team@\u200bexample.comOkay, Ampere Altra Max is ARM v8.2a.Do you want the Pro or Enterprise version for them?Subject: Custom build for OptimojiTo: pm-team@\u200bexample.com; dev-team@\u200bexample.comEnterprise.Subject: Custom build for OptimojiTo: pm-team@\u200bexample.com; dev-team@\u200bexample.comDo they need the multi-language extension, or is it just en-US?Subject: Custom build for OptimojiTo: pm-team@\u200bexample.com; dev-team@\u200bexample.comEnglish only.Subject: Custom build for OptimojiTo: pm-team@\u200bexample.com; dev-team@\u200bexample.comOkay, here you go.Had either participant in the thread put more care into their emails, they would have recognized that they were omitting critical details or failing to solicit them.The thread above is eight emails, but let\u2019s assume that there were 10 people on the thread. That\u2019s now 80 emails, meaning this trivial thread caused 80 collective context switches for employees across this company.Had the participants instead optimized for complete replies, they could have resolved this thread in two emails:Subject: Custom build for OptimojiTo: pm-team@\u200bexample.com; dev-team@\u200bexample.comOptimoji agreed to participate in our HamsterChat beta, but they only have ARM servers (Ampere Altra Max).Can you do a custom build for them with these properties?Architecture: ARMTier: EnterpriseLanguage: en-US onlySubject: Custom build for OptimojiTo: pm-team@\u200bexample.com; dev-team@\u200bexample.comSure, see attached.Ampere Altra Max is ARMv8, so I added that to our build matrix for the next release.If they need updates in the future, they can download our standard release builds as long as they choose ARMv8 flavor.Cal Newport describes this style of managing email as process-centric email. Newport recommends treating every email thread as a problem the recipients must solve. The goal is to create a process for solving that problem in as few emails as possible.Split threads and curate recipients\ud83d\udd17Sometimes an email thread drifts beyond its original scope. The subject line no longer represents the conversation accurately, and the recipients are no longer be the right participants for the discussion.When an email\u2019s scope changes, actively split the thread to eliminate noise by doing the following:Update the subject line to match the new scope of the discussion.Move any recipients to bcc if the thread is no longer relevant to them.Add any new recipients for whom the thread is relevant.Briefly explain the context of the thread for the people you added.As a concrete example, imagine that you start an email thread to review a design document:Subject: HamsterChat v2 design reviewTo: architecture-astronauts@\u200bexample.com; hamsterchat-dev@\u200bexample.comHi All,The HamsterChat v2 design document is now ready for review:https://\u200bexample.com/docs/hamsterchat-v2-spec/edit-WilliamEveryone signs off on the design, but someone suggests looping in the infrastructure team to coordinate hardware resources.The anti-pattern at this stage would be to add the infrastructure team to the thread and ask them a vague question:Subject: HamsterChat v2 design reviewTo: infrastructure@\u200bexample.comCc: hamsterchat-dev@\u200bexample.com; architecture-astronauts@\u200bexample.comInfrastructure folks - can you weigh in here?What\u2019s wrong with that email?A lot, actually:You\u2019re forcing the infrastructure team to dig through the thread to understand what you\u2019re asking them.The subject line is still \u201cHamsterChat design review,\u201d even though it\u2019s no longer a design review.You\u2019re dragging along a bunch of people from the design review who don\u2019t care about coordinating hardware resources, so the email is now pure distraction for them.You can solve all of those problems by splitting the thread:Subject: HamsterChat Q3 infra resources WAS: HamsterChat v2 design reviewTo: infrastructure@\u200bexample.comCc: hamsterchat-dev@\u200bexample.comBcc: architecture-astronauts@\u200bexample.com[adding infrastructure@, moving architecture-astronauts@ to bcc]Hi Infrastructure Folks,We\u2019re planning to introduce a new version of HamsterChat in Q3 (see thread below).The new service will require at least two 4-vCPU application servers and one 2-vCPU database server for testing. Will the infrastructure team be able to provide that by Q3?-WilliamCreate structure with headings and paragraph breaks\ud83d\udd17When talented speakers give presentations, they write every slide with care. They break up their talking points into small, digestable chunks, and they choose descriptive yet succinct headings.When you\u2019re writing a long email, think about it the same way you\u2019d present a slide deck. Focus each paragraph around a single idea. When in doubt, err on the side of shorter sentences and paragraphs. If your emails begin to look like LinkedIn clickbait, that\u2019s too short.Subject: Severe HamsterChat outage - all regions affectedTo: all-staff@\u200bexample.comHave you ever noticed that our website is unreachable?I noticed.And once I saw it, I couldn\u2019t unsee it.The cause? A stray curly brace in our nginx config.Click below\ud83d\udc47 for five unbeatable strategies to prevent outages.For emails longer than about five paragraphs, use headings to help your readers recognize the structure of your email.Subject: HamsterChat rollout planTo: all-staff@\u200bexample.comWe are still on track for the HamsterChat global release on Wednesday, July 16.There are many delicate pieces to this launch, so I\u2019ve summarized them all to ensure that we\u2019re all on the same page.Release announcement\ud83d\udd17We\u2019ll publish the release announcement to our blog on Wednesday at 12:01am ET.We got a lot of great tips from the release announcements chapter in Refactoring English, so we anticipate 10+ million visitors within the first few minutes.Product Hunt launch\ud83d\udd17HamsterChat will launch on Product Hunt on Wednesday at 3:01am ET.We purchased Product Hunt\u2019s Authentic Indie Platinum package, which guarantees that HamsterChat finishes the day in the #1 spot from organic votes.We anticipate the visibility on PH to bring in as many as four (4) unique visitors.TechCrunch interview\ud83d\udd17\u2026Section headings are also helpful when your email has multiple audiences who care about different subsets of your email. When you\u2019re emailing multiple teams, headings allow readers to zero in on the parts of your email that matter to them.Summary\ud83d\udd17Effective emails are clear, action-oriented, relevant, efficient, and succinct.Structure emails to deliver the most important information first, potentially with one-line summaries or bullet points.Use the Markdown Here browser extension to format your emails beautifully.Replying quickly is less important than minimizing the number of emails in a thread.Update the subject line and recipients when a thread\u2019s scope drifts from its original purpose.Use headings and paragraph breaks to help recipients understand the structure of your emails." ], "output": "readability/", "pwd": "/data/archive/1752726443.501588", "schema": "ArchiveResult", "start_ts": "2025-07-17T04:27:48.536234+00:00", "status": "succeeded" } ], "screenshot": [], "singlefile": [], "title": [ { "cmd": [ "/usr/bin/curl", "--silent", "--location", "--compressed", "--proxy", "socks5://tor-socks-proxy:9150", "--max-time", "60", "--user-agent", "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36 ArchiveBox/{VERSION} (+https://github.com/ArchiveBox/ArchiveBox/)", "https://refactoringenglish.com/chapters/techniques-for-writing-emails/#whats-an-effective-email" ], "cmd_version": "8.10.1", "end_ts": "2025-07-17T04:27:47.615793+00:00", "index_texts": null, "output": "Underused Techniques for Effective Emails \u00b7 Refactoring English", "pwd": "/data/archive/1752726443.501588", "schema": "ArchiveResult", "start_ts": "2025-07-17T04:27:47.598169+00:00", "status": "succeeded" } ], "wget": [] }, "icons": null, "is_archived": true, "is_static": false, "latest": { "archive_org": "https://web.archive.org/web/20250717042817/https://refactoringenglish.com/chapters/techniques-for-writing-emails/", "dom": "output.html", "favicon": "favicon.ico", "git": null, "media": "media/", "pdf": null, "screenshot": null, "singlefile": null, "title": "Underused Techniques for Effective Emails \u00b7 Refactoring English", "warc": null, "wget": null }, "link_dir": "/data/archive/1752726443.501588", "newest_archive_date": "2025-07-17T04:28:12.918959+00:00", "num_failures": 0, "num_outputs": 9, "oldest_archive_date": "2025-07-17T04:27:30.382243+00:00", "path": "/chapters/techniques-for-writing-emails/", "schema": "Link", "scheme": "https", "snapshot_abid": "snp_01K0BA65GV52C8AC7601G20K4G", "snapshot_id": "36e988d0-40b9-48aa-90dc-63aa20204c90", "sources": [ "/data/sources/1752726442-import.txt" ], "tags": null, "tags_str": "", "timestamp": "1752726443.501588", "title": "Underused Techniques for Effective Emails \u00b7 Refactoring English", "url": "https://refactoringenglish.com/chapters/techniques-for-writing-emails/#whats-an-effective-email" }