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 two user profile cards with a goal, behavior evidence, and an open research question.
UX Research
Personas
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 Root Cause Tree Analysis
Operations
Root Cause Tree Analysis
Three Amigos method illustration showing its working structure
Agile
Three Amigos
Purposedifferent
When target groups stay too vague and teams talk about the same people differently, personas create a shared, solid picture of usage. Condensed profiles make needs, contexts, and differences tangible enough for decisions.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 a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie.When story, test, and implementation could drift apart, it brings business perspective, engineering, and quality together early. It prevents a story from being read differently only late in the process.
Complexitydifferent
MediumLowMediumLow
Timedifferent
1-3 Tage30-60 min1-3 h15-30 min
Participantsdifferent
Internes Team3-72-83
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Persona Profiles, Needs Summary, Scenario NotesExample Map, Acceptance Criteria, Open QuestionsCause Tree, Evidence Notes, CountermeasuresClarified Story, Test Examples, Open Questions
Tagsno overlap
ResearchCustomerSynthesis
Behavior-Driven DevelopmentRequirementsExamplesRefinement
Root causeTreeIncidentQuality
CollaborationBehavior-Driven DevelopmentQualityRefinement
Add more methods