Written Communication

Mastering the art of clear, persuasive, and professional writing across all business contexts.

Table of Contents

• Principles of Good Writing
• Email Best Practices
• Reports and Documentation
• Instant Messaging and Chat
• Proposals and Persuasive Writing
• Writing for Different Audiences
• Tone and Voice
• Grammar, Punctuation, and Clarity
• Formatting for Readability
• Editing and Proofreading
• Common Writing Mistakes
• Exercises

Principles of Good Writing

The Foundation

Good writing is:

• Clear - Easily understood on first read
• Concise - Uses fewest words possible
• Correct - Accurate facts, grammar, spelling
• Complete - Includes all necessary information
• Compelling - Engages the reader
• Considerate - Respects reader's time and needs

The 7 Cs of Business Writing

The Psychology of Reading

How people read business writing:

1. Scan first - Looking for relevance
2. Skim key points - Headers, bullets, bold
3. Read selectively - Only what matters to them
4. Return if needed - For details later

This means:

• Put important info first (inverted pyramid)
• Use visual hierarchy (headers, bullets)
• Make it skimmable (short paragraphs)
• Easy to find details later (good structure)

The Inverted Pyramid

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
    MOST IMPORTANT INFO
━━━━━━━━━━━━━━━━━━━━━━
  SUPPORTING DETAILS
━━━━━━━━━━━━━━━━
  BACKGROUND
━━━━━━━━━━
 CONTEXT
━━━━━

Example:

❌ Traditional (chronological):
We started researching this problem last month. After 
interviewing customers and analyzing data, we identified 
several issues. We then evaluated options and...

✅ Inverted pyramid:
Recommendation: Switch to Platform B.

Key benefit: Will save $200K annually.

Analysis: We evaluated 3 platforms against our criteria...

Background: This project started when...

Write Like You Talk (But Better)

Conversational business writing:

But maintain professionalism:

• No slang (unless appropriate to audience)
• Complete sentences (mostly)
• Proper grammar
• Thoughtful tone

The "So What?" Test

Every paragraph should pass this test:

Reader asks: "So what? Why does this matter to me?"

Your writing answers that question.

Example:

❌ Doesn't answer "so what?":
"We upgraded to the new server system."

✅ Answers "so what?":
"We upgraded to the new server system. Your files now 
load 3x faster and you'll see fewer crashes."

Less Is More

Word count targets:

Cutting words:

Before (12 words): "I am writing to inform you that I 
will need to cancel"

After (3 words): "I need to cancel"

Savings: 75%

Common word bloat:

Email Best Practices

Email Structure

The perfect email:

SUBJECT: [Action] [Topic] - [Deadline if urgent]

Hi [Name],

[PURPOSE - one sentence]

[CONTEXT - 2-3 sentences if needed]

[DETAILS - bullets preferred]
• Point 1
• Point 2
• Point 3

[ACTION REQUIRED]
Please [specific action] by [deadline].

[CLOSING]

Best regards,
[Your name]

Subject Line Mastery

Formula: Category + Specifics + Urgency

Categories:

• ACTION REQUIRED: Needs response/action
• FYI: Information only
• DECISION NEEDED: Waiting on approval
• QUESTION: Seeking answer
• UPDATE: Status information

Examples:

✅ "ACTION: Q4 Budget approval needed by Friday"
✅ "QUESTION: Client preferences for next meeting?"
✅ "FYI: Office closed Dec 24-25"
✅ "UPDATE: Project Alpha 75% complete"
✅ "DECISION: Choose vendor A or B by Tuesday"

❌ "Quick question"
❌ "Following up"
❌ "Thoughts?"
❌ "Hey"
❌ "Important!!!"

Opening Lines

Get to the point:

❌ "I hope this email finds you well. I wanted to reach 
out because I've been thinking about..."

✅ "I need your input on the Q4 budget."

✅ "Quick question about tomorrow's meeting."

✅ "Here's the report you requested."

When you do need pleasantries:

Professional: "Hope you're well."
Warmer: "Hope you had a great weekend."
After absence: "Welcome back! Hope the vacation was great."
First contact: "Thanks for taking the time to connect."

Email Length and Structure

Optimal length: 50-150 words

Structure rules:

1. One idea per paragraph
2. Max 3-4 sentences per paragraph
3. Use bullets for lists (3+ items)
4. Bold key points sparingly
5. One main ask per email

When you must write longer:

Use sections:

Subject: Q4 Planning - Input Needed

Hi team,

We're planning Q4 and need your input by Friday.

BACKGROUND:
Q3 ended strong with [summary]. Q4 goals are [list].

YOUR INPUT NEEDED:
• Your team's top 3 priorities
• Resource constraints
• Dependencies on other teams

HOW TO RESPOND:
Use this template [link] by Friday 5pm.

TIMELINE:
• Input due: Friday Oct 13
• Planning meeting: Tuesday Oct 17  
• Final plan: Friday Oct 20

Questions? Reply here or ping me on Slack.

Thanks,
Sarah

Reply Etiquette

Response times:

Quick acknowledgment:

When you can't respond fully:

