
Use AI to stress-test your enterprise software strategy against multiple futures
You'll have 3-4 scenario briefs (each 1-2 pages) describing how your current software investments and AI bets would perform under different market conditions, plus decision rules for each scenario.
What you'll make
Software Strategy Stress Test
- Current State Assessment: dependency map and true costs
- Scenario Analysis: 3+ futures with impact assessments
- Decision Rules: build vs buy criteria for each scenario
- Investment Priorities: ranked opportunities by scenario probability
Submit as a structured document with your dependency map, scenario assessments, and decision framework
The 3 parts
Each part ends with a check you can see.
Map Your True Dependencies
Inventory your actual vendor relationships and calculate the hidden costs of your current software portfolio
Done when
Complete dependency map showing vendor relationships, subprocessors, and true costs including failure risk for top 3-5 systems
Test Against Multiple Futures
Build 3 distinct scenarios for how AI changes software economics and assess how your current investments perform
Done when
3 scenarios with specific impact assessments for your current portfolio — where investments thrive, struggle, or become obsolete
Find Precision Engineering Opportunities
Identify where your organization could build precision solutions instead of forcing business processes into standard platforms
Done when
Ranked list of 3-5 precision engineering opportunities with build vs buy decision criteria for each scenario
Capstone: you put together your Software Strategy Stress Test.
Where this helps
An elective: a single lesson that sits outside rtwo's job certificates and doesn't count toward one.
About this lesson
What you'll be able to do
- Stress-test current software investments against 3+ future scenarios with specific impact assessments
- Calculate true cost of vendor lock-in using dependency mapping and subprocessor analysis
- Distinguish precision engineering opportunities from legacy system optimization traps
- Design decision rules for build vs buy that account for AI engineering capacity changes
Who it's for
- Enterprise architects and IT leaders managing software portfolios
- CTOs and technology executives planning 3-5 year strategies
- Business leaders frustrated with inflexible enterprise systems
What it won't cover
- Specific AI tool implementation guides
- Vendor selection criteria or RFP processes
- Technical architecture patterns or code frameworks
- Budget planning or procurement processes
Skills you'll practise
- Scenario analysis under uncertainty
- Vendor dependency mapping
- Strategic decision-making with incomplete information
- Cost-benefit analysis across multiple futures