Business Communication

The Professional Communication Context

Business communication differs from personal communication in key ways:

  • Purpose-driven: Focused on objectives and outcomes
  • Hierarchical: Power dynamics and organizational structure matter
  • Documented: Often needs to be in writing
  • Reputation-building: Every interaction shapes your professional brand
  • Multi-audience: Often communicating to various stakeholders

The Core Principles

1. Professionalism

What it means:

  • Respectful and courteous tone
  • Appropriate formality level
  • Reliability and follow-through
  • Emotional regulation
  • Proper grammar and presentation

Red flags:

  • Overly casual language in formal settings
  • Emotional outbursts
  • Gossip and complaints
  • Poor grammar or typos
  • Missing deadlines without communication

2. Clarity and Brevity

Business professionals are busy. Get to the point.

Poor: "I hope this email finds you well. I wanted to reach out to touch base about the marketing campaign we discussed in passing a few weeks ago when we ran into each other in the hallway. I've been thinking about it and had some ideas I wanted to share when you have a chance."

Better: "Quick question about the marketing campaign: I have three ideas to share. Do you have 15 minutes this week to discuss?"

3. Strategic Thinking

Consider:

  • Who needs this information?
  • What action do I want them to take?
  • What's the best format (email, meeting, call, message)?
  • What's the appropriate timing?
  • What are the politics at play?

Email Communication

Email Structure

Subject Line:

  • Specific and actionable
  • "Request: Design review by Friday"
  • "Decision needed: Q4 budget allocation"
  • NOT "Hi" or "Quick question"

Opening:

  • Formal: "Dear [Name]" or "Hello [Name]"
  • Standard: "Hi [Name]"
  • Casual (internal): "Hey [Name]" or "[Name],"

Body:

  • Lead with the purpose/ask
  • Provide necessary context
  • Use bullets or numbers for multiple points
  • One topic per email when possible

Closing:

  • Clear call to action or next steps
  • Appropriate sign-off
  • Full signature with contact info

The Bottom Line on Top (BLOT)

Start with the conclusion, then provide supporting details.

