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 |  Architecture Request for Comments |  Delivery RAID Log |  Decision Making Pre-Mortem |
|---|---|---|---|---|
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. | 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-3 h | 1-3 Wochen vom Draft bis zur Entscheidung | 30 min Setup, dann laufend | 20–45 min |
Participantsdifferent | 2-8 | 3-20 Reviewer | 1-3 maintaining, briefing for everyone | Small cross-functional group |
Formatdifferent | Workshop + async | Async | Async | Workshop |
Outputdifferent | Gap Matrix, Action Plan, Risk Notes | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | RAID Log, Status Report Source | Risk list, Mitigation plan, Assumption log |
Tagsno overlap | StrategyAnalysisPlanning | ArchitectureDecisionAsyncGovernance | RiskTrackingStakeholdersGovernance | RiskDecisionFailurePlanning |