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
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration for Risk Storming.
Architecture
Risk Storming
Purposedifferent
In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures.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.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.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
LowMediumHighLow
Timedifferent
20–45 min1-3 Tage1-4 Wochen60-90 min
Participantsdifferent
Small cross-functional group1-41-64-12
Formatdifferent
WorkshopWorkshop + asyncAsyncWorkshop
Outputdifferent
Risk list, Mitigation plan, Assumption logArchitecture Views, Cross-view Notes, RationaleExperiment results, Decision log, Learning summaryAnnotated Diagram, Prioritized Risk List, Action Backlog
Tagsno overlap
RiskDecisionFailurePlanning
DocumentationStakeholdersArchitecture
ExperimentsGrowthAnalyticsValidation
RiskArchitectureWorkshopValidation
Add more methods