"Got it - will review and respond by [time]."

"Received. I need to check on [thing] and will get 
back to you by [day]."

"Thanks for this. I'm in meetings today but will 
respond tomorrow morning."

Reply All: When and When Not

Use Reply All when:

• Everyone needs your answer
• Confirming attendance (if others tracking)
• Adding relevant info for all
• Continuing group discussion

DO NOT Reply All when:

• Thanking (use direct reply)
• "Me too" or "Agreed" (unnecessary)
• Side conversation (take offline)
• Unsubscribing (defeats the purpose!)

CC and BCC

CC (Carbon Copy):

When NOT to CC:

• To pressure recipient (aggressive)
• To CYA without reason (annoying)
• Entire company (use email list)
• Private conversations (1:1 matters)

BCC (Blind Carbon Copy):

Appropriate uses:

• Large email list (privacy protection)
• Moving people to BCC ("moving to BCC to spare inboxes")
• Documenting for yourself

Never use BCC for:

• Secretly including someone (unethical)
• Monitoring without consent
• Playing politics

Tone in Email

Email lacks vocal tone, so words matter more.

Tone indicators:

Softeners (use wisely):

• "I think..." (weakens strong statements)
• "Perhaps we could..." (suggests rather than demands)
• "What if we..." (collaborative)
• "Help me understand..." (curious, not accusatory)

Avoid over-softening:

❌ "I'm so sorry to bother you, but if you have a chance, 
could you maybe possibly look at this when you get a 
moment, if it's not too much trouble?"

✅ "Could you review this by Friday? Let me know if that 
timing doesn't work."

Common Email Situations

Asking for something:

Hi [Name],

Could you [specific request] by [deadline]?

This will [benefit/reason].

Let me know if you need [any support/resources].

Thanks,
[You]

Saying no:

Hi [Name],

Unfortunately, I can't [request] because [brief reason].

However, I can [alternative if applicable].

Hope this works. Let me know if questions.

Best,
[You]

Following up:

Hi [Name],

Following up on my email from [date] about [topic].

[Restate the ask or question]

Could you let me know by [date]?

Thanks,
[You]

Thanking:

Hi [Name],

Thank you for [specific thing].

This [specific impact/benefit].

I really appreciate [what it means].

Thanks again,
[You]

Apologizing:

Hi [Name],

I apologize for [specific issue].

I take responsibility for [what went wrong].

To fix this, I'll [specific action].

This won't happen again because [prevention plan].

Sorry,
[You]

Reports and Documentation

Report Types

Executive Summary

Purpose: Decision-makers read this and nothing else.

Length: 1 page max (often 1-2 paragraphs)

Include:

1. What is this about? (1 sentence)
2. What's the recommendation/conclusion? (1 sentence)
3. Why? (2-3 key reasons)
4. What happens next? (1 sentence)

Example:

EXECUTIVE SUMMARY

This report evaluates three vendors for our new CRM system. 
I recommend Vendor B.

Key reasons:
• Lowest total cost ($480K vs. $600K+ for others)
• Best integration with our existing systems
• Strongest customer support (24/7 vs. business hours)
• Proven track record with similar companies

Next steps: If approved, we'll begin implementation in 
Q1 with go-live in Q2.

Report Structure

Standard business report:

1. Executive Summary (1 page)

2. Background/Context (1-2 pages)
   - What led to this report
   - Current situation
   - Why it matters

3. Analysis/Findings (3-5 pages)
   - Data collected
   - Options evaluated
   - Pros/cons of each

4. Recommendations (1-2 pages)
   - What should be done
   - Why this choice
   - Implementation plan

5. Conclusion (0.5 page)
   - Summary
   - Call to action

6. Appendices (as needed)
   - Detailed data
   - Supporting documents
   - Technical specifications

Documentation Best Practices

Types of documentation:

1. Process documentation - How to do something
2. Technical documentation - How something works
3. Decision documentation - Why we chose this
4. Onboarding documentation - Getting started guide

Good documentation is:

Discoverable:

• Clear titles
• Good search terms
• Proper categorization
• Linked from relevant places

Current:

• Date stamped
• Regularly reviewed
• Outdated parts marked
• Version controlled

Complete:

• Assumes less knowledge
• Defines terms
• Includes examples
• Covers edge cases

Actionable:

• Step-by-step instructions
• Screenshots if helpful
• Expected outcomes stated
• Troubleshooting included

Process Documentation Template

# [Process Name]

**Last updated:** [Date]
**Owner:** [Name]
**Frequency:** [How often this is done]

## Purpose
Why this process exists and what it accomplishes.

## When to Use
Situations where this process applies.

## Prerequisites
What you need before starting:
• Tool/system access
• Information needed
• Skills required

## Steps

### 1. [Step name]
What to do and why.

**How:**
1. Specific action
2. Specific action
3. Specific action

**Expected result:** What you should see.

**If something goes wrong:** How to troubleshoot.

### 2. [Next step]
[Continue pattern]

## Quality Checks
How to verify you did it right:
• Check 1
• Check 2

## Common Issues

