View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery RAID Log |  Engineering Hypothesis-Driven Troubleshooting |  Facilitation Alignment Mapping |  Business Strategy Business Model Stress Test |
|---|---|---|---|---|
Purposedifferent | 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. | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. | 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 | Low | Medium | Medium | High |
Timedifferent | 30 min Setup, dann laufend | 30-240 min | 1-2 h | Half day |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 1-6 | 4-12 | 3-8 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | RAID Log, Status Report Source | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Alignment Map, Open Issues, Decision Questions | Stress Test Report, Action Plan per Scenario |
Tagsno overlap | RiskTrackingStakeholdersGovernance | TroubleshootingProblem solvingDiagnosis | AlignmentStakeholdersStrategyFacilitation | StrategyBusiness modelRiskDiagnosis |