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 Five-Minute VC Check with its method-specific working model.
Business Strategy
5-Minuten VC-Check
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Purposedifferent
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.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.LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail.
Complexitydifferent
LowMediumMedium
Timedifferent
5-15 min2–4 h review as a planning range; preparation and evaluation additional3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
1-5Designers, developers as users, and facilitation1 or a small team; particularly suitable for 3–4 people
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
VC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation stepPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsLean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checks
Tagsno overlap
StartupValidationCompetition
ArchitectureEngineeringFeedbackValidationTasks
ArchitectureQualityRiskAssessmentLean
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration of Lean Startup with its method-specific working model.
Innovation
Lean Startup
Paper illustration for Risk Storming.
Architecture
Risk Storming
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping