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 a calibrated five-by-five risk matrix with response cards.
Decision Making
Risk Matrix
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Purposedifferent
When a project faces many possible disruptions, it quickly becomes unclear which risks deserve attention first. It separates options, evaluation criteria, and open risks. The result is captured as a Risk Matrix and a Top Risk List.An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale.When demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.
Complexitydifferent
LowMediumLowMedium
Timedifferent
30-60 min1-3 Wochen vom Draft bis zur Entscheidung1-5 Tage45-60 min
Participantsdifferent
3-103-20 ReviewerNutzertraffic2-8
Formatdifferent
Workshop + asyncAsyncAsyncWorkshop + async
Outputdifferent
Risk Matrix, Top Risk ListRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsInterest Metrics, Conversion Signal, Learning NoteAssumption map, Test backlog, Risk ranking
Tagsno overlap
RiskDecisionPrioritizationAssessment
ArchitectureDecisionAsyncGovernance
ValidationExperimentsDemandGrowth
AssumptionsRiskExperimentsValidation
Add more methods