| Problem | Solution |
|---------|----------|
| Issue 1 | How to fix |
| Issue 2 | How to fix |

## Related Resources
• Link to related process
• Link to tool documentation
• Contact for questions

Writing for Scanners

Most people scan, not read.

Make it scannable:

Use headers frequently:

• Every 3-4 paragraphs
• Descriptive (not "Next" - use "Implementation Timeline")
• Hierarchical (H1, H2, H3)

Use bullets for lists:

• 3+ related items = bullet list
• Parallel structure
• Start with action verbs when possible

Use tables for comparisons:

• Options analysis
• Pros/cons
• Features comparison
• Timeline/schedules

Bold key points:

• Sparingly (loses effect if overused)
• Important numbers
• Key conclusions
• Specific actions

Use white space:

• Short paragraphs (3-4 sentences max)
• Space between sections
• Wide margins
• Breathing room

Visual Elements in Reports

When to use:

Visual best practices:

• Caption every visual
• Reference in text ("See Figure 1")
• Keep it simple
• Use consistent colors/style
• Make text readable
• Cite data sources

Instant Messaging and Chat

Chat vs. Email

Use chat/IM when:

Use email when:

Chat Etiquette

Starting conversations:

❌ "Hey"
   [Wait for response]
   [Wait more]
   "Are you there?"

✅ "Hey Sarah - quick question about the Q4 budget. 
   Do you have a minute?"

Ask and tell in one message:

• Don't make people wait for the question
• Include context
• State what you need

Respect status indicators:

• 🟢 Available - OK to message
• 🟡 Away - Wait if not urgent
• 🔴 Busy/DND - Only urgent matters
• 🌙 Off hours - Email instead (non-urgent)

Message length:

Use threads:

• Keep conversations organized
• Don't hijack channels
• Reply in thread, not new message

Emoji and reactions:

Professional use:

• ✅ Acknowledge message
• 👍 Agreement
• 👀 Reviewing
• ✔️ Done
• ❓ Need clarification

Overuse to avoid:

• 😂 (can seem unprofessional)
• 🔥 (can be misinterpreted)
• 💩 (never professional)

Channel Communication

Channel best practices:

Public channels:

• Share information broadly
• Ask questions others might have
• Document decisions
• Build team knowledge

Private channels:

• Sensitive information
• Subset of team
• Focused projects
• Private discussions

Direct messages:

• One-on-one conversations
• Personal matters
• Sensitive feedback
• Private questions

@mentions etiquette:

Don't:

