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
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration for Standard Work Analysis.
Operations
Standard Work Analysis
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)
Purposedifferent
When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions.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.When the same task is done differently depending on the person, the method exposes the reliable core. It creates comparability without unnecessarily choking off needed latitude.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.
Complexitydifferent
LowLowMediumMedium
Timedifferent
30-120 min1-2 Tage1-3 h3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
2-61-42-61 or a small team; particularly suitable for 3–4 people
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Observation Notes, Improvement IdeasArchitecture Document, Context View, Runtime View, Deployment ViewStandard Work Sheet, Deviation List, Improved Standard, Training NeedsLean 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 checks
Tagsno overlap
LeanObservationProcessOperations
ArchitectureDocumentationCommunication
LeanProcessQuality
ArchitectureQualityRiskAssessmentLean
Add more methods