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 Pretotyping with its method-specific working model.
Product Discovery
Pretotyping
Paper illustration for Risk Storming.
Architecture
Risk Storming
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Purposedifferent
Pretotyping clarifies whether a customer problem and solution idea create enough real demand. It separates problem, assumption, solution, and evidence, and captures the result as a pretotyping sketch, test setup, and conversion data.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.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.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
LowLowLowMedium
Timedifferent
Stunden bis wenige Tage60-90 min45-90 min2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
1-44-122-8Designers, developers as users, and facilitation
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Pretotyping sketch, Test setup, Conversion data, Go or no-go decisionAnnotated Diagram, Prioritized Risk List, Action BacklogAssumption List, Critical Assumptions, Learning PlanPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap
ValidationDemandMVP
RiskArchitectureWorkshopValidation
AssumptionsRiskDecisionDiscovery
ArchitectureEngineeringFeedbackValidationTasks
Add more methods