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
Paper illustration of Design Charrette with its method-specific working model.
Innovation
Design Charrette
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
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 Root Cause Analysis.
Operations
Root Cause Analysis
Purposedifferent
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.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.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.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
MediumHighLowMedium
Timedifferent
Halber Tag bis mehrere Tage2-6 h15-30 min1-4 h
Participantsdifferent
10-503-102-63-8
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Sketches and Concepts, Consolidated Solution Sketch, Prioritized DirectionFMEA Table, Risk Priority, Mitigation ActionsRoot cause notes, CountermeasuresProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
BrainstormingWorkshopCollaborationIdeation
RiskQualityOperationsRoot cause
Root causeIncidentLeanProblem solving
Root causeProblem solvingQualityIncident
Add more methods