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
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
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Purposedifferent
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.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.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.
Complexitydifferent
MediumLowMediumHigh
Timedifferent
1-3 Tage30 min Setup, dann laufend45-60 min1-4 Wochen
Participantsdifferent
1-41-3 maintaining, briefing for everyone2-81-6
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncAsync
Outputdifferent
Architecture Views, Cross-view Notes, RationaleRAID Log, Status Report SourceAssumption map, Test backlog, Risk rankingExperiment results, Decision log, Learning summary
Tagsno overlap
DocumentationStakeholdersArchitecture
RiskTrackingStakeholdersGovernance
AssumptionsRiskExperimentsValidation
ExperimentsGrowthAnalyticsValidation
Add more methods