Strategic Response Scenarios
Exercise 4: Rapid Strategic Decision-Making Under Pressure
How This Exercise Works
Format: Quick-fire decision scenarios (5 minutes each)
Method: Individual reflection → Pair discussion → Group vote
Goal: Apply frameworks automatically under time pressure
For each scenario:
- Read the situation (90 seconds)
- Choose your decision (A, B, or C)
- Discuss with partner (2 minutes)
- Vote and hear rationale (90 seconds)
Scenario 1: Competitive Threat Response
Monday Morning Email from Your CMO:
"Team - urgent situation. Our main competitor just announced they're launching an AI-powered personal shopping assistant. Early reviews are glowing. It recommends products based on style preferences, past purchases, and real-time trends. Customers are calling it 'magical.'
Their stock jumped 8% on the news. Our marketing team is getting questions from press. Board wants to know our response by Friday.
We have three options on the table. Need your strategic input today."
Option A: Fast-Follow Response (6 months)
Approach: License existing AI shopping assistant platform, customize with our brand
- Investment: $800,000
- Timeline: 6 months to launch
- Risk: Medium (proven technology, but fast execution)
- Strategic Position: Maintain parity, don't lose customers
- Expected Impact: Neutral (prevents loss, doesn't create advantage)
Pros:
- Quick market response
- Lower risk (proven platform)
- Maintains competitive position
Cons:
- "Me too" solution lacks differentiation
- Expensive for parity play
- Doesn't create strategic advantage
Option B: Differentiated Innovation (12 months)
Approach: Build proprietary AI that combines shopping assistant with our unique strength - expert stylist knowledge base
- Investment: $1.5M
- Timeline: 12 months to launch
- Risk: High (custom development)
- Strategic Position: Leapfrog with superior offering
- Expected Impact: Positive (potential competitive advantage)
Pros:
- Differentiated offering aligned with brand
- Leverages existing strength (stylist expertise)
- Potential competitive advantage
Cons:
- 6-month lag behind competitor
- Higher risk (custom development)
- Might be over-engineered
Option C: Wait and Watch (0 months)
Approach: Monitor competitor performance, focus resources on other priorities
- Investment: $0 now
- Timeline: Re-evaluate in 6 months
- Risk: High (market share loss potential)
- Strategic Position: Let competitor validate demand first
- Expected Impact: Uncertain (might lose customers, might save wasted investment)
Pros:
- Preserves capital for other initiatives
- Let competitor validate demand and work out issues
- Can learn from their mistakes
Cons:
- Risk losing customers to competitor
- Signals weakness to market
- Harder to catch up later if successful
Your Decision Framework
Consider:
- AI Transformation Matrix: Where does each option sit?
- Fast-follow = Optimize or Enhance?
- Differentiated = Enhance or Transform?
- Innovation Adoption Phase: Are we in Knowledge Building, Pilot, Deployment, or Scaling?
- Three Horizons: Is this H1 (defend core), H2 (build new), or H3 (explore)?
- Risk vs. Reward: What's the cost of being wrong? What's the cost of being late?
Discussion: If you were the CEO, which option would you choose and why?
Scenario 2: Pilot Performance Decision
Quarterly Review - Your AI Initiative Status Report:
"We're 9 months into our 12-month AI-powered demand forecasting pilot (10 stores). Results are mixed:
The Good:
- Forecast accuracy improved from 65% to 78% (target: 85%)
- Stockouts reduced by 25% (target: 40%)
- Inventory carrying costs down 12% (target: 25%)
- Store managers report it's 'somewhat helpful'
The Challenging:
- Implementation took 9 months (planned: 6 months)
- Cost overrun: $1.3M spent (budget: $1.1M)
- Data quality issues required significant cleanup
- Seasonal events (holidays) still forecast poorly
- 3 of 10 stores don't trust system, override recommendations
Decision needed: Scale to 50 stores, pivot approach, or kill project?"
Option A: Scale as Planned
Approach: Deploy to remaining 40 stores despite mixed pilot results
- Investment: $2.5M additional
- Rationale: Pilot shows promise, issues are fixable, committed to board
- Risk: Scaling mediocre results, might waste capital
Pros:
- Deliver on commitment to board
- Economies of scale might improve economics
- Learning curve from pilot reduces deployment risk
Cons:
- Results below targets
- Cost overruns suggest poor estimation
- Scaling problems compounds them
Option B: Pivot the Approach
Approach: Pause scaling, spend 6 months fixing identified issues before deployment
- Investment: $400K additional (problem-solving phase)
- Rationale: Fix root causes before scaling
- Changes:
- Improve holiday/event forecasting
- Enhance change management with store managers
- Refine data quality processes
- Re-pilot with 5 different stores
Pros:
- Address root causes before scaling
- Reduce risk of scaling failure
- Improve target achievement probability
Cons:
- 6-month delay
- Additional cost
- Board expects results
- Competitor might move ahead
Option C: Kill the Project
Approach: Shut down pilot, reallocate resources to other AI initiatives
- Investment: $0 additional (stop losses)
- Rationale: Results don't justify further investment
- Alternative: Fund AI customer service chatbot instead (proven ROI)
Pros:
- Stop throwing good money after bad
- Reallocate to higher-ROI initiative
- Learn from failure, move on
Cons:
- Sunk cost of $1.3M
- Signal failure to organisation
- Lose potential future benefits
- Might be giving up too soon
The Scale/Pivot/Kill Criteria
| Criterion | Scale Signal | Pivot Signal | Kill Signal |
|---|---|---|---|
| ROI Trajectory | Exceeding targets | Below but improving | Negative or flat |
| Technical Feasibility | Proven | Solvable issues | Fundamental flaws |
| Market Readiness | Users embracing | Mixed adoption | Resistance |
| Strategic Fit | Core to strategy | Important but... | No longer priority |
| Competitive Pressure | Must have | Nice to have | Irrelevant |
| Resource Availability | Budgeted | Can fund fixes | Better alternatives |
Our Pilot Scores:
- ROI Trajectory: Below targets but positive trend
- Technical Feasibility: Proven (78% accuracy), but data quality issues
- Market Readiness: Mixed (3 of 10 stores don't trust it)
- Strategic Fit: Aligned with operational excellence strategy
- Competitive Pressure: Not immediate
- Resource Availability: Other initiatives competing
Discussion: Using the criteria table, what would you decide?
Scenario 3: Emerging Technology Investment
Innovation Team Memo - Emerging AI Technology:
"Multi-modal AI models (combining text, images, video) have made breakthrough progress. Early applications are impressive:
- Visual search: Upload photo → find similar products
- Virtual try-on: See clothes on your avatar
- Style advice: AI that understands fashion from images
- Quality inspection: Spot defects from photos
This could be transformational for retail. But it's early. Few enterprise implementations. Technology still evolving rapidly.
Question: Do we invest now to be pioneers, or wait until it matures?"
Option A: Pioneer Investment (18-24 months)
Approach: Partner with AI research lab, co-develop retail-specific multi-modal AI
- Investment: $2M over 2 years
- Potential Outcome: First-mover advantage, proprietary IP, brand leadership
- Risk: Very High (technology might not mature, wasted investment)
Pros:
- Potential competitive advantage
- Brand positioning as innovator
- Shape technology to retail needs
- IP ownership
Cons:
- Expensive "R&D" cost
- Technology might not work
- Long timeline to value
- Might be too early
Option B: Fast-Follower Position (12 months)
Approach: Monitor technology closely, pilot with vendor platforms when available
- Investment: $500K (pilot budget, reserved but not spent yet)
- Potential Outcome: Implement proven approaches, avoid pioneer mistakes
- Risk: Medium (might miss first-mover advantage)
Pros:
- Lower risk (let others validate)
- Lower cost
- Learn from pioneer mistakes
- More mature technology
Cons:
- No competitive advantage
- Might miss innovation window
- "Me too" positioning
Option C: Wait Until Mainstream (24+ months)
Approach: Add to "watch list," revisit when technology is proven and mature
- Investment: $0 now
- Potential Outcome: Adopt commodity technology when it's standard
- Risk: Low (proven technology) but might be too late for advantage
Pros:
- Lowest risk
- Lowest cost
- Proven technology
- Clear ROI case
Cons:
- Definitely no competitive advantage
- Might be requirement by then, not differentiator
- Long wait
The Innovation Timing Decision
Consider:
- Strategic Importance: How critical is this capability?
- Core to competitive position → Pioneer
- Important but not critical → Fast-Follower
- Nice to have → Wait
- Risk Tolerance: What's your organisation's innovation appetite?
- High tolerance, innovation culture → Pioneer
- Balanced, pragmatic → Fast-Follower
- Risk-averse, efficiency-focused → Wait
- Resources: Do you have capital and talent to pioneer?
- Deep pockets, AI talent → Can pioneer
- Moderate resources → Fast-follower fits
- Resource-constrained → Must wait
- Competitive Context: What are competitors doing?
- No one moving → Option to pioneer
- 1-2 pioneers → Fast-follow window
- Everyone moving → Must catch up
Three Horizons Lens:
- Pioneer Investment = Horizon 3 (transformational, long-term)
- Fast-Follower = Horizon 2 (emerging opportunity)
- Wait Until Mainstream = Horizon 1 (optimize with proven tech)
Discussion: Which option aligns with your organisation's strategy?
Key Learning
Frameworks become decision-making muscle memory. You're now using them automatically under time pressure - exactly what you need when facing real strategic decisions Monday morning.