Poor structure:

  • Long background
  • All the context
  • History of the issue
  • Finally, what you need (if they're still reading)

BLOT structure:

  • What you need: "I need approval for $5K to hire a contractor"
  • Why: "Our developer is out unexpectedly"
  • Context: "Project deadline is in 3 weeks"
  • Action: "Can you approve by EOD tomorrow?"

Email Tone

Professional formality scale:

Very Formal (executives, external, first contact):

  • "Dear Ms. Johnson,"
  • "I hope this message finds you well."
  • "I would appreciate your consideration of..."
  • "Thank you for your time and attention."
  • "Sincerely,"

Standard Professional (colleagues, routine business):

  • "Hi Sarah,"
  • "I wanted to follow up on..."
  • "Could you please..."
  • "Thanks,"
  • "Best,"

Casual (close colleagues, internal team):

  • "Hey team,"
  • "Quick question about..."
  • "Can you...?"
  • "Thanks!"
  • "Cheers,"

Match the formality of the person emailing you.

Email Red Flags

Avoid:

  • "Sorry to bother you, but..."
  • "Just following up..." (after just 1 day)
  • "Per my last email..." (passive aggressive)
  • "As I said before..." (condescending)
  • ALL CAPS (shouting)
  • Excessive exclamation points!!!
  • Emojis in formal communication
  • Unclear subject lines
  • Reply all unnecessarily

Meeting Communication

Before the Meeting

As organizer:

  • Clear agenda sent in advance
  • Required vs. optional attendees
  • Pre-reads shared with enough time
  • Clear start/end times
  • Meeting objective stated

As participant:

  • Review agenda and materials
  • Prepare questions or input
  • Know your role (present, decide, inform)

Meeting Roles

Organizer:

  • Starts on time
  • Follows agenda
  • Manages time
  • Ensures participation
  • Captures decisions and action items

Presenter:

  • Prepared materials
  • Clear key points
  • Engaging delivery
  • Handles questions well

Participant:

  • Active listening
  • Relevant contributions
  • Respectful of time
  • Follows up on action items

Meeting Etiquette

Do:

  • Arrive on time (or 2 minutes early)
  • Mute when not speaking (virtual)
  • Video on for important meetings (virtual)
  • Take notes
  • Contribute meaningfully
  • Stay off phone/email
  • Follow the agenda

Don't:

  • Interrupt speakers
  • Dominate the conversation
  • Side conversations
  • Multitask visibly
  • Show up unprepared
  • Leave early without notice

Speaking Up in Meetings

How to interject:

  • Wait for natural pause
  • "Can I add something here?"
  • "That's a good point. I'd also like to mention..."
  • "Building on what Sarah said..."

Disagreeing in meetings:

  • "I see it differently. Here's why..."
  • "That's one approach. Another option might be..."
  • "I have concerns about that. Can we discuss X?"
  • NOT "That won't work" or "That's wrong"

Reading the Room

Pay attention to:

  • Energy level (engaged vs. checked out)
  • Time remaining (speeding up vs. deep dive)
  • Power dynamics (who defers to whom)
  • Decision-making style (consensus vs. authority)
  • Tension or disagreement (address vs. table)

Presenting to Leadership

What Executives Want

  1. Bottom line first: conclusion, then supporting data
  2. Options with recommendations: Not just problems
  3. Clear ask: What decision or action you need
  4. Risk awareness: What could go wrong
  5. Data-backed: Numbers and evidence
  6. Brevity: Respect their time

The Executive Brief Format

Opening (30 seconds):

  • The situation
  • Why it matters
  • What you're asking for

Body (2-3 minutes):

  • Key data points (3-5 max)
  • Options considered
  • Your recommendation with rationale

Closing (30 seconds):

  • Specific ask
  • Timeline
  • Next steps

Always prepare for:

  • Tough questions
  • Skepticism
  • Push for more data
  • Different perspectives

Speaking to Authority

Do:

  • Be confident but humble
  • Have data ready
  • Acknowledge limitations
  • Respect their time
  • Follow their lead on formality

Don't:

  • Ramble or over-explain
  • Get defensive
  • Make excuses
  • Overpromise
  • Surprise them with bad news

Managing Up

Communicating with Your Boss

Understand their preferences:

  • Detail level (high-level vs. deep dive)
  • Communication mode (email, chat, face-to-face)
  • Update frequency (daily, weekly, as-needed)
  • Decision-making style (data, intuition, consensus)

Provide solutions, not just problems:

Poor: "The client is unhappy with the timeline."

Better: "The client requested a two-week extension. I see three options: 1) Extend timeline, 2) Reduce scope, 3) Add resources. I recommend option 1 because [reasons]. What do you think?"

The Update Email

Keep your boss informed without overwhelming:

Template:

Subject: [Project Name] — Weekly Update

Status: On track / At risk / Blocked

Completed this week:
• [Key accomplishment 1]
• [Key accomplishment 2]

Next week:
• [Priority 1]
• [Priority 2]

Blockers/Concerns:
• [Issue 1] — Need [specific help]

Questions/Decisions needed:
• [Question 1]

Managing Down

Communicating with Your Team

As a leader, communicate:

  • Clearly: Expectations and objectives
  • Consistently: Regular check-ins
  • Transparently: Share context and reasoning
  • Supportively: Show you're invested in their success
  • Appreciatively: Recognize contributions

Delegating Effectively

The 5 W's of delegation:

  • What needs to be done (specific outcome)
  • Why it matters (context and importance)
  • Who is responsible (clear owner)
  • When it's due (realistic deadline)
  • Where to find resources (tools, people, info)

Example: "I need you to create a customer survey (what) to understand why our NPS dropped last quarter (why). You'll own this end-to-end (who). The draft should be ready by next Friday (when). Sarah in marketing has survey templates you can use (where). Questions?"

Giving Feedback

Use the SBI Model:

  • Situation: "In yesterday's client meeting..."
  • Behavior: "You interrupted the client twice..."
  • Impact: "They seemed frustrated and cut the meeting short."

Then collaborate:

  • "What happened from your perspective?"
  • "How can we prevent this next time?"
  • "What support do you need?"

Cross-Functional Communication

Working with Other Departments

Common challenges:

  • Different priorities
  • Different jargon
  • Different metrics of success
  • Different working styles

Strategies:

  • Learn their language and priorities
  • Explain your needs in their context
  • Find mutual benefits
  • Build relationships proactively
  • Respect their constraints

Example: Poor: "Marketing needs the product launched by June."

Better: "Marketing has customer commitments for June. If we miss that, it impacts revenue by X and customer trust. What would it take to hit a June launch, even if it's MVP scope?"

Crisis Communication

When Things Go Wrong

Principles:

  • Speed: Respond quickly
  • Transparency: Be honest about what you know and don't know
  • Accountability: Own your part
  • Action: What you're doing to fix it
  • Updates: Keep people informed

Crisis communication template:

Subject: [Issue] — Status Update

What happened:
[Brief factual description]

Impact:
[Who/what is affected]

What we're doing:
[Immediate actions taken]

Next steps:
[Plan moving forward]

Timeline:
[When you'll provide next update]

Delivering Bad News

The framework:

  1. State facts directly: Don't bury the lead
  2. Take responsibility: If appropriate
  3. Explain what happened: Briefly
  4. Outline the plan: Next steps
  5. Be available: For questions and concerns

Example: "The project will be two weeks late. This is on me. I underestimated the testing phase. We've added resources and have a plan to deliver by the new date of [X]. I'll send daily updates. I'm sorry for the impact this has on your plans."

Networking Internally

Building Professional Relationships

Strategies:

  • Coffee chats: 30-minute informal conversations
  • Lunch invites: Get to know colleagues
  • Cross-team projects: Visibility and collaboration
  • Help others: Be a resource without expecting immediate return
  • Remember details: Personal and professional

Asking for Help

The request format:

  1. Context: Why you're reaching out
  2. Specific ask: Exactly what you need
  3. Time required: How much of their time
  4. Value exchange: What's in it for them (if anything)

Example: "Hi James, I'm working on the Q4 strategy and know you've done this before. Would you have 20 minutes this week to share what worked well and what you'd avoid? Happy to return the favor however I can."

Professional Boundaries

Knowing What to Share

Safe topics:

  • Weekend activities
  • Hobbies and interests
  • Family in general terms
  • Professional goals
  • Industry trends

Risky topics:

  • Politics and religion
  • Salary details
  • Office gossip
  • Romantic relationships at work
  • Health issues (detailed)
  • Financial problems

Use judgment based on relationship depth and company culture.

Communication Styles at Work

Adapt to Different Styles

Analytical:

  • Want data and logic
  • Time to process
  • Written communication
  • Details matter

Driver:

  • Want bottom line
  • Quick decisions
  • Brief and direct
  • Results-focused

Expressive:

  • Want vision and energy
  • Brainstorming
  • Stories and examples
  • Big picture

Amiable:

  • Want relationship first
  • Consensus and harmony
  • Personal connection
  • Team impact

Strategy: Identify their style and adapt your communication.

Quick Reference: Professional Communication Checklist

Before communicating:

  • [ ] Clear objective
  • [ ] Right medium (email, meeting, call)
  • [ ] Right audience
  • [ ] Right timing
  • [ ] Key message prepared

During communication:

  • [ ] Professional tone
  • [ ] Clear and concise
  • [ ] Active listening
  • [ ] Reading the room
  • [ ] Managing emotions

After communication:

  • [ ] Follow up in writing if needed
  • [ ] Complete action items
  • [ ] Update stakeholders
  • [ ] Document decisions

Common Mistakes

MistakeImpactFix
Too much casualAppears unprofessionalMatch formality to context
Too formalSeems stiff or distantRelax when appropriate
No follow-throughDamages credibilityDo what you say
Surprise escalationBreaks trustLoop in boss before escalating
Complaining upSeems negativeBring solutions
Taking creditLoses team trustShare credit generously
Avoiding conflictIssues festerAddress issues early

Key Takeaways

  1. BLOT (Bottom Line On Top): Lead with the conclusion
  2. Match the medium to the message: Important = face-to-face
  3. Manage up effectively: Solutions, not problems
  4. Build relationships proactively: Before you need them
  5. Adapt to your audience: Different styles need different approaches
  6. Document important communication: Cover yourself professionally
  7. Respond to everything: Even if just to acknowledge
  8. Professional != Cold: Be warm while being professional

Next Steps

Enhance specific business skills: