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 two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
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)
Paper illustration of Lean Startup with its method-specific working model.
Innovation
Lean Startup
Paper illustration for Risk Storming.
Architecture
Risk Storming
Purposedifferent
An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.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.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.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
LowMediumMediumLow
Timedifferent
15-45 min3–4 h for initial assessment; preparation and deeper analysis additionalWochen bis Monate je Lernzyklus60-90 min
Participantsdifferent
1-31 or a small team; particularly suitable for 3–4 people2-84-12
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
ADR File, Decision Log, RationaleLean 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 checksHypothesis list, MVPs, Learning reports, Pivot or persevere decisionAnnotated Diagram, Prioritized Risk List, Action Backlog
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
ArchitectureQualityRiskAssessmentLean
LeanStartupValidationMVP
RiskArchitectureWorkshopValidation
Add more methods