View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Operations A3 Problem Solving | ![]() Architecture arc42 | ![]() Business Strategy 5-Minuten VC-Check | ![]() Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 | Medium | Low | Low | Low |
Timedifferent | 45-90 min | 1-2 Tage | 5-15 min | 15-30 min |
Participantsdifferent | 2-5 | 1-4 | 1-5 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | A3 Report, Action Plan, Root Cause Analysis | Architecture Document, Context View, Runtime View, Deployment View | VC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation step | Root cause notes, Countermeasures |
Tagsno overlap | LeanProblem solvingCoachingOperations | ArchitectureDocumentationCommunication | StartupValidationCompetition | Root causeIncidentLeanProblem solving |



