View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Alignment Mapping |  Operations Root Cause Analysis |  Engineering Goal Question Metric |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. | 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. | Helps clarify technical problems, hypotheses, and next steps in concrete terms. It breaks a technical problem into testable parts. The result is captured as a GQM table and metric briefs. | 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 | Medium | Medium | Low |
Timedifferent | 1-2 h | 1-4 h | 90-180 min | 15-30 min |
Participantsdifferent | 4-12 | 3-8 | 3-6 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Alignment Map, Open Issues, Decision Questions | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | GQM Table, Metric Profiles | Root cause notes, Countermeasures |
Tagsno overlap | AlignmentStakeholdersStrategyFacilitation | Root causeProblem solvingQualityIncident | MetricsMeasurementEngineeringAlignment | Root causeIncidentLeanProblem solving |