C1 Level · Professional Communication
Think about this: The average professional receives 121 emails per day. Yet email is often the worst medium for important communication. When should you use email? When should you pick up the phone or schedule a meeting instead?
Email is ideal for:
Email struggles with:
Slack/IM: Quick, collaborative, real-time — good for questions, brainstorms, casual chat. Leaves no formal record.
Email: Formal, documented, searchable — good for decisions, action items, accountability. Slow for back-and-forth.
Meeting: High-bandwidth, synchronous — good for complex discussion, conflict resolution, relationship. Expensive on time.
Reflection question: How many emails in your inbox could have been a Slack message or a 5-minute call instead? What would you lose or gain by switching formats?
Scenario: You need budget approval from your manager to hire a contractor for a 6-month project.
Subject: Budget Request
"Hi, we need to hire someone for the project. Can you approve the budget? The contractor costs $50,000. Let me know asap."
Subject: Budget Approval Needed for Q2 Staffing
"Hi, I'm writing to request approval for a 6-month contract hire to support the client deliverables. The contractor would cost $50,000 total and would allow us to meet our June deadline without overloading the existing team. Can we schedule a quick call to discuss?"
Subject: Q2 Deliverables at Risk Without Staffing Approval
"Hi, the Q2 client deliverables are now at risk due to scope expansion and competing priorities. Our team is at capacity, and we're facing a 3-week timeline. I've identified a contractor with relevant experience who can integrate immediately. Cost is $50,000 for 6 months, against the Q2 budget allocation we discussed in January. This hire mitigates the delay risk and allows the team to deliver quality work on schedule. I've attached a one-pager with the contractor's background and deliverables. Can we align on next steps by Friday?"
For each scenario, rewrite the email to be clearer, more persuasive, and more likely to achieve its goal. Consider context, tone, and what the recipient actually needs to know.
Current email:
"We need more budget for marketing. The current spend isn't enough and we're falling behind competitors. Can you approve an additional $200k? This is important for growth."
Improved version:
"Our Q2 lead generation targets are tracking 28% below forecast due to underinvestment in paid channels. Competitors in our segment are spending 40% more on marketing. Increasing our budget by $200k would allow us to:
This would generate approximately $1.2M in incremental ARR by Q4. I've attached a detailed projection. Can we discuss timing for the budget reallocation?"
Why this works: Frames as a growth/risk issue with metrics, shows ROI, provides evidence of need, makes decision easy with clear next step.
Current email:
"I can't make the meeting on Thursday. I have too much going on. Can we reschedule?"
Improved version:
"I'd like to attend Thursday's sync, but I'm at a critical juncture on the client delivery and can't step away that afternoon. I'm keen to stay looped in on the discussion. Would Tuesday or Wednesday work instead? Alternatively, happy to review notes and circle back async."
Why this works: Explains reason (respect for meeting), shows commitment to topic (keen to stay looped in), offers multiple solutions, presents trade-offs professionally.
Current email:
"Hi, the project update was due last week. Where is it? We need this ASAP. This is holding everyone up."
Improved version:
"I notice the project update hasn't landed yet — it was due last Tuesday and the client is checking in with us today. I understand you may have competing priorities. Can we align on what's blocking this and what support you need to ship it by end of day? The team is waiting on these deliverables to move forward."
Why this works: States fact without blame (notice hasn't landed), shows understanding of competing priorities, offers support, clarifies impact, creates clear timeline without aggression.
Current email:
"[To: colleague, CC: colleague's boss] I can't believe you're still on schedule for the August launch. This project is clearly at risk. We need to escalate this immediately."
Improved version:
"Hi [colleague], we've hit a few obstacles that may impact the August timeline. I'd like to surface these before they become critical:
I think we need a 30-minute alignment call with stakeholders this week to reassess the timeline and identify mitigation options. [Boss], can you help us get that scheduled?"
Why this works: Frames as collaborative problem-solving, not blame. Provides specific issues, proposes solution, brings the boss in as facilitator, not as judge.
Email strips away tone of voice, facial expressions, and body language. The same words can sound angry, cold, or warm depending on how you read them. "Thanks for your input" can be genuine appreciation or cutting dismissal. How do you solve this?
We tend to read emails in the voice of someone we expect to hear from. If you think your manager is annoyed with you, her neutral email sounds cold. If you're stressed, a colleague's question sounds accusatory. This is human nature, not your fault. But awareness helps: write with clarity and warmth to pre-empt misreading.
Email styles vary by culture. In some cultures, directness is valued (German, Dutch). In others, indirectness and relationship-building come first (Japanese, Arabic). Remote work has made this more complex — your team may span 10 time zones and five cultures. A few principles that travel well:
CC'ing someone's boss is a power move that damages trust. Before you CC someone's manager:
The only good reason to CC a manager is if they requested transparency or if the person reports to them and the issue is genuinely unresolved. Frame it as collaboration ("let's bring [manager] in to help us align"), not escalation ("I'm escalating you").
Reflection questions: