OMBA 101 · Unit 3 of 6
Managerial Problem Solving
Business Foundations and Managerial Thinking
Start unit · 5 lessons →Learning objectives
After completing this unit, you will be able to:
- Turn vague symptoms into well-defined managerial problems
- Decompose problems with issue trees and structured logic
- Form hypotheses, gather evidence, and exercise judgment under uncertainty
- Prioritize problems by impact, urgency, and tractability
- Make defensible decisions when data and time are incomplete
Why this matters
Most management failures are problem-definition failures. Teams optimize the wrong metric, debate opinions instead of tests, or chase urgent noise while strategic fires smolder. Unit 3 gives you the disciplined thinking habit used in consulting, product leadership, and general management: define, decompose, test, decide.
Unit overview
Work through the five lessons below in order. Practice the frameworks on real situations, not hypothetical abstractions.
| # | Lesson | Core idea |
|---|---|---|
| 1 | Turning Symptoms into Well-Defined Problems | From "sales are down" to a testable question |
| 2 | Issue Trees and Structured Decomposition | MECE breakdown of causes and options |
| 3 | Hypotheses, Evidence, and Managerial Judgment | Testable beliefs vs opinions |
| 4 | Prioritizing Problems by Impact and Urgency | Impact/effort and escalation logic |
| 5 | Making Decisions with Incomplete Information | Good enough evidence, reversible bets |
Connection to applied work
Document one real problem from work or school using the full chain: symptom, problem statement, issue tree, top hypotheses, evidence plan, recommendation. This becomes your case analysis draft for OMBA 101.
Practice
- Rewrite a recent complaint from your team as a problem statement with scope, metric, and success criteria.
- Build a three-level issue tree for "customer churn increased."
- List three hypotheses for a live problem and what evidence would falsify each.
- Rank five open problems on impact and urgency; defend the top priority in five sentences.
Knowledge check
- What makes a problem statement managerially useful?
- What does MECE mean in an issue tree?
- How do hypotheses differ from brainstorming ideas?
- When should you act with incomplete information?
- How will Unit 4 connect problem solving to execution?
Key takeaways
- Symptoms are clues; problems are scoped questions with owners.
- Structure reduces debate time and blind spots.
- Judgment combines evidence with explicit assumptions.
- Prioritization is a leadership act, not a calendar accident.
- Finish all five 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 statement is a well-defined problem rather than a symptom or solution?
2. A team splits a revenue miss into {pricing problems, customer dissatisfaction, bad marketing}. What MECE violation is most severe?
3. ClearPeak's NRR fell from 108% to 96%. Level 1 identity split shows gross churn moved −8 points, expansion −1, contraction −1. Which branch should dominate investigation?
4. RidgeLine OTIF fell 7.1 points. Data show warehouse processing explains 61% of misses while suppliers explain 19%. What is the managerial lesson?
5. Per the Pyramid Principle, how should you present analysis to executives?
6. A team scores a mobile checkout fix at Impact 9, Confidence 9, Ease 8 (ICE product 648) versus an ML homepage project at 8, 3, 2 (product 48). Why does ICE include Confidence?
7. In Eisenhower's urgency vs importance matrix, where should strategic prevention work (e.g., fixing onboarding before scaling sales) typically land?
8. When deciding with incomplete information, which approach best preserves decision quality?