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
Six paper cards show a person moving from a problem through a service flow to a completed outcome.
UX Design
Storyboarding
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Purposedifferent
When a usage scenario needs to become understandable early, it condenses situations, context, and flow into a legible sequence. It helps check concept ideas before anything gets built.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.Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question.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.
Complexitydifferent
MediumLowMediumLow
Timedifferent
30-90 min15-45 min1-3 Tage30 min Setup, dann laufend
Participantsdifferent
1-81-31-41-3 maintaining, briefing for everyone
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncAsync
Outputdifferent
Storyboard, Concept Narrative, Testable AssumptionsADR File, Decision Log, RationaleArchitecture Views, Cross-view Notes, RationaleRAID Log, Status Report Source
Tagsno overlap
VisualizationConceptsSequencePrototype
ArchitectureRationaleDocumentationGovernance
DocumentationStakeholdersArchitecture
RiskTrackingStakeholdersGovernance
Add more methods