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 a journey map with four connected phases, several experience lanes and a point marked for closer investigation.
UX Research
Customer Journey Mapping
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 Team API with its method-specific working model.
Team Design
Team API
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
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.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.When expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document.The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails.
Complexitydifferent
MediumMediumLowLow
Timedifferent
2-4 h3–4 h for initial assessment; preparation and deeper analysis additionalHalf day initial, dann laufend1-2 h
Participantsdifferent
4-101 or a small team; particularly suitable for 3–4 peopleEin Team plus Stakeholder3-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Journey Map, Pain-point List, Opportunity BacklogLean 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 checksTeam API DocumentInception Canvas, Risks, Goal List, Open Questions
Tagsno overlap
JourneyServiceService design
ArchitectureQualityRiskAssessmentLean
TeamAlignmentCommunicationService
AlignmentArchitectureCanvas
Add more methods