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
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Paper illustration for Reverse Brainstorming
Innovation
Reverse Brainstorming
Paper illustration of Design Charrette with its method-specific working model.
Innovation
Design Charrette
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Purposedifferent
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.For persistent errors or blockages, the method shifts the view to the opposite of the desired effect. It exposes the mechanics of failure and makes hidden causes easier to grasp. This makes improvement more concrete and the problem clearer.In a tightly timed design process with many participants, the method pools several lines of thinking in a short time. It brings parallel design energy without letting the discussion tip into endless coordination. This quickly produces solid directions for architecture or space.When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.
Complexitydifferent
LowLowMediumMedium
Timedifferent
15-30 min30-60 minHalber Tag bis mehrere Tage1-4 h
Participantsdifferent
2-63-1210-503-8
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Root cause notes, CountermeasuresReverse Ideas, Risk Themes, Solution IdeasSketches and Concepts, Consolidated Solution Sketch, Prioritized DirectionProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
Root causeIncidentLeanProblem solving
BrainstormingIdeationCreativityRisk
BrainstormingWorkshopCollaborationIdeation
Root causeProblem solvingQualityIncident
Add more methods