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 for Risk Storming.
Architecture
Risk Storming
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration of Shape-first Modeling with its method-specific working model.
Knowledge Modeling
Shape-First Modeling
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Purposedifferent
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.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.Shape-First Modeling defines data quality through shapes before implementation or integration frays at the edges. The approach fits when validation and data contracts should be part of the design from the start.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
LowHighMediumMedium
Timedifferent
60-90 min1-4 WochenHalber Tag pro Domain Slice2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
4-121-61-4Designers, developers as users, and facilitation
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Annotated Diagram, Prioritized Risk List, Action BacklogExperiment results, Decision log, Learning summarySHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape DocumentationPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tags1 shared
RiskArchitectureWorkshopValidation
ExperimentsGrowthAnalyticsValidation
Knowledge graphValidationSemantic
ArchitectureEngineeringFeedbackValidationTasks
Add more methods