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.

Selected:Design ThinkingAssumption MappingARID (Active Reviews for Intermediate Designs)Risk Storming
Criterion
Design Thinking as a learning loop: an observation notebook, a focused problem statement, different idea sketches, a cardboard prototype and user-test notes. Feedback leads to new understanding.
Innovation
Design Thinking
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration for Risk Storming.
Architecture
Risk Storming
Purposedifferent
For complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.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.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.
Complexitydifferent
HighMediumMediumLow
Timedifferent
1 Tag bis mehrere Wochen45-60 min2–4 h review as a planning range; preparation and evaluation additional60-90 min
Participantsdifferent
4-102-8Designers, developers as users, and facilitation4-12
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Problem Statement, Prototype, Test LearningsAssumption map, Test backlog, Risk rankingPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsAnnotated Diagram, Prioritized Risk List, Action Backlog
Tagsno overlap
InnovationPrototypeResearch
AssumptionsRiskExperimentsValidation
ArchitectureEngineeringFeedbackValidationTasks
RiskArchitectureWorkshopValidation
Add more methods