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 C4 Model with its core stages and visible working result.
Architecture
C4 Model
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
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
The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes.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.When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.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
LowLowLowMedium
Timedifferent
1-4 h30-120 min30-60 min3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
1-52-62-81 or a small team; particularly suitable for 3–4 people
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Context Diagram, Container Diagram, Component DiagramObservation Notes, Improvement IdeasFishbone Diagram, Cause Categories, Investigation 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 checks
Tagsno overlap
ArchitectureCommunicationVisualization
LeanObservationProcessOperations
Root causeQualityOperations
ArchitectureQualityRiskAssessmentLean
Add more methods