methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
Paper illustration of Five-Minute VC Check with its method-specific working model.
Business Strategy
5-Minuten VC-Check
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
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.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.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
MediumLowLowLow
Timedifferent
45-90 min5-15 min1-2 Tage15-30 min
Participantsdifferent
2-51-51-42-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
A3 Report, Action Plan, Root Cause AnalysisVC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation stepArchitecture Document, Context View, Runtime View, Deployment ViewRoot cause notes, Countermeasures
Tagsno overlap
LeanProblem solvingCoachingOperations
StartupValidationCompetition
ArchitectureDocumentationCommunication
Root causeIncidentLeanProblem solving
Add more methods