OMBA 101 · Unit 5 of 6
Business Communication
Business Foundations and Managerial Thinking
Start unit · 5 lessons →Learning objectives
After completing this unit, you will be able to:
- Write executive memos with clear context, options, and recommendations
- Present recommendations to decision makers with structure and credibility
- Use data to support arguments without overwhelming non-technical audiences
- Communicate risk and uncertainty honestly and usefully
- Adapt the same core message to different stakeholders
Why this matters
The best analysis fails if the audience cannot act on it. Unit 5 builds the communication skills that separate trusted advisors from smart people who are ignored: clarity, brevity, appropriate evidence, and stakeholder awareness. These skills compound across every later MBA course and career role.
Unit overview
Work through the five lessons below in order. Draft real documents as you go; do not only read.
| # | Lesson | Core idea |
|---|---|---|
| 1 | Writing Clear Executive Memos | BLUF, structure, and decision-ready prose |
| 2 | Presenting Recommendations to Decision Makers | Narrative arc and Q&A readiness |
| 3 | Using Data Without Overwhelming the Audience | One chart, one point |
| 4 | Communicating Risk and Uncertainty | Ranges, scenarios, and honest limits |
| 5 | Adapting a Message to Stakeholders | Same facts, different frames |
Connection to applied work
Produce a two-page executive memo recommending one action on your anchor company problem from Units 1-3. This is a direct draft of your OMBA 101 executive memo deliverable.
Practice
- Rewrite a long email into a one-page memo with recommendation upfront.
- Build a five-slide outline for a decision meeting (no slides required, just headlines).
- Take one dataset or metric and design a single exhibit that supports a claim.
- Rewrite the same recommendation for a CFO vs a product lead (audience shift).
Knowledge check
- What belongs in the first paragraph of an executive memo?
- How do you present a recommendation without hiding tradeoffs?
- When does more data hurt communication?
- How should managers state uncertainty without sounding weak?
- What changes when the audience changes?
Key takeaways
- Communication is part of analysis, not packaging after the fact.
- Decision makers want recommendations, options, and risks, not data dumps.
- Credibility comes from structure and intellectual honesty.
- Stakeholder literacy is a core managerial skill.
- Finish lessons before unit assessments.
Unit assessment
Complete each section below. Score 80%+ on the quiz to finish this unit's assessment.
Exercises
Apply what you learned in this unit with structured practice.
Deliverable
300–500 word analysis document saved to your portfolio under OMBA 101.
Rubric
- • Framework applied correctly (not just named)
- • Specific evidence from a real example
- • Clear recommendation with tradeoffs acknowledged
- • Professional writing with source citation
Deliverable
Problem solutions + 150-word reflection in your OMBA 101 workbook.
Rubric
- • Attempted all practice items before checking answers
- • Honest reflection on errors
- • Identifies a specific review action
Memo / written deliverable
Write a concise managerial deliverable for this unit.
Deliverable
One-page PDF memo uploaded to your portfolio.
Rubric
- • SCR structure is clear in first 30 seconds of reading
- • Recommendation is specific and actionable
- • Evidence supports the conclusion (not just opinion)
- • Concise: no filler paragraphs
Knowledge quiz
Check your understanding before marking the unit complete.
1. Which opening paragraph best follows BLUF for an executive memo?
2. In SCR structure, what does the Complication section answer?
3. Why should a BLUF paragraph name the main tradeoff even when it weakens the author's case?
4. When presenting recommendations live, what habit best respects executive attention?
5. You have twelve charts for a CFO review. Which principle from 'using data without overwhelming the audience' applies?
6. How should you communicate forecast uncertainty to decision makers?
7. The same vendor consolidation story is shared with the CFO and frontline support agents. What must change between versions?
8. Which element is missing from a weak headcount memo that lists 17 Jira tickets and team biography?