Presentation Deck: Managerial Decision Making & Problem Solving
I. Introduction to Decision Making & Problem Solving
1. Role in Management & Career Advancement
The Heart of Management:
Decision making is not just one of a manager's duties; it is the core driver behind all four classical management functions:
Planning: Deciding long-term objectives, market positioning, and resource allocation.
Organizing: Deciding structural hierarchy, team division, and delegation of authority.
Leading: Deciding how to motivate employees, resolve conflict, and manage change.
Controlling: Deciding performance metrics, benchmarks, and corrective actions when performance strays.
The Career Advancement Driver:
In entry-level roles, professionals are judged on technical execution (e.g., writing code, generating reports). As you move into management, your career trajectory is determined by decision quality under ambiguity.
Good managers frame complex problems efficiently.
Great managers make sound strategic choices under incomplete information and high stakes.
Business Example (Netflix):
When Reed Hastings decided to pivot Netflix from DVD mailers to online streaming in 2007 (and later to original content creation with House of Cards in 2013), it was a career-defining and company-redefining decision. It required balancing immense cash burn with uncertain future subscriber adoption.
2. General Problem-Solving Guidelines: A Step-by-Step Approach
Problem-solving is a structured process to go from an undesirable current state to a target state.
┌─────────────────────────┐ ┌─────────────────────────┐ ┌─────────────────────────┐
│ 1. Define Root Cause │ ──► │ 2. Multi-Perspective │ ──► │ 3. Evaluate │
│ (Symptom vs. Root) │ │ Brainstorming │ │ Constraints │
└─────────────────────────┘ └─────────────────────────┘ └─────────────────────────┘
│
┌─────────────────────────┐ ┌─────────────────────────┐ │
│ 5. Post-Implementation │ ◄── │ 4. Execution & │ ◄────────────────┘
│ Audit & Review │ │ Change Management │
└─────────────────────────┘ └─────────────────────────┘
Step 1: Define the Problem Clearly (Symptom vs. Root Cause)
The Trap: Treating symptoms acts as a temporary bandage; the problem will inevitably resurface.
The Tool: Use the 5 Whys Methodology (developed by Sakichi Toyoda for Toyota) or the Ishikawa (Fishbone) Diagram to drill down to the primary cause.
Real-World Scenario:
Symptom: "Our customer service response time increased by 40%."
Superficial Fix: Hire 10 more support agents (expensive and wasteful).
Root Cause Analysis (5 Whys): Response time is high Support agents are overwhelmed Agents spend 80% of their time answering simple password resets The self-service portal link was removed in the last software update.
Actual Root Cause Solution: Restore and redesign the self-service portal link.
Step 2: View Problems from Multiple Perspectives
Cognitive Diversity: Avoid "groupthink" and departmental siloing.
An operational decision shouldn't just involve engineers; it requires financial valuation, legal compliance input, and user experience (UX) insights.
Technique: Use Edward de Bono's Six Thinking Hats (Emotional, Logical, Creative, Optimistic, Risk-oriented, Process-oriented) during group sessions.
Step 3: Evaluate Solutions Against Constraints
Every business operates within boundaries. Potential solutions must be filtered through hard constraints:
Financial: Return on Investment (ROI), payback period, cash flow limits.
Temporal: Time-to-market and operational downtime.
Resource/Capacity: Talent availability, bandwidth, existing IT infrastructure.
Regulatory/Legal: GDPR compliance, labor laws, safety standards.
Step 4: Implement the Chosen Solution
A decision is useless without execution. Implementation requires clear project management: defining key performance indicators (KPIs), setting milestones, assigning single-point owners (RACI matrix), and actively managing organizational change.
Step 5: Re-examine the Solution Post-Implementation
The Feedback Loop: Establish a formal post-mortem or audit 30 to 90 days after rollout. Did the decision produce the expected results? Were there unintended negative consequences?
Oral Speaker Notes (Section I):
"When presenting this section, emphasize that managers who fail often confuse symptoms with root causes. Remind the audience that a quick fix today usually creates a bigger emergency tomorrow. Always highlight the 5 Whys tool as a practical takeaway!"
II. The Eight Steps in the Decision-Making Process
Decision making is an ongoing, systematic process—not a single, spontaneous eureka moment.
[1] Identify Problem ──► [2] Identify Criteria ──► [3] Weight Criteria ──► [4] Develop Alternatives
│
[8] Evaluate Results ◄── [7] Implement Choice ◄── [6] Select Option ◄── [5] Analyze Options ◄┘
Deep Dive with a Concrete Business Scenario
Scenario: A regional logistics company needs to purchase a new fleet of delivery vans to support growing operations.
Step 1: Identify a Problem
Definition: Discrepancy between an existing state (inefficient, costly old fleet breaking down) and a desired state (reliable, cost-effective, low-emission fleet).
Trigger: Maintenance costs surged by 35% this year, and delayed deliveries caused customer churn to hit 8%.
Step 2: Identify Decision Criteria
Definition: Identifying the factors that will determine the final choice.
Fleet Example Criteria:
Purchase Cost / Lease Price
Fuel Efficiency / Energy Consumption (EV vs. Gas)
Cargo Capacity / Volume
Warranty & Maintenance Package
Vehicle Safety Features & Reliability Ratings
Step 3: Allocate Weights to Criteria
Not all criteria are created equal. Assign a weight scale (e.g., 1 to 10) based on strategic priorities.
Decision Criterion
Assigned Weight (W)
Strategic Justification
Vehicle Safety & Reliability
10
High priority to minimize liability and downtime.
Cargo Capacity
8
Essential to maximize packages per route.
Fuel / Energy Efficiency
7
Direct impact on recurring operating expenditure.
Purchase Price / Lease Rate
5
Important, but financing options make this secondary to long-term efficiency.
Warranty & Maintenance
4
Managed partly by an in-house fleet maintenance team.
Step 4: Develop Alternatives
Generate a list of viable solutions without evaluation. Premature evaluation stifles creative brainstorming.
Option A: Traditional Diesel Vans (Brand X)
Option B: Fully Electric Vehicles / EVs (Brand Y)
Option C: Hybrid Fleet Models (Brand Z)
Option D: Outsource delivery logistics entirely to a third-party partner (3PL)
Step 5: Analyze Alternatives
Evaluate each alternative on a scale of 1 to 10 for every criterion, then multiply by the criteria weight score (SW).
TotalScoreforAlternative=(RatingiWeighti)
Calculated Example for Option B (Electric Vehicles):
Safety/Reliability: 910=90
Cargo Capacity: 78=56
Energy Efficiency: 107=70
Purchase Price: 45=20 (High upfront cost)
Warranty: 84=32
Total Score (Option B) = 268 Points
Step 6: Select an Alternative
Select the alternative with the highest calculated total score.
Outcome: Option B (Electric Vehicles) achieves a score of 268, outperforming Option A (210) and Option C (242).
Step 7: Implement the Alternative
Finalize lease contracts, install EV charging stations across regional hubs, schedule driver training sessions, and transition delivery schedules.
Step 8: Evaluate Decision Effectiveness
Track key performance metrics after 6 months:
Did fuel/charging operating costs drop as projected?
Did vehicle breakdown rates decrease?
Did on-time delivery percentages recover to target levels?
If metrics fail to improve, re-evaluate: was the criteria weighting wrong, or was execution flawed?
III. Approaches to Managerial Decision Making
Managers make decisions using four distinct operational models, ranging from pure logic to gut feelings and data science.
DECISION APPROACHES
┌───────────────────────┬────────────────────────┬────────────────────────┬────────────────────────┐
│ RATIONALITY │ BOUNDED RATIONALITY │ INTUITION │ EVIDENCE-BASED MANAGEMENT
│ (Theoretical Ideal) │ (Practical Reality) │ (Pattern Recognition)│ (Data + Context) │
└───────────────────────┴────────────────────────┴────────────────────────┴────────────────────────┘
1. Classical Rationality vs. Bounded Rationality
Classical Rationality (The Theoretical Ideal)
Core Assumptions:
The problem is clear and unambiguous.
The decision maker has 100% complete information (knows all potential alternatives and exact future outcomes).
The decision maker possesses no emotional biases and acts with complete logic.
Goal is single-minded: Maximize organizational economic value.
Managerial Reality: Extremely rare in real-world business due to dynamic market conditions, time pressure, and cognitive bandwidth limitations.
Bounded Rationality (Herbert Simon’s Model - The Operational Standard)
Concept introduced by Nobel laureate Herbert Simon. Managers strive to be rational, but their rationality is constrained (bounded) by information overload, time constraints, and human cognitive processing limits.
Traditional Rationality: Search ALL Options ──► Identify OPTIMAL Choice ──► MAXIMIZE
Bounded Rationality: Search FEW Options ──► Identify ACCEPTABLE Choice ──► SATISFICE
Satisficing (Satisfy + Suffice):
Instead of spending infinite time searching for the mathematically perfect choice, managers settle for a solution that is "good enough"—it meets their baseline functional criteria.
Example: When hiring a sales representative under tight timelines, a manager accepts a strong candidate who meets 85% of job requirements rather than keeping the position vacant for 6 months to find a flawless candidate.
Escalation of Commitment:
A major psychological trap within bounded rationality: an increased commitment to a previous decision despite clear evidence that it is failing.
Root Drivers: Ego protection, fear of public failure, and the fallacious desire to recover sunk costs.
Real-World Case: Concorde (Supersonic Jet) project. The British and French governments continued funding the project for decades despite knowing it had no commercial viability, simply because they had already invested vast political and financial capital.
2. Intuition in Decision Making
Intuition is not magic, superstition, or random guessing. It is unconscious pattern recognition based on years of accumulated experience and domain expertise.
5 ASPECTS OF INTUITION
┌───────────────────────┬────────────────────────┬────────────────────────┬────────────────────────┐
│ Experience-Based │ Affect-Initiated │ Cognitive-Based │ Subconscious Processing│
│ (Past mistakes/wins) │ (Emotions & feelings) │ (Knowledge & training) │ (Deep data synthesis)│
└───────────────────────┴────────────────────────┴────────────────────────┴────────────────────────┘
│
▼
Values/Ethics-Based Choices
Experience-Based Decisions: Made using past successes, failures, or repeating market cycles.
Affect-Initiated Decisions: Driven by feelings, gut instinct, or emotional intelligence.
Cognitive-Based Decisions: Driven by deep technical skills, training, and specialized domain knowledge.
Subconscious Processing: Synthesizing complex data, subtle body language, or environmental signals below conscious awareness.
Values or Ethics-Based Decisions: Guided by deeply ingrained personal values or corporate ethics standards.
Business Example: A veteran venture capitalist (VC) like Peter Thiel reads pitch decks every day. When meeting founders, they can make a multi-million dollar investment decision in under 30 minutes. This "gut feeling" is actually cognitive and experience-based intuition processing thousands of pitch variables unconsciously.
3. Evidence-Based Management (EBMgt)
Evidence-Based Management forces decision makers to complement intuition and traditional habits with empirical research and real-time data.
THE 4 PILLARS OF EBMgt
│
┌───────────────────┬─────────────┴─────────────┬───────────────────┐
▼ ▼ ▼ ▼
Practitioner External Evidence Stakeholder Organizational
Expertise (Scientific Studies) Values Context
Pillar 1: Practitioner Expertise: The skills, judgment, and past experience of the manager.
Pillar 2: External Evidence: Scientific research studies, industry benchmarks, and rigorous external market data.
Pillar 3: Stakeholder Values & Concerns: Ethical considerations and preferences of customers, staff, shareholders, and local communities.
Pillar 4: Organizational Context: Unique internal circumstances, corporate culture, resource limits, and strategic goals.
Business Example (Google's "Project Oxygen"):
Instead of relying on conventional wisdom or executive opinion about what makes a great manager, Google gathered thousands of performance reviews, feedback surveys, and exit interviews. Using analytics, they identified the 8 specific behaviors of top managers (e.g., "Is a good coach," "Empowers team and does not micromanage"), completely transforming their internal leadership training programs based on empirical internal data.
