View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Failure Scenario Analysis |  Architecture C4 Model |  Decision Making Assumption Surfacing |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
Purposedifferent | In critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most damage. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-3 h | 1-4 h | 45-90 min | 45-60 min |
Participantsdifferent | 3-8 | 1-5 | 2-8 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Context Diagram, Container Diagram, Component Diagram | Assumption List, Critical Assumptions, Learning Plan | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | FailureResilienceRisk | ArchitectureCommunicationVisualization | AssumptionsRiskDecisionDiscovery | AssumptionsRiskExperimentsValidation |