View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture C4 Model |  Operations A3 Problem Solving |  Business Strategy 5-Minuten VC-Check |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | 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. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | The 5-Minute VC Check clarifies opportunities and strategic options at the earliest idea stage. It compares problem quality, customer willingness to pay, alternatives, differentiation, and market potential, and captures the result as a VC-check note, go/sharpen/park decision, and risk list. | 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 | Low | Medium | Low | Low |
Timedifferent | 1-4 h | 45-90 min | 5-15 min | 15-30 min |
Participantsdifferent | 1-5 | 2-5 | 1-5 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | A3 Report, Action Plan, Root Cause Analysis | VC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation step | Root cause notes, Countermeasures |
Tagsno overlap | ArchitectureCommunicationVisualization | LeanProblem solvingCoachingOperations | StartupValidationCompetition | Root causeIncidentLeanProblem solving |