Work World
139,263 views
25 min · 2 min read
7 steps
Advanced

How to improve business writing: emails, reports, and memos

Clear, efficient writing saves time and builds credibility. This guide gives practical, repeatable steps to improve emails, reports, and memos so each document communicates purpose, reduces back-and-forth, and gets results.

Verified by pleasexplain editors
  1. Step 1: Define your purpose first

    Spend 2–5 minutes before writing to name the single main purpose of the message (inform, request, decide, or record). Writing with one clear goal reduces length by 20–50% and makes it easier for readers to act. Note the desired reader action in one sentence at the top of your draft.

    [Illustration: person writing a one-sentence objective on a sticky note placed above a laptop screen]

  2. Step 2: Know your audience

    Identify the reader’s role, knowledge level, and decision power in 1–3 bullet points. Tailor tone and detail — executives need a 1-paragraph summary; analysts need 2–3 supporting data points. Matching content to needs avoids unnecessary explanations and speeds decision-making.

    [Illustration: two silhouettes labeled 'Executive' and 'Analyst' with different document lengths beside them]

  3. Step 3: Start with a clear subject or header

    Compose a subject line or heading of 5–10 words that includes topic and intent (e.g., 'Q2 Budget Decision Needed by May 10'). A precise subject increases open rates and helps recipients prioritize within 3 seconds of scanning their inbox.

    [Illustration: email subject line field showing concise, action-oriented text on a screen]

  4. Step 4: Lead with the main point

    Put the conclusion or request in the first 1–2 sentences or the first paragraph for reports and memos, and in the opening line for emails. Readers often scan for the outcome; front-loading the answer reduces follow-up questions and clarifies expectations.

    [Illustration: document with the first paragraph highlighted and a large checkmark icon nearby]

  5. Step 5: Use concise, structured paragraphs

    Limit paragraphs to 2–4 sentences and use short sentences (12–18 words). Group related ideas into 3–5 bullet points when listing options or steps; this improves readability and memory retention for busy readers.

    [Illustration: page showing short paragraphs and a bulleted list with 3 items]

  6. Step 6: Choose plain, active language

    Prefer active verbs and simple words (e.g., 'Send the report' not 'The report should be sent'). Aim for sentences that are 70–80% active voice to increase clarity and accountability. Avoid jargon unless the audience expects it.

    [Illustration: comparison of two sentences, one in passive voice crossed out and an active version highlighted]

  7. Step 7: End with clear next steps

    Close with specific actions, deadlines, and owners in 1–2 lines (e.g., 'Please review by Thu, May 14; I will finalize on May 16. Owner: Maria.'). This reduces ambiguity and cut down on reminder emails and missed deadlines.

    [Illustration: document footer showing 'Next steps' with date, action, and person columns]


  • Limit emails to 1–2 asks; use separate messages for separate decisions.
  • Set a 10–15 minute timer when drafting short messages to prevent over-editing.
  • Create templates for recurring reports that include standard headings and a 1-paragraph executive summary.
  • Use the subject line for deadlines and actions to increase response speed by up to 30%.
  • Read aloud drafts for 30–60 seconds to catch awkward phrasing and run-on sentences.
  • Keep a personal style sheet with preferred spellings, abbreviations, and approved acronyms to save 1–2 minutes per document.

  • Avoid burying the main point in long background sections; readers may stop before reaching it.
  • Don’t assume tone transfers the same across channels — an email can feel terse; add one polite sentence if unsure.
  • Avoid excessive attachments; summarize key facts in the body and attach only supporting files under 5 MB.
  • Don’t rely solely on spellcheck for clarity; it misses context errors and incorrect words.

Was this guide helpful?