Overview

Lecture URL: https://skill.re/learn/manager/scenario-analysis-and-planning.php

AI FOR MANAGERS CERTIFICATION

Independent AI Application (Level 3) | Independent Decision Support

LECTURE: Scenario Analysis and Planning

Lesson 2.2 | Estimated Duration: ~16 minutes

Welcome to the AI for Managers certification program. I am your instructor, and today we are covering one of the essential lessons in the Independent Decision Support module: Scenario Analysis and Planning.

This is Lesson 2.2 in Level 3, the Independent AI Application track. Whether you are joining us as a new manager finding your footing, a seasoned director refining your approach, or a VP setting strategic direction for your organization, the material in this session is designed to meet you where you are and give you something immediately actionable.

In our previous lesson, we covered Structuring Complex Decisions. Today we build directly on that foundation. If any of those concepts feel uncertain, I would encourage you to revisit that material before we go further.

Before we begin, let me set expectations. This is not a passive lecture. I will ask you to think, to challenge assumptions, and to connect what we discuss to your own work. The managers who get the most out of this program are those who pause, reflect, and apply. So I encourage you to have a notepad ready, whether physical or digital, and to jot down ideas as they come to you.

Let us get started.

Lesson 2.2: Scenario Analysis and Planning

Title & Purpose

Scenario Analysis and Planning teaches you to use AI to model different future scenarios, stress-test

plans against "what if" situations, and understand how sensitive your strategy is to assumptions. AI helps

you run simulations and explore possibilities. You exercise judgment about which scenarios matter, which

risks are worth planning for, and what contingencies make sense. By the end, you'll anticipate challenges

and build adaptive plans rather than brittle ones.

Why This Matters for Managers

Real-world plans encounter reality. Markets shift. Competitors move. Team members leave. Customers behave

differently than expected. Yet many managers plan as if the assumptions will hold.

The challenge: Perfect prediction is impossible. But you can:

• Identify the assumptions your plan depends on
  - Model what happens if key assumptions are wrong
  - Spot which scenarios would break your plan
  - Build contingencies for high-impact risks
  - Plan adaptively rather than rigidly

The AI opportunity: AI excels at:

• Building scenario models (if X changes, then Y happens)
  - Running simulations (what if growth is half what we expect?)
  - Sensitivity analysis (which assumptions matter most?)
  - Exploring outcomes (what does success/failure look like?)
  - Stress-testing plans (what breaks our plan?)

What AI can't do: Decide which scenarios are worth planning for or what contingencies are smart.

That's judgment.

Core Concepts

1. Scenario Architecture

Strong scenario planning includes:

• Base case: Most likely path given current assumptions
  - Upside scenario: What if things go better than we expect?
  - Downside scenario: What if things go worse?
  - Black swan scenario: What if something unexpected happens entirely?
  - Contingency plans: For each scenario, what do we do differently?

1. Assumption Sensitivity

Not all assumptions matter equally:

• High-impact, high-uncertainty: These matter. Plan for them.
  - High-impact, low-uncertainty: These matter but we're confident, so less analysis needed
  - Low-impact, any-uncertainty: Less critical to scenario planning
  - Critical paths: Where a single assumption failure breaks the whole plan

1. Adaptive Planning vs. Brittle Planning

• Brittle plans: Set a course and if assumptions change, you're in trouble
  - Adaptive plans: Set direction with flexibility to adjust based on learning
  - Contingency building: Plan trigger points (if X happens, we pivot)

1. Decision Trees and Branching

Plans branch based on outcomes:

• Scenario A happens -> follow path 1
  - Scenario B happens -> follow path 2
  - Scenario C happens -> follow path 3

Rather than one rigid plan, you're building a decision tree.

1. Learning and Feedback Loops

The best plans include ways to learn:

• Leading indicators that signal whether assumptions are holding
  - Trigger points (if this metric moves, we reassess)
  - Feedback loops (what are we learning that changes the plan?)

Practical Managerial Use Cases

1. Launch planning (new product, new market, new initiative)

• Upside: Takes off faster than expected
  - Downside: Slower adoption, takes 2x longer to scale
  - Wild card: Competitor launches similar product

1. Financial planning (quarterly/annual forecast)

• Upside: Revenue grows faster, churn lower
  - Downside: Economic slowdown, customer delays
  - Wild card: Major customer switches to competitor

1. Team planning (headcount, hiring, growth)

• Upside: Attract great people, retention high
  - Downside: Hiring takes longer, attrition spikes
  - Wild card: Key person leaves

1. Strategic bets (big investment in new direction)

• Upside: Market moves faster than expected, we win
  - Downside: Market stays flat, we've invested for nothing
  - Wild card: Incumbent competitor enters space aggressively

1. Organizational change (restructure, process change, system migration)

