Corporate Communication
Communication in corporate isn't about being natural or authentic. It's about being effective. This chapter teaches you to speak the language.
The Corporate Communication Paradox
Say a lot without saying anything. Commit to nothing while seeming committed. Disagree without disagreeing. Say no while saying yes.
Welcome to corporate speak.
Email: Your Most Important Communication Tool
The Anatomy of a Perfect Corporate Email
Subject Line:
- Clear and specific
- Action required if urgent: [ACTION REQUIRED]
- FYI if just informational: [FYI]
- Use tags your company uses
Opening:
- "Hi [Name]," for friendly
- "Hello [Name]," for formal
- Skip greeting for quick replies in threads
Body:
- First sentence: Why you're writing
- Middle: Details, context, information
- End: What you need or next steps
Closing:
- "Thanks," for most situations
- "Best regards," for formal
- "Thanks in advance," when asking for something
- "Best," when neutral
Example:
Subject: [ACTION REQUIRED] Q3 Budget Approval Needed by Friday
Hi Sarah,
I need your approval on the Q3 marketing budget by end-of-day Friday to meet the finance deadline.
Key changes from Q2:
• Increased digital spend by 15% based on ROI data
• Reduced event budget by 20% per your guidance
• Total budget: $150K (within allocated range)
Budget deck attached. Happy to discuss if you have questions.
Can you approve by Friday?
Thanks,
Alex
Why this works:
- Clear subject with urgency indicator
- States need immediately
- Provides key information concisely
- Specific call-to-action
- Polite but direct
Email Best Practices
Timing
- Send during business hours: Even if you work late, schedule send for morning
- Response time: Within 24 hours, faster for urgent
- Urgent: Call or Slack, then email for record
- Friday afternoon: Avoid sending anything requiring immediate action
CC and BCC
- CC: When people need visibility but not action
- Too many CCs: CYA culture or poor boundaries
- BCC: Almost never appropriate in corporate
- Reply All: Use when everyone needs the info, not by default
Common Email Mistakes
1. Novel-length emails
- Problem: No one reads them
- Fix: Use bullet points, be concise, link to longer docs
2. Vague subject lines
- Problem: "Quick question" tells nothing
- Fix: "Question on Q3 Marketing Budget Timeline"
3. Burying the ask
- Problem: Request hidden in paragraph 4
- Fix: State what you need upfront
4. Emotional emails
- Problem: You can't unsend, creates evidence
- Fix: Wait 24 hours, tone down, or call instead
5. No clear action
- Problem: Recipient doesn't know what to do
- Fix: End with specific request or next step
6. Poor formatting
- Problem: Wall of text is unreadable
- Fix: Short paragraphs, bullets, whitespace
The CYA Email
Cover Your Ass = Document important communications
When to send CYA email:
- After verbal decisions
- When you sense political risk
- When instructions are unclear
- Before implementing big changes
- When you want written confirmation
Template:
Subject: Following up on [Topic] Discussion
Hi [Name],
Following up on our conversation about [topic], here's my understanding:
• We agreed to [decision/action]
• Timeline: [dates]
• I'll be responsible for [your part]
• You'll handle [their part]
Please confirm or let me know if I missed anything.
Thanks,
[You]
What this does:
- Creates written record
- Allows them to correct misunderstandings
- Protects you if things go wrong
- Professional, not accusatory
Corporate Speak: The Translation Guide
Common Phrases and What They Mean
| What They Say | What They Mean |
|---|---|
| "Let's circle back" | Not happening now, maybe never |
| "Let's take this offline" | Stop talking about this in this meeting |
| "I'll loop you in" | Maybe I will, maybe I won't |
| "Let's keep this on our radar" | We're not doing anything about it |
| "That's an interesting perspective" | I disagree but won't say it |
| "Let me think about that" | No, but I won't say no directly |
| "We need to socialize this" | Build support before officially proposing |
| "Let's align on this" | We disagree and need to resolve it |
| "Can you provide more color?" | I need details/context |
| "We need buy-in from leadership" | This needs political support to happen |
| "Let's get on the same page" | We're not aligned and that's a problem |
| "I have some concerns" | I'm opposed but being diplomatic |
| "We should level-set" | Our expectations don't match |
| "Let's park that for now" | Not discussing this now |
| "We need to operationalize this" | Turn idea into actual process |
| "That's above my pay grade" | Not my decision, ask someone higher |
| "I'll run this up the flagpole" | I'll ask my boss |
| "We need more bandwidth" | We're too busy/don't have resources |
| "It is what it is" | Accept this; we can't change it |
| "We need to manage expectations" | Lower expectations, we're not delivering |
How to Say Things Diplomatically
| Instead of | Say |
|---|---|
| "That's a terrible idea" | "I have some concerns about that approach" |
| "This won't work" | "I see some challenges we'd need to address" |
| "You're wrong" | "I have a different perspective" |
| "I can't do that" | "Given current priorities, we'd need to deprioritize X to take this on" |
| "That's not my job" | "That's typically handled by [team/person]. Should I connect you?" |
| "You didn't do what you said" | "I was expecting X by Friday. Can we align on the timeline?" |
| "This is stupid" | "Help me understand the rationale here" |
| "No" | "Let me think about that and get back to you" |
How to Disagree Without Being Disagreeable
The Formula:
- Acknowledge their point
- State your concern
- Ask a question or offer alternative
Examples:
Poor: "That timeline is impossible." Better: "I understand the urgency. My concern is quality if we rush. Could we discuss what's non-negotiable versus flexible?"
Poor: "This strategy won't work." Better: "I see what you're trying to achieve. Based on past experience with similar approaches, we faced X challenge. How might we address that?"
Poor: "You're wrong about the data." Better: "Interesting. I'm seeing different numbers on my end. Can we compare our sources to make sure we're looking at the same dataset?"
Meeting Communication
Speaking in Meetings
When to speak:
- You have relevant expertise
- You're asked directly
- You have important information
- You disagree with a decision
- You see a risk others don't
When not to speak:
- Just to hear yourself talk
- You have nothing new to add
- It's not your area
- You're just agreeing (nod instead)
How to speak effectively:
1. Get to the point "I have three concerns about this approach: timeline, resources, and stakeholder buy-in."
2. Use the "headline first" method Start with conclusion, then explain. "I recommend we postpone launch by two weeks. Here's why..."
3. Bring data "Based on last quarter's metrics..." has more impact than "I think..."
4. Make it about the business "This impacts our Q3 revenue target" is better than "I don't like this"
5. Offer solutions "I see the issue with X. What if we tried Y approach instead?"
Meeting Etiquette
Do:
- Arrive on time (or 2 minutes early)
- Come prepared
- Pay attention (close laptop if you can't multitask discretely)
- Take notes
- Follow up on your commitments
- Contribute meaningfully
Don't:
- Show up late without warning
- Dominate conversation
- Check phone obviously
- Side conversations
- Eat loudly
- Interrupt
- Argue aggressively
Reading the Meeting Room
Observe:
- Who speaks first? (Usually most senior)
- Who speaks most? (Not always the leader)
- Who does everyone look to? (Real decision maker)
- Who's ignored? (Low status or respect)
- What creates tension? (Landmines)
- What's not being said? (Real issues often unspoken)
Adapt accordingly:
- Don't speak before senior people if hierarchical culture
- Match the energy and tone of the room
- If everyone's formal, be formal
- If direct disagreement happens, it's safe
- If disagreement is avoided, be diplomatic
Difficult Conversations
The Framework
1. Prepare
- What's the issue?
- What outcome do you want?
- What's their perspective likely?
- What evidence do you have?
- What's your backup plan?
2. Start Right "I want to discuss something that's been on my mind. Do you have 20 minutes?"
3. State the Issue Clearly "I've noticed [specific behavior/issue]. I'm concerned about [specific impact]."
4. Listen Let them respond. Truly listen. Ask questions.
5. Collaborate on Solution "How do you think we should handle this going forward?"
6. Document Send follow-up email summarizing agreement.
Giving Difficult Feedback
The SBI Model: Situation-Behavior-Impact
Structure: "In [situation], when you [specific behavior], the impact was [consequence]."
Example: "In yesterday's client meeting, when you interrupted the client multiple times, it seemed to frustrate them and we lost the opportunity to hear their concerns fully."
Why this works:
- Specific, not general
- Observable behavior, not judgment
- Clear impact, not assumption
Follow with: "Going forward, [desired behavior]. Does that make sense?"
Receiving Difficult Feedback
The temptation: Defend, justify, explain, deflect.
The right response:
- Listen fully: Don't interrupt
- Clarify: "Can you give me a specific example?"
- Acknowledge: "I understand your concern"
- Thank them: "I appreciate you bringing this to my attention"
- Reflect: Consider if it's valid
- Act: If valid, change; if not, note different perception
Do not:
- Get defensive immediately
- Make excuses
- Blame others
- Dismiss their feedback
- Get emotional (in the moment)
Remember: Feedback is a gift, even if poorly delivered. Extract the useful part.
Written Communication Best Practices
Slack / Teams / Chat
Treat it as semi-formal:
- Professional but friendly
- Quick responses okay
- Typos more acceptable than email
- Emojis okay in moderation
- Threads keep things organized
Response expectations:
- During work hours: Within 1-2 hours
- After hours: Next business day
- Urgent: Say "urgent" or call instead
Don't:
- Send "hey" without context (just ask your question)
- Use for complex topics (email or call instead)
- Expect immediate response
- Send confidential/sensitive information
- Have difficult conversations
Documents and Presentations
Documents:
- Executive summary first
- Use clear headers
- Bullet points over paragraphs
- Visual breaks (tables, charts)
- Conclusion with recommendations
Presentations:
- One idea per slide
- Minimal text
- Large fonts
- Visual > text
- Tell a story, don't just present facts
The deck rule: If you're sending it to be read, more text is okay. If you're presenting it, less text is essential.
Communication Styles by Audience
To Your Boss
- Brief and focused
- Solutions not just problems
- Data and facts
- Respect their time
- Proactive updates
To Peers
- Collaborative tone
- Reciprocal relationship
- Informal okay
- Share credit
- Build relationship
To Your Team
- Clear expectations
- Regular feedback
- Transparent when possible
- Supportive tone
- Recognition and praise
To Executives
- Ultra-brief
- Bottom line upfront
- Business impact focus
- Data-driven
- No surprises
- Confidence without arrogance
To Clients/External
- Professional always
- Clear and simple language
- Responsive
- Solution-oriented
- Represent company well
Communication Red Flags
Warning signs of communication trouble:
- You're often misunderstood
- People don't respond to your emails
- You're not invited to important meetings
- Your ideas are dismissed
- People seem annoyed by you
- You get feedback about communication
If you notice these, adjust your approach.
The Communication Matrix
| Situation | Channel | Timing | Tone |
|---|---|---|---|
| Quick question | Slack | Immediate | Casual |
| Formal request | 24-48hr response | Professional | |
| Urgent issue | Call + Email | Immediate | Direct |
| Complex topic | Meeting + Email | Scheduled | Collaborative |
| Difficult feedback | In-person | Planned | Constructive |
| FYI updates | As needed | Informative | |
| Brainstorming | Meeting | Scheduled | Open |
| Decisions | Email + Meeting | Documented | Clear |
Communication Traps to Avoid
1. The Reply All Disaster Don't reply-all to company-wide emails with jokes, questions, or "thanks."
2. The Emotional Email Never send an angry email immediately. Wait 24 hours or call instead.
3. The CC Ambush Don't CC someone's boss on first communication about an issue.
4. The Vague Passive-Aggressive "Per my previous email..." just makes you look petty.
5. The Overshare Don't share personal issues, politics, religion, or controversial topics.
6. The Assumption Don't assume your message was understood. Confirm understanding.
7. The Bad Writing Poor grammar, spelling, or structure damages your credibility.
The Ultimate Communication Rule
Match your communication to your audience, situation, and company culture.
What works in one company fails in another. What works with one manager fails with another. What works in crisis fails in normal times.
Be adaptable.
Remember
Corporate communication is a skill, not a personality trait.
You can learn to:
- Write effective emails
- Speak confidently in meetings
- Give and receive feedback well
- Navigate difficult conversations
- Adapt your style to your audience
Master communication and you'll master corporate success.
Words are your primary tool. Use them well.