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 branching category tree with a highlighted search path and possible dead ends.
UX Research
Tree Testing
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration for Risk Storming.
Architecture
Risk Storming
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Purposedifferent
When a navigation exists but search paths still fail, tree testing checks findability without visual distraction. The method shows whether labels, levels, and paths really lead to the intended destination.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.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
MediumLowLowLow
Timedifferent
1-2 Tage30 min Setup, dann laufend60-90 min15-45 min
Participantsdifferent
Based on research question1-3 maintaining, briefing for everyone4-121-3
Formatdifferent
AsyncAsyncWorkshopAsync
Outputdifferent
Findability Metrics, Path Analysis, Revised IARAID Log, Status Report SourceAnnotated Diagram, Prioritized Risk List, Action BacklogADR File, Decision Log, Rationale
Tagsno overlap
Information architectureNavigationFindability
RiskTrackingStakeholdersGovernance
RiskArchitectureWorkshopValidation
ArchitectureRationaleDocumentationGovernance
Add more methods