• @channel for non-urgent matters
• @mention in threads (they're already following)
• @mention multiple people for same thing
• @mention off-hours unless urgent

Chat Communication Style

Be clear and direct:

❌ "Thoughts on maybe possibly doing the thing differently?"
✅ "Should we change our approach to X? Here's why I'm asking..."

❌ "IDK, YMMV, but IMHO we should ASAP do XYZ"
✅ "I think we should do XYZ soon. Here's why..."

Provide context:

❌ "Did you send it?"
✅ "Did you send the Q4 budget to Finance?"

❌ "That doesn't work"
✅ "The export feature isn't working - getting error 404"

Group messages:

When asking team:

❌ "Can someone do X?"
   [Everyone waits for someone else]

✅ "Can someone do X? I need it by [time].
   @Sarah or @John - could one of you help?"

Managing Chat Overload

Strategies:

Mute low-priority channels:

• Check on your schedule, not real-time
• Catch up once or twice daily
• Stay in for searching/reference

Set boundaries:

• Turn off notifications after hours
• Use Do Not Disturb
• Communicate your availability

Batch process:

• Set specific times to check Slack
• Don't stay in chat all day
• Focus time = notifications off

Use status:

• Update status when focused
• Set automatic away
• Custom status for context

Organize channels:

• Star important channels
• Section by priority
• Leave inactive channels
• Archive completed projects

Common Chat Mistakes

Proposals and Persuasive Writing

Proposal Structure

Standard proposal:

1. Executive Summary (0.5 page)
   The ask + key benefits

2. Problem Statement (1 page)
   What needs fixing/improving

3. Proposed Solution (2-3 pages)
   Your recommendation
   How it works
   Why it's best

4. Implementation Plan (1-2 pages)
   Timeline
   Resources needed
   Milestones

5. Budget (1 page)
   Costs broken down
   ROI analysis

6. Risks & Mitigation (0.5 page)
   What could go wrong
   How you'll handle it

7. Conclusion (0.5 page)
   Restate recommendation
   Call to action

8. Appendices (as needed)
   Supporting details

Persuasive Writing Framework

AIDA Model:

A - Attention: Hook the reader

Example:
"We're losing $50K monthly to inefficient processes."

I - Interest: Make them want to know more

Example:
"Three teams spend 15 hours/week on manual data entry 
that could be automated."

D - Desire: Show how good it could be

Example:
"Automating this saves 45 hours weekly, freeing the team 
to focus on strategic work and eliminating costly errors."

A - Action: Tell them what to do

Example:
"I need approval to proceed with the automation project. 
See details below."

Making Your Case

The three types of persuasion:

1. Ethos (Credibility):

• Your experience
• Data and research
• Expert opinions
• Track record

2. Pathos (Emotion):

• Impact on people
• Pain of problem
• Vision of better future
• Stories and examples

3. Logos (Logic):

• Data and facts
• Clear reasoning
• Cost-benefit analysis
• Step-by-step logic

Use all three:

Example proposal opening:

"Having led 5 successful automation projects [ETHOS], 
I've seen teams waste hundreds of hours on manual work 
when they could be serving customers [PATHOS]. 

The ROI data is clear: automation pays for itself in 
4 months [LOGOS]."

Handling Objections

Anticipate objections and address them:

Common objections:

Addressing objections structure:

1. Acknowledge: "I understand the concern about cost."

2. Validate: "Budget is tight and we need to spend wisely."

3. Reframe: "Here's why this is actually a cost-saver..."

4. Evidence: [Data showing ROI]

5. Action: "Let's start with a pilot to prove value."

Comparative Analysis

When proposing one option among many:

Create comparison table:

Scoring matrix:

Call to Action

Every proposal needs a clear ask:

Weak CTA:

❌ "Let me know your thoughts"
❌ "Feel free to reach out with questions"
❌ "We should discuss this sometime"

Strong CTA:

✅ "I need approval to proceed by Friday."
✅ "Please choose Option A or B by end of week."
✅ "Let's meet Tuesday to finalize the decision."

CTA components:

1. What - Specific action needed
2. Who - Who needs to do it
3. When - Clear deadline
4. How - How to respond/proceed

Writing for Different Audiences

Audience Analysis

Before writing, ask:

Tailoring to Different Levels

Writing for executives:

Characteristics:

• Limited time
• Strategic thinkers
• Focus on outcomes
• Bottom-line oriented

How to write:

• Lead with recommendation
• Focus on impact and ROI
• Use executive summary
• Appendices for details
• Be brief (2-3 pages max)

Example:

"I recommend investing $100K in tool X. 

This will save $300K annually by reducing manual work.

Implementation takes 6 weeks with low risk."

Writing for managers:

Characteristics:

• Need enough detail to implement
• Care about team impact
• Balance strategic and tactical
• Responsible for execution

How to write:

• More detail than executives
• Clear implementation plan
• Resource requirements
• Timeline and milestones
• Risk management

Example:

"This project requires 3 developers for 6 weeks.

Timeline:
• Week 1-2: Planning and design
• Week 3-4: Development
• Week 5: Testing
• Week 6: Deployment

Risk: Team bandwidth. Mitigation: Defer project Y."

Writing for individual contributors:

Characteristics:

• Need full implementation details
• Doing the actual work
• Care about "how"
• Want clear instructions

How to write:

• Step-by-step instructions
• Technical details
• Examples and screenshots
• Troubleshooting guide
• Complete information

Example:

"To set up the tool:

1. Go to Settings > Integrations
2. Click 'Add Integration'
3. Select 'Tool X' from dropdown
4. Enter API key from [location]
5. Click 'Authorize'

Expected result: Green confirmation message.

If you get error 401: Your API key is invalid. 
Generate new key at..."

Technical vs. Non-Technical Audiences

For technical audiences:

You can:

• Use technical terms
• Assume knowledge
• Go deeper on details
• Be precise and specific
• Use technical diagrams

Example:

"The API uses OAuth 2.0 authentication with JWT tokens. 
Rate limit is 1000 requests/hour with exponential backoff 
on 429 responses."

For non-technical audiences:

You should:

• Define technical terms
• Use analogies
• Focus on what, not how
• Emphasize benefits
• Use simple visuals

Example:

"The system verifies your identity securely (like showing 
ID at airport). You can make 1000 requests per hour. If 
you go over, you'll need to wait a bit before trying again."

Industry-Specific Writing

Each industry has norms:

International Audiences

When writing for global audiences:

Avoid:

• Idioms ("hit it out of the park")
• Cultural references (US sports, holidays)
• Slang and colloquialisms
• Sarcasm (easily misunderstood)

Use:

• Simple, direct language
• Short sentences
• Active voice
• Standard vocabulary
• Universal examples

Be aware:

• Date formats (DD/MM vs. MM/DD)
• Time zones (specify)
• Currency (always specify)
• Measurements (metric vs. imperial)
• Formality levels (vary by culture)

Tone and Voice

Understanding Tone

Tone = How you say what you say

Tone spectrum:

Cold ←──────────────────→ Warm
Formal ←───────────────→ Casual
Direct ←───────────────→ Indirect
Serious ←──────────────→ Playful

Same message, different tones:

Professional Tone Guidelines

Default professional tone:

• Respectful
• Clear
• Warm but not overly casual
• Direct but not blunt
• Positive when possible

Adjusting formality:

Voice Consistency

Voice = Your unique style

Your voice should:

• Be authentic
• Stay consistent
• Match your brand/company
• Suit your role

Finding your voice:

Ask yourself:

• How do I talk in real life?
• What's my personality?
• What's my company's culture?
• What feels natural to write?

Example voices:

Corporate voice:

