4.2/5 - (61 votes)

You send a quick “Project update: we are on track for Friday” email and think of it as pure information. But that little message is asking your reader to believe you, trust your timeline, and let you get on with the work.

The myth that only sales emails are persuasive

Most of us sort work writing into two piles. There are the emails that try to convince someone (a pitch, a proposal, a budget request) and the emails that simply report facts.

The writing experts at Purdue OWL, the online writing lab run by Purdue University, reject that split. Their guide to effective workplace writing puts it in four words: “Workplace writing is persuasive.”

A status report, a meeting recap, even a time-off request: each one wants something from the reader. Sometimes it is an action, sometimes an approval, sometimes just understanding. That is persuasion, even if nobody would ever call it a sales email.

What your neutral email is really asking for

Take a time-off request. On the surface, it is just a date range. Underneath, it is trying to convince your manager that the timing works and that nothing will fall apart while you are gone.

Compare these two versions:

Flat: “I will be off from March 4 to March 8.”

Persuasive: “I would like to take March 4 to 8 off. The client report goes out on March 1, and Dana has agreed to cover any questions while I am away.”

Both are polite and free of typos. Only the second one answers the questions your manager is already asking in their head, which makes it much easier to approve.

See also  Why your résumé bullet points sound off even with zero typos

Four things to weigh before you start writing

Purdue recommends looking at four elements before you settle on how to write any workplace document:

  • Purpose: what do you want the reader to do, approve, or understand?
  • Audience: who is the direct reader, and what do they already know?
  • Stakeholders: everyone affected by the document, not only the person in the “To” field.
  • Context: the situation in which the message will actually be read.

Stakeholders are the element people forget most often. The colleague in cc, or the manager who will open the thread next week, is a reader too. If your message only makes sense to the main recipient, it is quietly failing everyone else.

Why one template does not fit every message

This way of thinking rejects the idea of a single model for every document. An email to your boss, a safety report for a technical team, and a memo to the whole company do not share the same audience, context, or stakeholders.

So they should not share the same tone or structure either. Copying the same format into every situation is one of the most common workplace writing habits, and it usually leaves at least one reader working harder than they should.

Purdue frames the fix around how the reader will actually use what you wrote. Its advice is simple: “Identify information readers will need and make that information easily accessible and understandable.”

In practice, that means putting the date, the decision, or the request where nobody can miss it, instead of burying it in the third paragraph.

See also  Skipping the Oxford comma is fine, switching back and forth is not

The one question to ask before you hit send

Before you send anything, even a two-line update, ask yourself one thing: what do I want this person to do or believe after reading it?

If you cannot answer in one sentence, the email is not ready yet. If you can, check that the answer is clearly visible in the message, and that anyone in cc would understand it too.

The rule to remember: there is no such thing as a neutral work email. Every message is asking for something, so make the ask easy to see.