View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Innovation Double Diamond |  Operations Barrier Analysis |  Architecture arc42 |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | For complex problems with a fuzzy situation, the method cleanly separates search space and decision. It first creates breadth in understanding and then focus in elaboration. This brings open questions, problem definition, and solution path into a traceable movement. | For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | Wochen bis Monate | 2-4 h | 1-2 Tage | 15-30 min |
Participantsdifferent | 3-12 | 2-6 | 1-4 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Problem Statement, Solution Options, Prototypes, Deliverables per Phase | Barrier Inventory, Failure Analysis per Barrier, Action Backlog | Architecture Document, Context View, Runtime View, Deployment View | Root cause notes, Countermeasures |
Tagsno overlap | ProcessDivergenceInnovation | Root causeSafetyIncident | ArchitectureDocumentationCommunication | Root causeIncidentLeanProblem solving |