• Upside: Smooth transition, improvements immediate
  - Downside: Productivity dip longer than expected, morale issues
  - Wild card: Key people quit during transition

Examples

Example 1: Growth Plan Scenario Analysis

Scenario: You've committed to 40% YoY revenue growth. Your plan assumes:

• Customer acquisition cost (CAC) stays flat
  - Churn stays at 5%
  - Sales conversion improves 20% with new hires
  - No competitive disruption

With AI:

Prompt:

`

Help me stress-test my growth plan. I'm projecting 40% revenue growth based on:

• Current revenue: $10M
  - CAC: $5K, churn: 5%, conversion: 15% -> 18%
  - Sales team growth: +3 reps
  - No major competitive changes

Scenarios I should model:

1. Base case (assumptions hold)
2. CAC increases (market gets competitive)
3. Churn increases (product issues or competition)
4. Conversion improvement doesn't happen (new reps need ramp time)
5. Competitor enters and steals customers

For each scenario, help me:

• Model revenue outcome
  - Identify what operational metrics tell us we're in that scenario
  - What we'd do differently in that scenario
  - When we'd know we need to pivot

`

AI helps you build the model:

`

Base Case Model:

• Target revenue: $14M (40% growth)
  - Assumes existing customer base + new customer growth - churn

Upside Scenario (2x expected growth):

• CAC drops 20% (better product-market fit, viral growth)
  - Churn drops to 3% (strong retention)
  - Conversion hits 22%
  - Potential outcome: $16M+ revenue, problem becomes scaling
  - Leading indicator: CAC lower than expected, viral metrics trending up

Downside Scenario (0% growth):

• CAC rises 30% (market saturation)
  - Churn rises to 8% (competitive pressure)
  - Conversion stays at 15% (no improvement)
  - Potential outcome: $10M revenue (flat), below plan
  - Leading indicator: CAC rising, churn ticking up month-over-month

Competitive Disruption Scenario:

• New competitor launches with superior offering
  - Our churn spikes to 12% for 3 months
  - New customer growth decelerates
  - Potential outcome: $8-9M revenue, temporary crisis
  - Leading indicator: Win-loss analysis shows we're losing to competitor
  - Recovery path: Urgent product improvements, customer success focus

Conversion Failure Scenario (new reps slow to ramp):

• New reps productive at 50% expected (ramp takes 6 months not 3)
  - CAC increases 20% (less efficient targeting while ramping)
  - Overall growth: 15% instead of 40%
  - Leading indicator: Pipeline doesn't grow as expected, sales cycle lengthens

`

Your Plan with Contingencies:

Q1-Q2: Monitor for Scenario Signals

• Track CAC weekly (alert if it rises >15% vs. plan)
  - Track churn by cohort (alert if rising above 5%)
  - Track new rep productivity (alert if below 40% of target at 8-week mark)
  - Competitive intelligence (early warning system for new competitors)

If CAC Rising Scenario:

• Action: Double down on organic/viral channels
  - Timing: Pivot if CAC >$6K (20% above current)
  - Contingency: Scale back new customer acquisition, focus on expansion revenue

If Churn Rising Scenario:

• Action: Customer success interventions, product improvements
  - Timing: Pivot if churn >6% for 2 consecutive months
  - Contingency: Pause growth spending, focus on retention, lower revenue target to $12M

If New Rep Ramp Delayed:

• Action: Accelerated onboarding, pairing with top performers
  - Timing: Decide by month 4 (if at 30% productivity, extend timeline)
  - Contingency: Hire mid-market specialist instead of enterprise rep, adjust quota mix

If Competitor Enters:

• Action: Immediate product audit, competitive positioning
  - Timing: Assess at first sign (lose deal to competitor)
  - Contingency: Invest in differentiation, customer defense, prepare for margin pressure

Dynamic Replanning:

"We'll review monthly. If actual is tracking toward a different scenario, we'll adjust. August checkpoint:

if CAC is up and churn is up, we move to contingency mode. Revenue target becomes $12-13M and we focus

on profitability over growth."

Why this works:

• Makes assumptions explicit
  - Models consequences of assumption failure
  - Identifies leading indicators (early warning signals)
  - Builds trigger points (when to pivot)
  - Prepares contingencies (not caught off guard)

Example 2: Organizational Change Scenario Planning

Scenario: You're merging two teams (20 people total). Plan assumes:

• Smooth integration, no attrition
  - Productivity dip for 4 weeks, then returns to baseline
  - Combined team is more effective than two teams

With AI:

Prompt:

`

I'm planning a team merger. Help me model what could go wrong:

Current state:

• Team A: 10 people, high-performing, tight culture
  - Team B: 10 people, newer team, less established culture
  - Plan: Merge into one team with joint leader (me)

Base case assumptions:

• No attrition
  - 4-week productivity dip, returns to baseline
  - Team A and Team B cultures blend
  - Combined team unlocks synergy

Scenarios to model:

1. High-attrition scenario (people quit because of change)
2. Culture clash scenario (teams don't blend)
3. Productivity dip lasts longer than expected
4. Key person from either team leaves

For each scenario:

• What does it look like?
  - How would we know early that we're in that scenario?
  - What would we do differently?

`