"We are pleased to announce the Q4 results, which 
exceeded expectations through strong team performance 
and market conditions."

Startup voice:

"Big news! We crushed our Q4 goals thanks to this 
amazing team. Here's what we learned..."

Personal voice:

"I'm excited to share that we had a great Q4. The team 
worked hard and it paid off. A few key learnings..."

Positive vs. Negative Framing

Positive framing = More persuasive

Example transformation:

❌ Negative:
"Unfortunately, we can't implement your feature because 
our team is overloaded and we don't have the budget. 
This will be a problem for Q4."

✅ Positive:
"We'd love to implement your feature. To make it happen 
in Q4, we'd need to either add resources or descope 
another project. Which would you prefer?"

The "Yes, and" vs. "Yes, but"

"Yes, but" = Rejection in disguise

❌ "Yes, but that won't work because..."
❌ "I agree, but we can't..."
❌ "Good idea, but..."

"Yes, and" = Builds on ideas

✅ "Yes, and we could also..."
✅ "I agree, and to make it work we'd need..."
✅ "Good idea, and here's how we could implement it..."

Empathy in Writing

Show you understand their perspective:

Formula: Acknowledge + Validate + Respond

Example 1:
"I understand this is frustrating [acknowledge]. You 
have a valid concern [validate]. Here's what we can 
do [respond]..."

Example 2:
"I know you're under tight deadline pressure [acknowledge]. 
That's a tough position [validate]. Let's see how we can 
help [respond]..."

Empathy phrases:

• "I understand..."
• "That must be..."
• "I can see why..."
• "That makes sense..."
• "I hear you..."

Grammar, Punctuation, and Clarity

Common Grammar Mistakes

Subject-verb agreement:

❌ "The team are meeting"
✅ "The team is meeting" (collective noun = singular)

❌ "Data shows"
✅ "Data show" (data = plural of datum)
   OR "The data shows" (when used as collective)

Pronoun agreement:

❌ "Each person should bring their laptop"
✅ "Each person should bring his or her laptop"
   OR "Everyone should bring their laptops" (now acceptable)

❌ "The company announced their new policy"
✅ "The company announced its new policy"

Tense consistency:

❌ "We analyzed the data and write the report"
✅ "We analyzed the data and wrote the report"
✅ "We analyze the data and write the report"

Punctuation That Matters

Commas (the business impact):

❌ "Let's eat, Grandma!" vs. "Let's eat Grandma!"
❌ "Let's eat the manager" vs. "Let's eat, the manager"

Business example:
"We invited the clients, John and Sarah"
(4 people: clients + John + Sarah)

vs.

"We invited the clients John and Sarah"  
(2 people: both are clients)

Oxford/Serial comma (use it):

❌ "We need marketing, sales and engineering"
   (Ambiguous: is sales and engineering one group?)

✅ "We need marketing, sales, and engineering"
   (Clear: three separate groups)

Semicolons (connect related ideas):

✅ "The project is behind schedule; we need more resources."
✅ "Attendance is mandatory; however, remote participation is allowed."

Don't overuse - usually a period works better.

Colons (introduce lists or explanations):

✅ "We need three things: budget, time, and people."
✅ "Here's the problem: we're losing customers."

