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
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)
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 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.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.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.
Complexitydifferent
HighLowMediumMedium
Timedifferent
4-5 Tage45-90 min2–4 h review as a planning range; preparation and evaluation additional45-60 min
Participantsdifferent
5-82-8Designers, developers as users, and facilitation2-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Prototype, Test Findings, Decision RationaleAssumption List, Critical Assumptions, Learning PlanPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsAssumption map, Test backlog, Risk ranking
Tagsno overlap
Design sprintPrototypeValidationInnovation
AssumptionsRiskDecisionDiscovery
ArchitectureEngineeringFeedbackValidationTasks
AssumptionsRiskExperimentsValidation
Add more methods