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 for Contextual Inquiry.
UX Research
Contextual Inquiry
Paper illustration of an IBIS map with issues, positions and arguments
Knowledge Modeling
IBIS
A paper-based illustration representing Domain Storytelling with its core stages and visible working result.
Knowledge Modeling
Domain Storytelling
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Purposedifferent
When work processes are known only from accounts and the real context stays hidden, Contextual Inquiry makes behavior at the workplace visible. Observation and follow-up questions together show how people actually work, get interrupted, and improvise.IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus.Domain Storytelling translates domain knowledge into a shared narrative of actors, objects, and workflows. It is especially useful when language, rules, and process understanding must be tightly connected.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.
Complexitydifferent
MediumMediumLowLow
Timedifferent
1-3 Wochen1-3 h1-2 h15-45 min
Participantsdifferent
4-12 Beobachtungen2-82-81-3
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopAsync
Outputdifferent
Field Notes, Workflow Insights, Pain PointsIssue Map, Positions, Argument NotesDomain Story, Glossary Notes, Process NarrativeADR File, Decision Log, Rationale
Tagsno overlap
UX researchObservationContext
RationaleKnowledgeDecision
KnowledgeDomain-Driven DesignProcess
ArchitectureRationaleDocumentationGovernance
Add more methods