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 Lean UX Canvas with its method-specific working model.
UX Design
Lean UX Canvas
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Purposedifferent
The Lean UX Canvas helps clarify user behavior, touchpoints, and concept decisions. It makes assumptions and desired outcomes visible and captures the result as a completed canvas, hypothesis list, and first experiment.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.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.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.
Complexitydifferent
MediumLowLowLow
Timedifferent
2-3 h30 min Setup, dann laufend15-45 min1-2 Tage
Participantsdifferent
3-81-3 maintaining, briefing for everyone1-31-4
Formatdifferent
Workshop + asyncAsyncAsyncWorkshop + async
Outputdifferent
Completed Lean UX Canvas, Hypothesis list, First experimentRAID Log, Status Report SourceADR File, Decision Log, RationaleArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
CanvasHypothesisOutcomesDiscovery
RiskTrackingStakeholdersGovernance
ArchitectureRationaleDocumentationGovernance
ArchitectureDocumentationCommunication
Add more methods