View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Business Strategy GAP Analysis | ![]() Decision Making Pre-Mortem | ![]() Architecture Request for Comments | ![]() Business Strategy Business Model Stress Test |
|---|---|---|---|---|
Purposedifferent | GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing. | In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | A Business Model Stress Test checks how well a business model holds up under pressure and headwinds. It compares strengths, risks, market logic, and courses of action. The result is captured as a stress-test report and action plan per scenario. |
Complexitydifferent | Medium | Low | Medium | High |
Timedifferent | 1-3 h | 20–45 min | 1-3 Wochen vom Draft bis zur Entscheidung | Half day |
Participantsdifferent | 2-8 | Small cross-functional group | 3-20 Reviewer | 3-8 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop |
Outputdifferent | Gap Matrix, Action Plan, Risk Notes | Risk list, Mitigation plan, Assumption log | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Stress Test Report, Action Plan per Scenario |
Tagsno overlap | StrategyAnalysisPlanning | RiskDecisionFailurePlanning | ArchitectureDecisionAsyncGovernance | StrategyBusiness modelRiskDiagnosis |



