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.

Selected:Customer Journey Mappingarc42LASR (Lightweight Approach for Software Reviews)Architecture Decision Record
Criterion
Paper illustration of a journey map with four connected phases, several experience lanes and a point marked for closer investigation.
UX Research
Customer Journey Mapping
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
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 two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Purposedifferent
When a user journey falls apart across many touchpoints, customer journey mapping makes the experience visible as a coherent arc. Phases, emotions, and breaks become legible enough to prioritize critical moments deliberately.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.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.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
MediumLowMediumLow
Timedifferent
2-4 h1-2 Tage3–4 h for initial assessment; preparation and deeper analysis additional15-45 min
Participantsdifferent
4-101-41 or a small team; particularly suitable for 3–4 people1-3
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Journey Map, Pain-point List, Opportunity BacklogArchitecture Document, Context View, Runtime View, Deployment ViewLean 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 checksADR File, Decision Log, Rationale
Tagsno overlap
JourneyServiceService design
ArchitectureDocumentationCommunication
ArchitectureQualityRiskAssessmentLean
ArchitectureRationaleDocumentationGovernance
Add more methods