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
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)
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
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.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.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.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.
Complexitydifferent
HighMediumLowLow
Timedifferent
4-5 Tage3–4 h for initial assessment; preparation and deeper analysis additional1-2 Tage15-45 min
Participantsdifferent
5-81 or a small team; particularly suitable for 3–4 people1-41-3
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Prototype, Test Findings, Decision 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 checksArchitecture Document, Context View, Runtime View, Deployment ViewADR File, Decision Log, Rationale
Tagsno overlap
Design sprintPrototypeValidationInnovation
ArchitectureQualityRiskAssessmentLean
ArchitectureDocumentationCommunication
ArchitectureRationaleDocumentationGovernance
Add more methods