❌ "The requirements are: budget, time, and people."
   (Don't put colon after "are")

Dashes (emphasis and interruption):

Em dash (—) no spaces:

✅ "The result—after months of work—exceeded expectations."
✅ "We need approval quickly—by Friday at the latest."

En dash (–) for ranges:

✅ "Q1–Q2 planning"
✅ "Pages 10–15"

Hyphens (-) in compound modifiers:

✅ "decision-making process" (before noun)
✅ "The process of decision making" (after noun, no hyphen)

✅ "full-time employee"
✅ "up-to-date information"

Active vs. Passive Voice

Active voice = Clearer, stronger

❌ Passive: "The report was completed by Sarah."
✅ Active: "Sarah completed the report."

❌ Passive: "Mistakes were made."
✅ Active: "We made mistakes." (takes ownership)

❌ Passive: "It is believed that..."
✅ Active: "We believe..." OR "Research shows..."

When passive is OK:

• Unknown actor: "The system was hacked"
• Unimportant actor: "The meeting is scheduled for Tuesday"
• Diplomatic reasons: "Some concerns were raised" (vs. "You raised concerns")

Clarity Principles

Be specific:

❌ Vague: "We'll do it soon"
✅ Specific: "We'll complete it by Friday"

❌ Vague: "Some customers complained"
✅ Specific: "15 customers (23%) complained"

❌ Vague: "The system is slow"
✅ Specific: "Page load time increased from 2s to 8s"

Use concrete language:

❌ Abstract: "Synergize cross-functional capabilities"
✅ Concrete: "Help teams work together better"

❌ Abstract: "Optimize resource allocation"
✅ Concrete: "Assign people to the right projects"

Avoid hedging (when not needed):

❌ "I think we should probably maybe consider..."
✅ "I recommend..."

❌ "It seems like this might be somewhat important"
✅ "This is important"

But hedge when appropriate:

✅ "The data suggests..." (not proven)
✅ "This could indicate..." (possible interpretation)
✅ "We might consider..." (soft suggestion)

Common Word Confusions

Formatting for Readability

Visual Hierarchy

Use formatting to guide the eye:

# Large Headers (H1) - Main topics
## Medium Headers (H2) - Subtopics  
### Smaller Headers (H3) - Details

**Bold** for key points (use sparingly)
*Italics* for emphasis (even more sparingly)
CAPS FOR ACRONYMS ONLY (not emphasis)

Paragraph Structure

Optimal paragraph length:

• First paragraph: 1-2 sentences (hook)
• Body paragraphs: 3-4 sentences (one idea each)
• Last paragraph: 1-2 sentences (conclusion/CTA)

Bad paragraph:

❌ This is a very long paragraph that contains multiple 
ideas all crammed together without any breaks and it goes 
on and on making it hard to read and process the information 
and by the time you get to the end you've forgotten what 
the beginning was about and it's just exhausting to look 
at and even more exhausting to read...

Good paragraphs:

✅ Start with topic sentence.

Support it with 2-3 related sentences. Keep paragraphs 
focused on one idea. Break when you shift topics.

Start new paragraph for new idea. This makes it scannable 
and easier to digest.

Lists and Bullets

When to use bullets:

• 3 or more related items
• Items of equal importance
• When order doesn't matter
• To break up text

When to use numbered lists:

• Steps in a process
• Ranked items
• When order matters
• Referenced later ("see item 3")

Bullet best practices:

Parallel structure:

❌ Mixed structure:
• Analyze the data
• Writing the report
• The presentation should be created

✅ Parallel structure:
• Analyze the data
• Write the report  
• Create the presentation

Consistent punctuation:

✅ Option 1 (complete sentences):
• This is a complete sentence.
• So is this one.
• And this one too.

✅ Option 2 (fragments, no periods):
• Short phrase
• Another phrase
• One more phrase

❌ Inconsistent:
• Complete sentence.
• Fragment
• Another complete sentence.

White Space

White space = Readability

Create white space with:

• Line breaks between paragraphs
• Space before/after headers
• Margins (don't fill page edge-to-edge)
• Space around images/tables
• Shorter line length (60-80 characters optimal)

Bad (dense):

❌ This document is about quarterly planning.We need to 
complete the following tasks:budget analysis,timeline 
creation,resource allocation,and stakeholder communication.
Each task has specific requirements...

Good (breathing room):

✅ This document is about quarterly planning.

We need to complete:
• Budget analysis
• Timeline creation
• Resource allocation
• Stakeholder communication

Each task has specific requirements...

Fonts and Styling

Font choices:

Don't:

• Mix more than 2 font families
• Use decorative fonts for body text
• Underline (looks like links)
• Use color alone to convey meaning
• WRITE IN ALL CAPS (shouting)
• Overuse bold and italic

Tables for Organization

When to use tables:

• Comparing options
• Structured data
• Specifications
• Schedules/timelines
• Feature comparisons

Table best practices:

✅ Good table:
• Clear headers
• Aligned columns (numbers right, text left)
• Alternating row colors (if long)
• Reasonable column width
• Readable font size

❌ Bad table:
• No headers
• Cramped or stretched
• Too many columns
• Tiny font
• No visual separation

Editing and Proofreading

The Editing Process

Draft → Edit → Polish → Proof → Send

1. Draft (Get it out):

• Write without editing
• Get ideas down
• Don't worry about perfection
• Just finish a first version

2. Edit for structure (Big picture):

• Is the order logical?
• Does each paragraph have a purpose?
• Is anything missing?
• Is anything redundant?
• Does it flow?

3. Edit for clarity (Sentence level):

• Can I say this more simply?
• Are sentences clear?
• Active voice where possible?
• Specific vs. vague?
• Unnecessary words?

4. Polish (Word choice):

• Better word choices?
• Consistent tone?
• Professional language?
• Transitions smooth?

5. Proofread (Errors):

• Spelling
• Grammar
• Punctuation
• Formatting
• Names and numbers

Self-Editing Techniques

The 24-hour rule:

• Write one day
• Edit the next
• Fresh eyes catch more

Read aloud:

• Hear awkward phrasing
• Catch run-on sentences
• Notice repetition
• Find unclear parts

Print it out:

• Different medium = new perspective
• Easier to spot errors
• Can mark up physically

Change the view:

• Different font
• Different size
• Different format
• Different device

Cut 20%:

• Challenge: remove 1 in 5 words
• Forces you to be concise
• Improves clarity
• Strengthens writing

The "so what?" test:

• Read each sentence
• Ask "so what?"
• If you can't answer, cut or clarify

Common Editing Marks

What to cut:

❌ "In order to" → ✅ "To"
❌ "Due to the fact that" → ✅ "Because"
❌ "At this point in time" → ✅ "Now"
❌ "Despite the fact that" → ✅ "Although"
❌ "For the purpose of" → ✅ "To" or "For"
❌ "In the event that" → ✅ "If"
❌ "It is important to note that" → ✅ [delete, just state it]
❌ "I think that..." → ✅ [delete "I think"]

Redundancies to eliminate:

❌ "Past history" (all history is past)
❌ "Future plans" (all plans are future)
❌ "Added bonus" (all bonuses are added)
❌ "End result" (results are at the end)
❌ "Collaborate together" (collaboration is together)
❌ "Consensus of opinion" (consensus is opinion agreement)

Proofreading Checklist

Content:

• [ ] All facts accurate?
• [ ] Names spelled correctly?
• [ ] Numbers correct?
• [ ] Links work?
• [ ] Dates/times correct?

Structure:

• [ ] Logical flow?
• [ ] Paragraphs focused?
• [ ] Transitions smooth?
• [ ] Headers accurate?

Language:

• [ ] No grammar errors?
• [ ] No spelling mistakes?
• [ ] Punctuation correct?
• [ ] Consistent tense?
• [ ] Active voice (mostly)?

Formatting:

• [ ] Consistent font?
• [ ] Headers formatted?
• [ ] Bullets aligned?
• [ ] White space appropriate?
• [ ] Professional appearance?

Tone:

• [ ] Appropriate for audience?
• [ ] Consistent throughout?
• [ ] Professional?
• [ ] Clear and direct?

Getting Feedback

Who to ask:

• Someone who knows the topic (for accuracy)
• Someone who doesn't (for clarity)
• A good writer (for quality)
• Your target audience (for relevance)

What to ask:

"Please review this and tell me:
• Is the purpose clear?
• Is anything confusing?
• Is anything missing?
• What would you change?
• Would this persuade you?"

How to use feedback:

• Thank them
• Don't be defensive
• Consider their perspective
• Look for patterns (multiple people say same thing)
• You decide what to change

Common Writing Mistakes

The Fatal Flaws

1. Burying the lede:

❌ "Following up on our conversation last Tuesday where 
we discussed various options and their implications for 
the project timeline, and after consulting with multiple 
stakeholders and reviewing the budget constraints, I wanted 
to let you know that we need to cancel the project."

✅ "We need to cancel the project.

Here's why: [brief explanation]

Here's what happens next: [plan]"

2. Jargon overload:

❌ "We need to leverage our core competencies to synergize 
cross-functional deliverables and operationalize the go-forward 
strategy for optimal value-add."

✅ "We need to use our strengths to work together better and 
create value for customers."

3. Vague language:

❌ "We'll get back to you soon with some ideas."

✅ "I'll send you 3 options by Friday at 5 PM."

4. Too formal/stiff:

❌ "It has come to my attention that..."

✅ "I noticed that..."

5. Emotional writing:

❌ "I can't believe you missed the deadline AGAIN! This is 
completely unacceptable and I'm extremely frustrated..."

✅ "The report was due Tuesday and I received it Thursday. 
This impacts our client meeting. Let's discuss how to 
prevent this going forward."

Mistakes That Hurt Credibility

Overcommunication Mistakes

Too many messages:

❌ Email 1: "Quick question"
   Email 2: "Are you available?"
   Email 3: "Let me know"
   Email 4: "Thanks"

✅ One email: "Quick question: Are you available for a 
   call this week? Let me know what works. Thanks!"

Too much detail:

❌ "The meeting is at 2pm on Tuesday, which is October 15th, 
in Conference Room B, which is located on the 3rd floor of 
the main building at 123 Main Street, in case you need the 
address..."

✅ "Meeting: Tuesday, Oct 15, 2pm, Conference Room B (3rd floor)"

Undercommunication Mistakes

Too little context:

❌ "Can you send me that thing?"

✅ "Can you send me the Q4 budget spreadsheet we discussed 
   in yesterday's meeting?"

Assuming knowledge:

❌ "Update the TPS reports using the new RFP protocol per 
   the SOW."

✅ "Please update the client reports using our new process 
   (see attached guide) according to the project agreement."

Email-Specific Mistakes

Exercises

Exercise 1: The Cutting Challenge

Objective: Learn to write concisely

1. Take a recent email or document you wrote
2. Count the words
3. Challenge: Cut 30% without losing meaning
4. Techniques to use:
   • Remove redundant phrases
   • Cut unnecessary adjectives
   • Replace wordy phrases with single words
   • Eliminate "I think" and hedging
   • Active voice instead of passive

Example:

Before (42 words):
"I am writing to let you know that we will be having a 
meeting next Tuesday at 2pm in the conference room to 
discuss the budget for the next quarter and we would 
really appreciate it if you could attend."

After (18 words):
"We're meeting Tuesday at 2pm in the conference room 
to discuss Q4 budget. Please attend."

Result: 57% reduction

Your turn: Try with 3 different pieces of writing

Exercise 2: Tone Transformation

Objective: Practice adjusting tone for audience

Take this message and rewrite it for each audience:

Original message: "The Q4 project didn't meet our timeline and went over budget by 20%. Several team members didn't complete their work on time."

Rewrite for:

1. Your boss (upward): Focus: Take responsibility, explain, show plan

2. Your team (downward): Focus: Constructive, learning, moving forward

3. Client (external): Focus: Professional, solutions, reassurance

4. Peer in another department (lateral): Focus: Collaborative, context-sharing

Compare: How does each version differ?

Exercise 3: Clarity Audit

Objective: Identify and fix unclear writing

Find or write a paragraph with clarity issues. Check for:

• [ ] Jargon or acronyms without explanation
• [ ] Vague words (soon, some, things, stuff)
• [ ] Passive voice overuse
• [ ] Complex sentences (25+ words)
• [ ] Abstract language (no concrete examples)
• [ ] Missing context

Rewrite for maximum clarity:

• Define or eliminate jargon
• Replace vague with specific
• Use active voice
• Break long sentences
• Add concrete examples
• Provide necessary context

Exercise 4: Email Effectiveness Analysis

Objective: Evaluate and improve your emails

Review your last 20 sent emails. Score each on:

Calculate average score

Action plan:

• Identify lowest-scoring area
• Create a template for common email types
• Use template for next 10 emails
• Re-score and compare

Exercise 5: Audience Translation

Objective: Practice writing for different audiences

Choose a technical or complex topic you know well

Write 4 versions:

1. For experts (100 words): Use technical language, assume knowledge

2. For informed non-experts (150 words): Some explanation, less jargon

3. For complete beginners (200 words): Simple language, analogies, no assumptions

4. For executives (50 words): Bottom line only, strategic focus

Reflect:

• Which was easiest/hardest?
• What did you learn about your audience awareness?

Exercise 6: Proposal Power Practice

Objective: Write a persuasive proposal

Choose a real change you want to make at work

Write a 1-page proposal including:

1. Problem statement (2-3 sentences)
2. Proposed solution (1 paragraph)
3. Benefits (3 bullets with data)
4. Costs (1-2 sentences)
5. Timeline (brief)
6. Call to action (1 sentence)

Self-edit for:

• Lead with recommendation?
• Specific data and benefits?
• Addresses likely objections?
• Clear action requested?

Bonus: Actually send it

Exercise 7: The Proofreading Game

Objective: Improve error-catching skills

Find a document with intentional errors (create one or find online)

Set a timer for 5 minutes

Catch these types of errors:

• Spelling mistakes
• Grammar errors
• Punctuation problems
• Formatting inconsistencies
• Factual errors
• Unclear sentences

Track:

• How many you caught
• How many you missed
• What types you're good/bad at catching

Practice: Do this weekly to improve

Exercise 8: Active Voice Workout

Objective: Master active voice

Take 10 passive sentences and rewrite as active:

Examples:

❌ "The report was completed by Sarah."
✅ "Sarah completed the report."

❌ "Mistakes were made in the analysis."
✅ "We made mistakes in the analysis."

Find passive voice in your own writing:

• Search for "was," "were," "been," "being"
• Check if you can add "by zombies" after the verb (If it makes sense, it's passive: "The report was completed [by zombies]")

Rewrite: Convert 80% to active voice

Exercise 9: Structure Master

Objective: Practice document structure

Choose a complex topic and create:

1. Executive summary (1 paragraph):

• What is this?
• What's the recommendation?
• Why?
• What's next?

2. Full document (2-3 pages) with:

• Clear sections with headers
• Inverted pyramid structure
• Visual elements (table, bullets)
• Logical flow
• Consistent formatting

3. One-pager version:

• Condense to key points only
• Bullet-heavy
• Scannable in 60 seconds

Reflect:

• Which was hardest to write?
• Could someone understand from executive summary alone?
• Is the one-pager truly standalone?

Exercise 10: Personal Style Guide

Objective: Develop your writing standards

Create your own reference document:

1. Voice and tone:

• My default tone: _____
• Adjust to _____ for formal situations
• Adjust to _____ for casual situations

2. Common phrases I use:

• Opening emails: _____
• Closing emails: _____
• Making requests: _____
• Saying no: _____

3. Grammar rules I follow:

• Oxford comma: yes/no
• Contractions: yes/no/sometimes
• One space or two after period: _____

4. Templates for:

• Request email
• Update email
• Bad news email
• Thank you email
• Proposal structure

5. Proofreading checklist:

• [ ] My common mistakes to watch for
• [ ] Must-check items before sending

Use this guide for consistency across all your writing

Key Takeaways

Good writing is:

• Clear, concise, and complete
• Structured for skimming
• Appropriate for the audience
• Error-free
• Actionable

Master the basics:

• Email effectiveness
• Report structure
• Professional tone
• Grammar and punctuation
• Editing process

Know your audience:

• Adjust formality
• Adjust depth
• Adjust tone
• Adjust length
• Adjust format

Practice deliberately:

• Every email is practice
• Edit ruthlessly
• Get feedback
• Track improvement
• Build good habits

Writing is thinking:

• Unclear writing = unclear thinking
• Forcing clarity in writing = forcing clarity in thought
• Good writing = clear thinking + good communication

The ability to write well is one of the most valuable professional skills. It scales your influence, documents your ideas, and builds your reputation. Invest time in improving it, and you'll see returns throughout your career.