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 RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
Paper illustration for Risk Storming.
Architecture
Risk Storming
Purposedifferent
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.When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.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 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.
Complexitydifferent
LowHighMediumLow
Timedifferent
30 min Setup, dann laufend1-4 Wochen1-3 Tage60-90 min
Participantsdifferent
1-3 maintaining, briefing for everyone1-61-44-12
Formatdifferent
AsyncAsyncWorkshop + asyncWorkshop
Outputdifferent
RAID Log, Status Report SourceExperiment results, Decision log, Learning summaryArchitecture Views, Cross-view Notes, RationaleAnnotated Diagram, Prioritized Risk List, Action Backlog
Tagsno overlap
RiskTrackingStakeholdersGovernance
ExperimentsGrowthAnalyticsValidation
DocumentationStakeholdersArchitecture
RiskArchitectureWorkshopValidation
Add more methods