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 paper-based illustration representing Design Sprint with its core stages and visible working result.
Innovation
Design Sprint
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration for Risk Storming.
Architecture
Risk Storming
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Purposedifferent
When the product question is unclear and time pressure is high, the method takes a team from an open idea to a testable solution. It connects problem understanding, decision, and learning in one compact format, lowering the risk of spending a lot of energy on a mere guess.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.ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.
Complexitydifferent
HighHighLowMedium
Timedifferent
4-5 Tage1-4 Wochen60-90 min2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
5-81-64-12Designers, developers as users, and facilitation
Formatdifferent
WorkshopAsyncWorkshopWorkshop + async
Outputdifferent
Prototype, Test Findings, Decision RationaleExperiment results, Decision log, Learning summaryAnnotated Diagram, Prioritized Risk List, Action BacklogPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tags1 shared
Design sprintPrototypeValidationInnovation
ExperimentsGrowthAnalyticsValidation
RiskArchitectureWorkshopValidation
ArchitectureEngineeringFeedbackValidationTasks
Add more methods