AI helps model outcomes:

`

Base Case: No attrition, 4-week dip, return to baseline

• Risk: Assumes change is smooth and people see value quickly

High-Attrition Scenario (2-3 people leave from each team):

• Impact: 25% capacity loss, continuity issues, survivor morale damaged
  - Leading indicators: Exit interviews cite culture, management, direction
  - Month 1: People mention considering other options
  - Month 2-3: Actual resignations start
  - Recovery: Takes 6+ months to rehire and ramp
  - Better outcomes: Proactive engagement, clear vision of merged team value

Culture Clash Scenario (teams don't integrate):

• Impact: Two teams operating in parallel, synergy never materializes
  - Leading indicators: People self-segregate, different standards, subtle conflicts
  - Month 1: People cluster by old team during meetings/breaks
  - Month 2-4: Conflicts surface in how work gets done
  - Recovery: Either painful integration work or accept two sub-teams
  - Better outcome: Intentional culture building, explicit values alignment

Extended Productivity Dip (8 weeks not 4):

• Impact: Key projects slip, customers notice, pressure to deliver
  - Leading indicators: Ramp-up slower than expected, people still figuring out processes
  - Early signal: After 2 weeks, still high level of questions/confusion
  - Contingency: Extend timelines, bring in external support, pare back scope
  - Prevention: Intensive onboarding, clear processes, paired work initially

Key Person Leaves (e.g., strong engineer quits):

• Impact: Project disruption, knowledge loss, team morale hit
  - Leading indicators: Person quiet in meetings, less engaged, interviewing
  - Contingency: Cross-training, documentation, replacement planning

`

Your Adaptive Plan:

Preparation Phase (Before Merge):

• Individual conversations with each team about rationale and value
  - Identify potential risks and concerns from each team
  - Outline merged team structure, reporting, expectations
  - Communicate: this is change, but here's why it's good

Merge Week 1-2:

• Monitor attrition signals (who's disengaged? Who's exploring options?)
  - Watch for culture clash (are people clustering by old team? Any conflicts?)
  - Check productivity (early indicators of ramp-up speed)
  - Weekly check-ins with key flight risks

If Attrition Risk Emerges:

• Trigger: 1 person mentions leaving, or 3+ disengaged people
  - Action: Immediate one-on-ones, understand concerns, address where possible
  - Decision point: Week 3 (do we see recovery or does risk escalate?)

If Culture Clash Emerges:

• Trigger: Observed clustering by team, different work standards, tensions in meetings
  - Action: Explicit team norms-setting, mixed working groups, shared projects
  - Decision point: Week 4 (are we seeing integration or divergence?)

If Productivity Dip Extends:

• Trigger: After week 4, still high confusion/low output
  - Action: Extend ramp timeline, intensive training, pare back commitments
  - Decision point: Week 6 (are we trending toward baseline recovery?)

If Key Person Signals Exit:

• Trigger: Observed disengagement, or direct "I'm thinking about my next move"
  - Action: Immediate conversation, understand concerns, creative solutions
  - Decision point: Within one week (can we retain them?)

Success Metrics:

• Month 1: No attrition, team feels integrated
  - Month 2: Productivity back to ~80% of baseline, culture issues resolved
  - Month 3: Full productivity, clear merged team identity
  - Month 6: Synergy is real (faster delivery or better quality than two teams)

Anti-Patterns & Misuse Risks

1. Scenario Overload

Risk: You model so many scenarios that you paralyze decision-making.

Mitigation: Focus on high-impact, uncertain scenarios. Ignore low-impact ones.

1. Ignoring the Scenarios You Don't Like

Risk: You model downside scenarios but don't actually plan for them.

Mitigation: For each scenario, build explicit contingencies. Make them real.

1. Overconfidence in Predictions

Risk: AI models give you numbers (15% growth, 8% churn) and you treat them as forecasts.

Mitigation: Scenario planning is about ranges and possibilities, not precise prediction.

1. Contingencies That Never Get Activated

Risk: You plan for scenarios but never actually pivot when they occur.

Mitigation: Set trigger points. When trigger hits, actually pivot. Track what you missed.

1. Static Plans in Dynamic Environment

Risk: You create a 12-month plan and execute it regardless of what you're learning.

Mitigation: Build feedback loops. Reassess quarterly or when key assumptions change.

Human Judgment Checkpoints

Critical moments where you override or adapt:

1. Scenario selection: Which scenarios actually matter? Or are you modeling everything equally?
2. Assumption validity: Which assumptions could realistically be wrong? Which are almost certain?
3. Trigger point setting: When would you actually pivot? Be honest about your threshold.
4. Contingency realism: Are these contingencies actually executable? Or are they fantasy plans?
5. Frequency of reassessment: How often will you actually revisit the plan? Build that in.
6. Tolerance for change: Are you actually willing to change course, or are you committed to the plan

regardless?

Responsible AI Considerations

1. Avoiding False Precision

The risk: AI gives you numbers (15.3% growth) and you treat them as predictions.

Your practice: Scenario planning is about possibilities and ranges. Use AI's numbers as scenarios,

not forecasts.

1. Acknowledging Unpredictability

The risk: You plan for the scenarios you can imagine and miss the ones you can't.

Your practice: Build flexibility into plans. Acknowledge what you don't know. Plan for adaptability,

not perfect prediction.

Practice & Reflection Prompts

1. Pick a plan you're executing. What assumptions does it depend on? Which would change the outcome

if they're wrong? Model those.

1. Scenario contrast: Build base case and downside scenario. What's different? At what point would

you pivot from base to downside planning?

1. Trigger identification: For each scenario, set a trigger (when would you know you're in that scenario?).

Are these triggers measurable? Do you track them?

1. Contingency stress test: For each scenario, what would you actually do? Is it realistic? Could you

execute it fast?

Key Takeaways

• Plans face reality. Scenario planning is about preparing for possibilities, not predicting the

future perfectly.

• Not all scenarios matter equally. Focus on high-impact, uncertain scenarios. Ignore low-impact ones.
  - Trigger points enable adaptation. Without triggers, contingency plans never happen.
  - Leading indicators are actionable. Track metrics that tell you which scenario is unfolding.
  - Contingencies must be real. If you wouldn't actually execute them, don't plan for them.

Terms & Glossary Items

• Scenario modeling: Building out possible future states under different assumptions
  - Sensitivity analysis: Which assumptions matter most? Which changes don't affect the outcome?
  - Trigger point: A decision rule (if X happens, we do Y)
  - Leading indicator: Metric that signals which scenario is unfolding early
  - Contingency plan: What we do if our base case assumptions don't hold
  - Adaptive planning: Building flexibility to adjust as you learn

Related Lessons

• Lesson 2.1: Structuring Complex Decisions -- Where you evaluate options
  - Lesson 2.3: Evidence Gathering and Synthesis -- Where you build assumptions
  - Lesson 2.4: Recommendation Development -- How to communicate plans that include contingencies

[SYNTHESIS AND APPLICATION]

Let us step back and look at the bigger picture of what we have covered in this session on Scenario Analysis and Planning.

The concepts here are not abstract frameworks meant to sit in a binder on your shelf. They are practical tools for the decisions you make every day as a manager. Whether you are leading a small team or a large department, whether you work in technology, finance, healthcare, education, or any other sector, the principles we discussed apply to your work right now.

Here is what I want you to take away from this session:

First, the conceptual understanding. You now have a clearer mental model of scenario analysis and planning and how it fits into the broader landscape of AI-augmented management. This mental model is what allows you to make good decisions rather than reactive ones.

Second, the practical application. We walked through specific scenarios, examples, and frameworks that you can apply in your work this week. Not next quarter. This week. I want you to identify one specific situation in your current work where you can apply what we discussed today.

Third, the judgment dimension. Perhaps most importantly, we discussed when and how to exercise human judgment. AI is a powerful tool, but it requires an informed, thoughtful manager at the helm. That is you. Your judgment, your context awareness, your understanding of your team and your organization, those are irreplaceable.

[REFLECTION EXERCISE]

Before we close, I would like you to spend two minutes, just two minutes, on this reflection:

Think about your work this past week. Identify one task, one decision, one communication where the concepts from today's lesson would have changed your approach. What would you have done differently? What would the outcome have been?

Write that down. That connection between concept and practice is where real learning happens.

[CLOSING REMARKS]

In our next lesson, we will explore Evidence Gathering and Synthesis, which builds directly on what we have covered today. I would encourage you to complete the reflection exercises before moving on, as they will prepare you for the next set of concepts.

This has been Lesson 2.2: Scenario Analysis and Planning, part of the Independent Decision Support module in Level 3: Independent AI Application of the AI for Managers certification.

Remember: the goal is not to know more about AI. The goal is to be a better manager because of how you use AI. Those are very different things, and this program is designed for the latter.

Thank you for your time, your attention, and your commitment to growing as a leader in an AI-transformed workplace. I look forward to our next session together.

END OF TRANSCRIPT

AI for Managers Certification Program

Level 3: Independent AI Application | Independent Decision Support | Lesson 2.2

A SkillsClinic initiative by No Worker Left Behind and The Work Company.

Duration: ~16 minutes | Word Count: ~2524