Decision Method
Scenario Analysis for Teams
Think through best case, worst case, and realistic outcomes before you commit. Understand the range of possibilities for every option.
What is a Scenario Analysis?
Scenario Analysis is a decision-making method where you think through three possible outcomes for each option: the best case (everything goes right), the worst case (everything goes wrong), and the likely scenario (what will most probably happen).
Most teams only think about the expected outcome. Scenario Analysis makes you deal with uncertainty: What if this goes better than expected? What if it goes worse? What's the most probable outcome?
By mapping out all three scenarios, you can identify options where even the worst case is acceptable, and avoid options where the worst case is catastrophic, even if the best case looks amazing.
When to use Scenario Analysis
- The decision involves significant uncertainty or risk
- You need to stress-test an option before committing resources
- The team is overconfident or overly pessimistic about an option
- You want to prepare contingency plans for different outcomes
- The worst-case scenario could be very costly or irreversible
- You need to communicate risks and opportunities to stakeholders
Step-by-step guide
- 1
Define the option
Clearly state the option you're analyzing. Be specific about scope, timeline, and what 'going forward' means. Example: 'Launch the premium tier in Q3 with 3 new features.'
- 2
Describe the Best Case
What happens if everything goes right? Think about ideal market conditions, flawless execution, and favorable external factors. Be specific about outcomes: revenue, users, timeline, impact.
- 3
Describe the Worst Case
What happens if everything goes wrong? Consider technical failures, market rejection, competitive responses, and resource constraints. Be honest about the real downside.
- 4
Describe the Likely Scenario
What will most likely happen given what you know today? Account for typical delays, average market response, and realistic team capacity. Most decisions play out here.
- 5
Compare and decide
Look at all three scenarios for each option. Can you live with the worst case? Is the likely scenario good enough? Is the best case worth the risk? Choose the option with the best balance of upside and manageable downside.
Pro tip: Write the worst case first. Teams naturally gravitate toward optimism, so starting with risks produces more honest scenario assessments.
Pro tip: Add a 'trigger' to each scenario: What specific event or signal would tell you this scenario is unfolding? This makes the analysis actionable.
Example
A startup is evaluating whether to expand into a new market segment.
Best Case
Strong product-market fit from day one. First enterprise client signs within 6 weeks. Revenue from new segment covers development costs within 4 months. Team morale spikes from early success.
Worst Case
New segment requires major product changes not anticipated. Sales cycle is 6x longer than core market. After 6 months, only 2 trial users, no paying customers. Team is stretched thin, core product quality suffers.
Likely Scenario
Product needs moderate adjustments for the new segment. First paying customer after 3 months. Break-even on development costs after 8 months. Some distraction from core product but manageable with clear priorities.
How to do Scenario Analysis in DecTrack
- 1Create a new decision, add participants, and add the options you want to evaluate
- 2Select Scenarios as the analysis method. You'll see the three-scenario layout (Best, Worst, Likely)
- 3Fill in each scenario with specific, measurable outcomes (revenue, timeline, user numbers)
- 4Publish the decision so participants can vote and discuss in the comments
- 5Compare scenarios across options and finalize the decision
Frequently asked questions
- 2-4 sentences per scenario is enough. Focus on specific, measurable outcomes (revenue, timeline, user numbers) rather than vague descriptions. The goal is to make each scenario concrete enough to evaluate.
- Good. Different team members may have different risk assessments based on their experience. Document both versions and discuss which assumptions are more realistic. This often reveals hidden risks.
- You can, but it's not required. If you do, a common split is: Best Case 10-20%, Likely Scenario 60-70%, Worst Case 10-20%. The main value is in thinking through the scenarios, not in the exact probabilities.
- Yes. In DecTrack, the scenarios are captured and shared with the team. Asynchronous discussion often produces more diverse perspectives than a live workshop. The written format also creates useful risk documentation.
- For low-risk, easily reversible decisions, a simple Pro/Con list is faster and sufficient. Scenario Analysis shines when the decision is hard to reverse, involves significant resources, or has high uncertainty.
Related methods
Pro/Con Analysis
List arguments for and against each option to create a clear basis for discussion. Ideal when the decision is qualitative and you want the whole team involved.
SWOT Analysis
Systematically evaluate Strengths, Weaknesses, Opportunities, and Threats for each option. Gives you the full picture before you commit.
Impact/Effort Matrix
Rate each option by impact and effort to find quick wins and stop wasting resources on low-value work.