View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Goal Question Metric |  Operations A3 Problem Solving |  Facilitation Stakeholder Mapping |
|---|---|---|---|
Purposedifferent | 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 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. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 90-180 min | 45-90 min | 60–90 min |
Participantsdifferent | 3-6 | 2-5 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | GQM Table, Metric Profiles | A3 Report, Action Plan, Root Cause Analysis | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | MetricsMeasurementEngineeringAlignment | LeanProblem solvingCoachingOperations | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
