View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making Radar |  Agile Specification by Example |  Operations 5 Whys |  Agile Example Mapping |
|---|---|---|---|---|
Purposedifferent | When capabilities, maturity levels, or market positions need to be compared across several dimensions, overview is easily lost. Radar brings different characteristics into a shared picture and shows patterns faster than tables do. | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | 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 story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-2 h | 60-90 min pro Feature | 15-30 min | 30-60 min |
Participantsdifferent | 2-10 | 3-6 | 2-6 | 3-7 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Radar Map, Capability Scores, Action Areas | Example Table, Acceptance Tests | Root cause notes, Countermeasures | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | AssessmentPortfolioCapability | AgileRequirementsExamplesBehavior-Driven Development | Root causeIncidentLeanProblem solving | Behavior-Driven DevelopmentRequirementsExamplesRefinement |