Writing for Work

Professional Stakes

Work writing has consequences.

The email that gets ignored or acted on. The proposal that wins or loses. The report that builds or damages your reputation. The message that creates clarity or confusion.

Most professionals write daily but few received training. This chapter covers the work writing that matters most.

Email

The Email Problem

Too many emails. Too much noise. Too little attention.

Your email competes with dozens of others. It will be read quickly — or not at all.

The Effective Email Formula

Subject line: Specific, actionable, honest

Bad: "Update" Good: "Q3 Budget Revision — Need Approval by Friday"

First line: The main point. Don't bury it.

Body: Details needed to act, nothing more.

Close: Clear next step.

Email Lengths

Quick reply: 1-3 sentences. No greeting needed.

Standard: 5-10 sentences. Get to the point fast.

Detailed: Only when genuinely necessary. Consider whether another format works better.

Tone in Email

Email lacks vocal cues. What sounds professional to you might sound cold to them.

Warmer: "Hope you're well" / "Thanks for sending this" / "I appreciate the quick response"

Direct isn't rude: "I need this by Friday" is clear. "If you could possibly get this to me by Friday that would be great" is waffling.

Find the balance for your workplace culture.

AI Prompt: Email Draft

Draft an email.

To: [Who]
Purpose: [What you want to accomplish]
Tone: [Formal/casual/urgent/etc.]
Key points:
- [Point 1]
- [Point 2]
Context: [Any background needed]
Desired action: [What you want them to do]

Keep it concise.

AI Prompt: Email Improvement

Improve this email:

[Your draft]

Make it:
- Clearer
- More concise
- More likely to get the response I want
- Appropriate tone for [context]

Reports and Documents

The Executive Summary

Decision-makers read the summary. Maybe nothing else.

Include:

  • Main finding or recommendation
  • Key supporting points (3-5)
  • Implications or next steps

Length: One page or less. Usually 1-3 paragraphs.

Write it last: Even though it comes first.

Document Structure

For reports:

  1. Executive summary
  2. Background/context
  3. Analysis/findings
  4. Discussion/implications
  5. Recommendations
  6. Appendices (supporting data)

For memos:

  1. Purpose statement
  2. Background (brief)
  3. Key points
  4. Recommendation/action

Scanability

Readers skim. Help them:

  • Clear headings
  • Short paragraphs
  • Bullet points for lists
  • Bold for key terms
  • White space

They should get the gist from scanning.

AI Prompt: Report Structure

Help me structure a report on [topic].

Purpose: [What it needs to accomplish]
Audience: [Who will read it]
Length target: [Pages]
Key findings: [What you need to convey]

Create an outline with sections and key points in each.

Proposals and Pitches

What Proposals Need

To win, proposals must:

  • Understand the reader's problem
  • Offer a credible solution
  • Demonstrate why you're the right choice
  • Make action easy

Proposal Structure

1. Understanding the problem Show you get what they're facing. This builds credibility.

2. Your solution What you're proposing. Clear and specific.

3. Why this works Evidence, examples, reasoning.

4. Why you Your qualifications, experience, differentiators.

5. Specifics Timeline, pricing, deliverables, terms.

6. Next steps Make action clear and easy.

The Pitch

When you have less time (or space), focus on:

  • The one problem you solve
  • The one thing you offer
  • The one reason to choose you

AI Prompt: Proposal Draft

Help me draft a proposal.

Client: [Who]
Their problem: [What they're facing]
My solution: [What I'm offering]
My credentials: [Why I'm qualified]
Key differentiator: [Why me vs. alternatives]

Create a proposal that addresses their needs and makes a compelling case.

Feedback and Performance Writing

Giving Written Feedback

Written feedback lasts. Be thoughtful.

Structure:

  1. Specific observation (what you saw)
  2. Impact (why it mattered)
  3. Suggestion or question (what next)

Example: "The analysis in your report was thorough and well-sourced (observation). This gave the leadership team confidence in your recommendations (impact). For next time, consider adding an executive summary for those who won't read the full document (suggestion)."

Performance Reviews

What to include:

  • Specific accomplishments with evidence
  • Areas of strength with examples
  • Development areas with concrete suggestions
  • Clear ratings or assessments
  • Forward-looking goals

What to avoid:

  • Vague generalities
  • Surprise criticisms
  • Personal characteristics vs. behaviors
  • Recency bias (only recent events)

AI Prompt: Feedback Draft

Help me write feedback for [person/project].

What went well: [Specifics]
What could improve: [Specifics]
My relationship to them: [Boss/peer/etc.]
Tone needed: [Direct/gentle/formal]

Draft constructive feedback that's specific and actionable.

Slack and Chat

The Chat Medium

Chat is different from email:

  • More casual
  • Faster expectation
  • More interruptive
  • Less structured

Chat Best Practices

Be concise. Chat rewards brevity.

Front-load. Key point first. Details second.

Use threads. Keep conversations organized.

Consider async. Not everything needs immediate response.

Know when to switch. Complex topics → video call. Permanent decisions → email/doc.

AI Prompt: Chat Response

Draft a Slack message.

Context: [Channel/DM, who, situation]
What I need to say: [Your point]
Tone: [Casual/professional]

Keep it appropriate for chat — concise and natural.

Meeting Notes and Summaries

What to Capture

Essential:

  • Decisions made
  • Action items (who, what, when)
  • Key discussion points
  • Follow-up needed

Optional:

  • Attendees
  • Context
  • Detailed discussion

The Summary Format

Meeting: [Name/Date] Attendees: [List]

Decisions:

  • [Decision 1]
  • [Decision 2]

Action Items:

  • [Person]: [Task] by [Date]
  • [Person]: [Task] by [Date]

Key Discussion:

  • [Point 1]
  • [Point 2]

Next Meeting: [Date/Time]

AI Prompt: Meeting Notes

Here are rough notes from a meeting:

[Your rough notes]

Turn these into clean meeting notes with:
- Key decisions
- Action items with owners and dates
- Main discussion points
- Any follow-up needed

Business Cases and Recommendations

The Logic of Business Cases

  1. What's the opportunity or problem?
  2. What are the options?
  3. What do you recommend?
  4. Why? (Evidence and reasoning)
  5. What are the risks?
  6. What's needed to proceed?

Structuring Recommendations

State the recommendation first: "I recommend we proceed with Option B."

Then the reasoning: "This option offers the best balance of cost and timeline..."

Acknowledge tradeoffs: "The main risk is..."

Define next steps: "If approved, we would..."

AI Prompt: Business Case

Help me structure a business case.

The opportunity/problem: [Describe]
Options considered: [List options]
My recommendation: [What you propose]
Key reasons: [Why this option]
Risks: [What could go wrong]
What I need: [Approval/budget/resources]

Create a clear business case structure.

Professional Writing Principles

Clarity Over Cleverness

Work writing exists to accomplish something. Clever writing that obscures meaning fails.

When in doubt, be clear.

Reader-First

What does the reader need to know? What do they want?

Start there, not with what you want to say.

Get to the Point

Business readers are busy. Respect their time.

Lead with the main point. Provide details after.

Make Action Clear

What do you want them to do? Make it obvious and easy.

What's Next

Work writing gets things done. Creative writing does something different — it moves people.

Next chapter: Creative writing — stories, essays, blogs, and writing that resonates.

Editing and RefinementCreative Writing