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)
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
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.In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures.An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale.
Complexitydifferent
LowMediumLowMedium
Timedifferent
15-45 min3–4 h for initial assessment; preparation and deeper analysis additional20–45 min1-3 Wochen vom Draft bis zur Entscheidung
Participantsdifferent
1-31 or a small team; particularly suitable for 3–4 peopleSmall cross-functional group3-20 Reviewer
Formatdifferent
AsyncWorkshop + asyncWorkshopAsync
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 checksRisk list, Mitigation plan, Assumption logRFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
ArchitectureQualityRiskAssessmentLean
RiskDecisionFailurePlanning
ArchitectureDecisionAsyncGovernance
Add more methods