Why do work emails take so long to write? Causes, costs and Mac fixes for developers

What the research says about email time

Good data on work email time is thin. The most useful figure comes from Microsoft's 2023 Work Trend Index. It says the heaviest 25% of email users spend 8.8 hours a week on email. The survey covered 31,000 full-time employed or self-employed workers in 31 markets. Microsoft 365 usage data came from a rolling 28-day period ending March 2023.

Read that number as a warning sign, not a benchmark. Heavy users are not average users. The figure shows what the top of the range looks like, and that is useful when you compare your own week.

Microsoft's June 2025 follow-up gives a different view. The average worker receives 117 emails a day, and most get skimmed in under 60 seconds. That is a reading figure. It does not report weekly hours on email, so it cannot tell you how long writing takes.

The same follow-up says employees are interrupted 275 times a day. That count covers only the top 20% of users by ping volume. Do not treat it as your own number. Use it to see how loud a busy inbox can get.

The 2023 report also splits your Microsoft 365 time by type of work. Email makes up 15% of that time. Communicating, which covers meetings, email, and chat, takes 57%. Creating takes 43%. Communication takes more of that time than creating does.

What a slow email habit costs you each week

Start with hours, then turn hours into money. Count the minutes you spend reading threads, drafting, and rereading. Do this for one normal week. A rough number is enough to decide whether a fix is worth an afternoon.

Here is the math, with the inputs labeled. The BLS puts average hourly earnings for all private-sector employees at $38.00 in its October 2026 release. That is a broad average, not a pay rate. Five hours a week over 48 working weeks comes to 240 hours, or about $9,120 a year. The five hours and the 48 weeks are example inputs. Replace them with your own.

The money is only part of the cost. Email also breaks your focus. Kushlev and Dunn tested checking habits directly. Their study enrolled 124 adults, about two-thirds of them students, in a two-week design.

In one week, people checked email three times a day. In the other week, they checked without a limit. Daily stress was lower in the limited week, though most people found the limit hard to keep. UBC's summary gives no effect sizes, so do not promise a number.

Why work emails take so long to write

Most slow emails are slow before the first word. You open the thread and scroll for the question. You check a ticket, a pull request, or a Slack message. By the time you type, you have already spent part of the job rebuilding context.

The second delay is the blank page. A reply to a product manager about a slipped release has many possible openings. You type one, delete it, and type another. Each restart costs more than the sentence itself.

Developers feel this most with bad news. The message must explain a cause, give a date, and avoid sounding defensive. Several goals at once make every sentence slower to write.

Mistakes that make the problem worse

1. Rewriting the same paragraph again and again. Each pass adds length, and the tone rarely gets clearer.
2. Checking the inbox every few minutes. Each check restarts your focus before you finish the reply.
3. Writing every reply from scratch. Most work replies repeat the same few answers.
4. Replying to the whole thread in one message. The reader then has to find the answer again.
5. Leaving email for the end of the day. Replies arrive late, and the work after them stalls.

Every mistake on that list has a cheap fix. The next sections cover the ones that take minutes to set up, then the ones that need a habit change.

Set up Text Replacements for the replies you send every week

Text Replacements turn a short trigger into a full sentence or paragraph. Developers often send the same few messages, such as a deploy status, a request for a call, or a reproduction request. Store them once and reuse them.

1. Choose Apple menu > System Settings > Keyboard > Text Replacements.
2. Click Add. Type the short trigger, then the full text it should expand into.
3. Click Done. Apple says Text Replacements are not available in all apps, so test them in each app you use.

Let Writing Tools proofread and rewrite your draft

Writing Tools works on text you have already written. Select the text, Control-click it, then choose Writing Tools > Show Writing Tools. The menu offers Proofread, Rewrite with Friendly, Professional, or Concise, Summarize or Key Points, and Describe a change.

Use Rewrite with Concise on a long draft. Then read the output against the thread. The tool changes wording. It cannot know whether the release really moved to a new date.

Check your version before you plan around it. Apple's Mac Help page for Writing Tools covers macOS 27. Apple also says Apple Intelligence is not available in every language or region, and usage limits may apply. Compose needs the ChatGPT extension. I did not verify older macOS versions.

Batch your email checks into fixed windows

Checking less is the one habit in this page with study support. Kushlev and Dunn's paper, published in Computers in Human Behavior, tested a limit of three checks a day. People felt less stressed in the limited week.

Most people found the limit hard to keep, so make it concrete. Pick fixed times, such as the start of the day, after lunch, and before you stop. Turn off Mail banner alerts in System Settings so new messages wait for your window.

Schedule sends and summarize threads in Gmail and Outlook

In Gmail on a computer, click Compose. Click the down arrow next to Send, then choose Schedule send. Gmail lets you keep up to 100 scheduled emails. Scheduled emails may go out a few minutes late, so keep exact times out of it.

Scheduling helps with time zones. Write the reply while the thread is fresh, then send it at the start of the other person's day. You avoid a second writing session later.

In Outlook for Mac, open the message and click the Copilot icon on the message toolbar. Choose Summarize and reply to this email. Microsoft says Copilot in Outlook works only in the latest Outlook for Mac. Legacy Outlook is not supported.

A worked example: a status email after a slipped release

Say a release slipped because of a bad migration. The client wants the new date, the cause, and what changes. The thread is long, so you start by reading it, not typing.

Ask before you reread. Hold ⌥ ⌘ and ask what the client asked for in the last message. Lazur answers out loud. Keep the thread open and check the key lines yourself.

Dictate the first pass next. Click in the reply, hold fn, and speak in plain words. Say the cause in one sentence and the new date in full. Dictation types the text at the cursor, so you can edit it right away.

Then run Writing Tools > Rewrite with Concise on the draft. Compare the new date with the thread. If the rewrite changed a fact, put the original back. Proofread last. If the client sits in another time zone, use Schedule send for their morning.

Handle sensitive email with care

Not every email can go into an AI tool. If you handle client data, personal data, or security details, follow your employer rules first. Developers face this too. Customer records, API keys, and incident details can sit in the thread you are rewriting.

Here is what Lazur does with your input. It listens and looks at your screen only while you hold the shortcut. Audio and the screenshot go to AI providers so they can answer. They are not stored, and content is never used to train AI models. Your employer may still say no, and that rule wins.

What to change first and how to measure it

Change one thing for a week. Start with Text Replacements because it takes minutes to set up. Add scheduled sends for messages that can wait. Keep a note of the minutes you spend on email each day, then compare it with your first week.

Be honest about the evidence. The checking limit has study support. The Microsoft figures come from Microsoft 365 usage, not a random sample of all workers. The 2025 telemetry also excludes education and EU tenants. Writing Tools, templates, and scheduled sends are practical, but no source here shows they cut writing time.

If your slowest emails are about code, start with the thread. Ask Lazur to explain the thread out loud before you open the reply box. For more on protecting focus between messages, read how to recover focus after interruptions while coding on Mac. For dictation in developer tools, see AI dictation for developers.