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 Specification by Example with a method-specific labelled workspace.
Agile
Specification by Example
Paper illustration of a yellow story card, blue rule cards, green example cards and a red question card on a light workspace.
Agile
Example Mapping
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
Purposedifferent
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.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.When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments.
Complexitydifferent
MediumLowMediumHigh
Timedifferent
60-90 min pro Feature30-60 min1-3 h1-4 h
Participantsdifferent
3-63-71-83-8
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Example Table, Acceptance TestsExample Map, Acceptance Criteria, Open QuestionsArgument Map, Evidence Gaps, Decision RationaleChallenge Findings, Risk Register, Mitigation Plan
Tagsno overlap
AgileRequirementsExamplesBehavior-Driven Development
Behavior-Driven DevelopmentRequirementsExamplesRefinement
SensemakingDecisionRationale
RiskDecisionSensemaking
Add more methods