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 a yellow story card, blue rule cards, green example cards and a red question card on a light workspace.
Agile
Example Mapping
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
Paper illustration of Acceptance Criteria Workshop with a method-specific labelled workspace.
Agile
Acceptance Criteria Workshop
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Purposedifferent
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.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.When a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update.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.
Complexitydifferent
LowHighLowMedium
Timedifferent
30-60 min1-4 h20-40 min pro Story1-3 h
Participantsdifferent
3-73-83-61-8
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Example Map, Acceptance Criteria, Open QuestionsChallenge Findings, Risk Register, Mitigation PlanAcceptance Criteria, Story UpdateArgument Map, Evidence Gaps, Decision Rationale
Tagsno overlap
Behavior-Driven DevelopmentRequirementsExamplesRefinement
RiskDecisionSensemaking
AgileRequirementsRefinementBehavior-Driven Development
SensemakingDecisionRationale
Add more methods