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
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration of Double Diamond with its method-specific working model.
Innovation
Double Diamond
Paper illustration of Lean Startup with its method-specific working model.
Innovation
Lean Startup
Paper illustration of Five-Minute VC Check with its method-specific working model.
Business Strategy
5-Minuten VC-Check
Purposedifferent
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.For complex problems with a fuzzy situation, the method cleanly separates search space and decision. It first creates breadth in understanding and then focus in elaboration. This brings open questions, problem definition, and solution path into a traceable movement.For uncertain business assumptions, the method forces the idea into contact with real market reactions early. It separates wishful picture, assumption, and observable behavior, so that learning becomes faster than planning. This translates uncertainty into measurable insight.The 5-Minute VC Check clarifies opportunities and strategic options at the earliest idea stage. It compares problem quality, customer willingness to pay, alternatives, differentiation, and market potential, and captures the result as a VC-check note, go/sharpen/park decision, and risk list.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
2–4 h review as a planning range; preparation and evaluation additionalWochen bis MonateWochen bis Monate je Lernzyklus5-15 min
Participantsdifferent
Designers, developers as users, and facilitation3-122-81-5
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsProblem Statement, Solution Options, Prototypes, Deliverables per PhaseHypothesis list, MVPs, Learning reports, Pivot or persevere decisionVC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation step
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
ProcessDivergenceInnovation
LeanStartupValidationMVP
StartupValidationCompetition
Add more methods