Scenario Analysis
Evaluate technical decisions using structured analysis: Tree of Thought branching, multi-dimensional weighted scoring, trade-off matrices, and evidence-based decision frameworks.
Guiding Principle
"Every architectural decision is a trade-off — make trade-offs explicit, weight criteria by stakeholder priorities, and document not just what you chose, but what you rejected and why."
Procedure
Step 1 — Decision Framing
- Define the decision to be made with clear scope boundaries
- Identify decision criteria: technical (performance, scalability, security), business (cost, time, risk), team (skills, hiring, maintainability)
- Weight criteria by stakeholder priority (distribute 100 points across criteria)
- Identify constraints: non-negotiable requirements that eliminate options
- Define evaluation method: scoring scale (1-5), evidence types, confidence levels
Step 2 — Option Generation (Tree of Thought)
- Generate primary options (3-5 distinct approaches)
- For each option, explore sub-branches: implementation variants, phasing strategies
- Identify hybrid options that combine strengths of multiple approaches
- Apply constraint filtering: eliminate options that violate non-negotiable requirements
- Shortlist viable options (3-4) for detailed evaluation
Step 3 — Multi-Dimensional Scoring
- Score each option against each weighted criterion (1-5 scale)
- Tag evidence type per score:
[CODE], [DOC], [BENCHMARK], [INFERENCE], [ASSUMPTION]
- Calculate weighted scores and rank options
- Perform sensitivity analysis: which weight changes would flip the ranking
- Identify the decision boundary: how close are the top options
Step 4 — Decision & Documentation
- Recommend the top option with explicit rationale
- Document trade-offs accepted with the recommended option
- Identify risks and mitigation strategies for the chosen path
- Define reversibility: how easy is it to change this decision later
- Produce an ADR capturing context, decision, alternatives, and consequences
Quality Criteria
- Decision criteria weighted by stakeholder input, not analyst preference
- Every score backed by evidence tag (never unsubstantiated)
- Sensitivity analysis shows the decision is robust under reasonable weight changes
- Rejected alternatives documented with clear rejection rationale
Anti-Patterns
- Analysis paralysis: comparing 10+ options without constraint filtering
- Scoring all criteria equally instead of weighting by priority
- Confirmation bias: scoring the preferred option favorably without evidence
- Making irreversible decisions without considering reversibility cost