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
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
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
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.ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.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.
Complexitydifferent
MediumMediumHighLow
Timedifferent
45-90 min2–4 h review as a planning range; preparation and evaluation additional2-6 h15-30 min
Participantsdifferent
2-5Designers, developers as users, and facilitation3-102-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
A3 Report, Action Plan, Root Cause AnalysisPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsFMEA Table, Risk Priority, Mitigation ActionsRoot cause notes, Countermeasures
Tagsno overlap
LeanProblem solvingCoachingOperations
ArchitectureEngineeringFeedbackValidationTasks
RiskQualityOperationsRoot cause
Root causeIncidentLeanProblem solving
Add more methods